Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

• 1
• 2
• 3

3.41.0 | Updated: 12 Mar 2017

33,455

2,274

Maintainer(s):

Software Author(s):

• Rony Shapiro
• 1
• 2
• 3

### All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

### Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

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

>
NOTE

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

### 1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

#### 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://community.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

choco upgrade passwordsafe -y --source="'INTERNAL REPO URL'" --version="'3.41.0'" [other options]

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:


$exitCode =$LASTEXITCODE

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

Exit $exitCode   - name: Install passwordsafe win_chocolatey: name: passwordsafe version: '3.41.0' source: INTERNAL REPO URL state: present   chocolatey_package 'passwordsafe' do action :install source 'INTERNAL REPO URL' version '3.41.0' end   cChocoPackageInstaller passwordsafe { Name = "passwordsafe" Version = "3.41.0" Source = "INTERNAL REPO URL" }  Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.  package { 'passwordsafe': ensure => '3.41.0', provider => 'chocolatey', source => 'INTERNAL REPO URL', }  Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey. ### 4. If applicable - Chocolatey configuration/installation See infrastructure management matrix for Chocolatey configuration elements and examples. NOTE Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more... Package Approved This package was approved by moderator flcdrg on 26 Mar 2017. Description Password Safe is a password database utility. Users can keep their passwords securely encrypted on their computers. A single Safe Combination unlocks them all. Please Note: This is an automatically updated package. If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly. tools\chocolateyinstall.ps1 $ErrorActionPreference = 'Stop';

$packageName= 'passwordSafe'$toolsDir   = "$(Split-Path -parent$MyInvocation.MyCommand.Definition)"
$url = 'https://sourceforge.net/projects/passwordsafe/files/passwordsafe/3.41.0/pwsafe-3.41.0.msi'$url64      = 'https://sourceforge.net/projects/passwordsafe/files/passwordsafe/3.41.0/pwsafe-3.41.0.msi'

