Downloads of v 0.6.4:


Last Update:

25 Sep 2018

Package Maintainer(s):

Software Author(s):

  • Scille


parsec secure encrypted resilient cloud storage

parsec (Install)

This is not the latest version of parsec (Install) available.

  • 1
  • 2
  • 3

0.6.4 | Updated: 25 Sep 2018



Downloads of v 0.6.4:



Software Author(s):

  • Scille

  • 1
  • 2
  • 3
parsec (Install) 0.6.4

This is not the latest version of parsec (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install parsec (Install), run the following command from the command line or from PowerShell:


To upgrade parsec (Install), run the following command from the command line or from PowerShell:


To uninstall parsec (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

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 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

3. Copy Your Script

choco upgrade parsec-cloud -y --source="'INTERNAL REPO URL'" --version="'0.6.4'" [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 parsec-cloud -y --source="'INTERNAL REPO URL'" --version="'0.6.4'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install parsec-cloud
    name: parsec-cloud
    version: '0.6.4'
    state: present

See docs at

chocolatey_package 'parsec-cloud' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.6.4'

See docs at

cChocoPackageInstaller parsec-cloud
    Name     = "parsec-cloud"
    Version  = "0.6.4"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'parsec-cloud':
  ensure   => '0.6.4',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 25 Sep 2018.


Secure cloud framework

$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$url64      = ''

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url
  url64bit      = $url64

  softwareName  = 'parsec*'

  checksum      = 'F048A91577888ED23CC265BB37B75569C737FD794425F94242E55ECAC8C99057'
  checksumType  = 'sha256'
  checksum64    = 'F048A91577888ED23CC265BB37B75569C737FD794425F94242E55ECAC8C99057'
  checksumType64= 'sha256'

  silentArgs    = "/S `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`""
  validExitCodes= @(0, 3010, 1641)

Install-ChocolateyPackage @packageArgs

$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'parsec*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  fileType      = 'EXE' #only one of these: MSI or EXE (ignore MSU for now)
  silentArgs    = "/S"
  validExitCodes= @(0, 3010, 1605, 1614, 1641) #

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['file'] = ''

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

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.

Add to Builder Version Downloads Last Updated Status
parsec (Install) 0.10.4 226 Tuesday, March 19, 2019 Approved
parsec (Install) 0.10.0 195 Thursday, March 7, 2019 Approved
parsec (Install) 0.9.2 224 Sunday, January 13, 2019 Approved
parsec (Install) 0.8.7 180 Saturday, January 12, 2019 Approved
parsec (Install) 0.8.3 226 Friday, November 16, 2018 Approved
parsec (Install) 0.8.2 197 Thursday, November 15, 2018 Approved
parsec (Install) 0.8.1 194 Thursday, November 8, 2018 Approved
parsec (Install) 0.6.6 192 Monday, October 1, 2018 Approved
parsec (Install) 0.6.5 188 Monday, October 1, 2018 Approved
parsec (Install) 0.6.4 205 Tuesday, September 25, 2018 Approved
parsec (Install) 0.6.3 218 Monday, September 24, 2018 Approved
parsec (Install) 0.6.2 249 Tuesday, August 28, 2018 Approved
parsec (Install) 0.6.1 233 Monday, August 27, 2018 Approved

Discussion for the parsec (Install) Package

Ground Rules:

  • This discussion is only about parsec (Install) and the parsec (Install) 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 parsec (Install), 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.
comments powered by Disqus