Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...

Downloads:
6,650
Downloads of v 1.3.0.501:
287
Last Update:
25 Jun 2019
Package Maintainer(s):
Software Author(s):
- Yukata Sawada
Tags:
multipar parchive NG data protect- Software Specific:
- Software Site
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

MultiPar
- Software Specific:
- Software Site
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
6,650
Downloads of v 1.3.0.501:
287
Software Author(s):
- Yukata Sawada
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
Some Checks Have Failed or Are Not Yet Complete
1 Test Passing and 1 Failing Test
To install MultiPar, run the following command from the command line or from PowerShell:
To upgrade MultiPar, run the following command from the command line or from PowerShell:
To uninstall MultiPar, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download multipar --internalize --source=https://chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade multipar -y --source="'STEP 3 URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade multipar -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure multipar installed
win_chocolatey:
name: multipar
state: present
version: 1.3.0.501
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'multipar' do
action :install
version '1.3.0.501'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: multipar,
Version: 1.3.0.501,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller multipar
{
Name = 'multipar'
Ensure = 'Present'
Version = '1.3.0.501'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'multipar':
provider => 'chocolatey',
ensure => '1.3.0.501',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install multipar version="1.3.0.501" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was approved as a trusted package on 29 Jul 2019.
MultiPar can do file verification, error detection, correction and recovery to protect your files and folders from deletion, copy errors, download errors, software errors, hardware errors, virus infection, malicious tampering, and all other forms of data corruption.
MultiPar was made as an alternative to QuickPar. While it looks like a multi-lingual version of QuickPar, there are some good features; Unicode characters, directory-tree, faster repairing, smaller recovery files, batch scripting, and so on.
Features
MultiPar supports both PAR 1.0 and PAR 2.0 specifications.
See the Parchive project for details of Parchive.
- MultiPar.1.3.0.501.nupkg (b62ef7534c82) - ## / 61 - Log in or click on link to see number of positives
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version | Downloads | Last Updated | Status |
---|---|---|---|
MultiPar 1.3.0.501 | 287 | Tuesday, June 25, 2019 | Approved |
MultiPar 1.3.0.500 | 154 | Friday, May 24, 2019 | Approved |
MultiPar 1.3.0.5 | 107 | Saturday, May 11, 2019 | Approved |
MultiPar 1.3.0.4 | 89 | Saturday, April 20, 2019 | Approved |
MultiPar 1.2.9.9 | 923 | Wednesday, December 21, 2016 | Approved |
MultiPar 1.2.9.8 | 287 | Tuesday, November 15, 2016 | Approved |
MultiPar 1.2.9.7 | 312 | Thursday, October 20, 2016 | Approved |
MultiPar 1.2.9.6 | 326 | Saturday, July 30, 2016 | Approved |
MultiPar 1.2.9.5 | 246 | Wednesday, July 20, 2016 | Approved |
MultiPar 1.2.9.3 | 224 | Sunday, May 8, 2016 | Approved |
MultiPar 1.2.9.1 | 275 | Saturday, February 13, 2016 | Approved |
MultiPar 1.2.9.0 | 224 | Friday, January 8, 2016 | Approved |
MultiPar 1.2.8.7 | 259 | Sunday, December 6, 2015 | Approved |
MultiPar 1.2.8.6 | 237 | Saturday, October 24, 2015 | Approved |
MultiPar 1.2.8.5 | 209 | Monday, October 5, 2015 | Approved |
MultiPar 1.2.8.4 | 235 | Sunday, September 20, 2015 | Approved |
MultiPar 1.2.8.3 | 248 | Friday, August 28, 2015 | Approved |
MultiPar 1.2.8.2 | 233 | Tuesday, August 11, 2015 | Approved |
MultiPar 1.2.8.0 | 250 | Sunday, July 12, 2015 | Approved |
MultiPar 1.2.7.6 | 251 | Friday, July 10, 2015 | Approved |
MultiPar 1.2.3.3 | 601 | Saturday, November 23, 2013 | Approved |
MultiPar 1.2.2.6 | 350 | Monday, June 24, 2013 | Approved |
© 2012 - 2019 Multipar.eu | All rights reserved
-
- multipar.install (= 1.3.0.501)
Ground Rules:
- This discussion is only about MultiPar and the MultiPar package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or MultiPar, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.