$packageArgs = @{ packageName =$packageName
unzipLocation = $toolsDir fileType = 'MSI' url =$url
url64bit      = $url64 silentArgs = "/qn /norestart /l*v "$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log""
validExitCodes= @(0, 3010, 1641)

checksum      = '8da60ecc1cce2121facec7e903840c05'
checksumType  = 'md5'
checksum64    = '8da60ecc1cce2121facec7e903840c05}'
checksumType64= 'md5'
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
#   $f='c:\path\to\thisFile.ps1' # gc$f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File$f+".~" -en utf8; mv -fo $f+".~"$f

# If this is an MSI, cleaning up comments is all you need.
# If this is an exe, change installerType and silentArgs
# Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9).

$ErrorActionPreference = 'Stop'; # stop on all errors$packageName = 'passwordSafe'
$softwareName = 'passwordSafe*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique$installerType = 'MSI'
#$installerType = 'EXE'$silentArgs = '/qn /norestart'
# https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
$validExitCodes = @(0, 3010, 1605, 1614, 1641) if ($installerType -ne 'MSI') {
# The below is somewhat naive and built for EXE installers
# Uncomment matching EXE type (sorted by most to least common)
#$silentArgs = '/S' # NSIS #$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup
#$silentArgs = '/s' # InstallShield #$silentArgs = '/s /v"/qn"' # InstallShield with MSI
#$silentArgs = '/s' # Wise InstallMaster #$silentArgs = '-s'           # Squirrel
#$silentArgs = '-q' # Install4j #$silentArgs = '-s -u'        # Ghost
# Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence.
#$silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) # https://chocolatey.org/packages/autohotkey.portable$validExitCodes = @(0)
}

$uninstalled =$false
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key)  -ErrorAction SilentlyContinue  | ? {$_.DisplayName -like "$softwareName" } if ($key.Count -eq 1) {
$key | % {$file = "$($_.UninstallString)"

if ($installerType -eq 'MSI') { # The Product Code GUID is all that should be passed for MSI, and very # FIRST, because it comes directly after /x, which is already set in the # Uninstall-ChocolateyPackage msiargs (facepalm).$silentArgs = "$($_.PSChildName) $silentArgs" # Don't pass anything for file, it is ignored for msi (facepalm number 2) # Alternatively if you need to pass a path to an msi, determine that and # use it instead of the above in silentArgs, still very first$file = ''
}

Uninstall-ChocolateyPackage -PackageName $packageName  -FileType$installerType
-SilentArgs "$silentArgs"  -ValidExitCodes$validExitCodes
-File "$file" } } 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"} } ## OTHER HELPERS ## https://github.com/chocolatey/choco/wiki/HelpersReference #Uninstall-ChocolateyZipPackage #Uninstall-BinFile # Only needed if you added one in the installer script, choco will remove the ones it added automatically. #remove any shortcuts you added  tools\ReadMe.md ## Summary How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages If you are submitting packages to the community feed (https://chocolatey.org) always try to ensure you have read, understood and adhere to the create packages wiki link above. ## Automatic Packages? Consider making this package an automatic package, for the best maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages ## Shim Generation Any executables you include in the package or download (but don't call install against using the built-in functions) will be automatically shimmed. This means those executables will automatically be included on the path. Shim generation runs whether the package is self-contained or uses automation scripts. By default, these are considered console applications. If the application is a GUI, you should create an empty file next to the exe named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'. See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui If you want to ignore the executable, create an empty file next to the exe named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 'bob.exe.ignore'. See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects ## Self-Contained? If you have a self-contained package, you can remove the automation scripts entirely and just include the executables, they will automatically get shimmed, which puts them on the path. Ensure you have the legal right to distribute the application though. See https://github.com/chocolatey/choco/wiki/Legal. You should read up on the Shim Generation section to familiarize yourself on what to do with GUI applications and/or ignoring shims. ## Automation Scripts You have a powerful use of Chocolatey, as you are using PowerShell. So you can do just about anything you need. Choco has some very handy built-in functions that you can use, these are sometimes called the helpers. ### Built-In Functions https://github.com/chocolatey/choco/wiki/HelpersReference A note about a couple: * Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. * Install-BinFile - used for non-exe files - executables are automatically shimmed... * Uninstall-BinFile - used for non-exe files - executables are automatically shimmed ### Getting package specific information Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument ### Need to mount an ISO? https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package ### Environment Variables Chocolatey makes a number of environment variables available (You can access any of these with$env:TheVariableNameBelow):

* TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
* ChocolateyInstall = Top level folder where Chocolatey is installed
* chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
* chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
* chocolateyPackageFolder = The top level location of the package folder

The following are more advanced settings:

* chocolateyPackageParameters = (0.9.8.22+)
* CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
- Otherwise take a dependency on the specific version you need.
* chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
- Automatically handled in built in Choco functions.
* OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
* OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
* OS_NAME = The reported name of the OS. (0.9.9+)
* IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)

#### Experimental Environment Variables
The following are experimental or use not recommended:

* OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
* CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
- it's based on git describe
* IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
* chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
* chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)



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.

passwordSafe (Install) 3.60.0 1382 Monday, October 17, 2022 Approved
passwordSafe (Install) 3.59.0 4432 Sunday, June 19, 2022 Approved
passwordSafe (Install) 3.58.0 2248 Thursday, December 23, 2021 Approved
passwordSafe (Install) 3.57.0 925 Wednesday, October 27, 2021 Approved
passwordSafe (Install) 3.55.0 2844 Tuesday, February 9, 2021 Approved
passwordSafe (Install) 3.54.1 1526 Monday, October 26, 2020 Approved
passwordSafe (Install) 3.53.0 950 Friday, September 11, 2020 Approved
passwordSafe (Install) 3.52.0 1959 Monday, April 13, 2020 Approved
passwordSafe (Install) 3.51.0 1244 Tuesday, January 7, 2020 Approved

This package has no dependencies.

Discussion for the passwordSafe (Install) Package