Downloads of v 1.1.7:


Last Update:

14 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Mike Bos


pass4win passwordstore password admin


  • 1
  • 2
  • 3

1.1.7 | Updated: 14 Jan 2016



Downloads of v 1.1.7:



Software Author(s):

  • Mike Bos

  • 1
  • 2
  • 3
pass4win 1.1.7

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install pass4win, run the following command from the command line or from PowerShell:


To upgrade pass4win, run the following command from the command line or from PowerShell:


To uninstall pass4win, 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 pass4win -y --source="'INTERNAL REPO 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 pass4win -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install pass4win
    name: pass4win
    version: '1.1.7'
    state: present

See docs at

chocolatey_package 'pass4win' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.1.7'

See docs at

cChocoPackageInstaller pass4win
    Name     = "pass4win"
    Version  = "1.1.7"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'pass4win':
  ensure   => '1.1.7',
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator ferventcoder on 14 Jan 2016.


Windows version of Pass ( in the sense that the store (password structure) is and should be exactly the same between the two programs.

$ErrorActionPreference = 'Stop';

$packageName = 'pass4win'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = ''

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

  silentArgs    = '/S'
  validExitCodes= @(0, 3010, 1641)
  registryUninstallerKey = 'Pass4Win'
  checksum      = ''
  checksumType  = 'md5'
  checksum64    = ''
  checksumType64= 'md5'

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'pass4win'
$registryUninstallerKeyName = 'Pass4Win'
$msiProductCodeGuid = '{insert it here}'
$shouldUninstall = $true

$local_key     = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$local_key6432   = "HKCU:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName" 
$machine_key   = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key6432 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"

$file = @($local_key, $local_key6432, $machine_key, $machine_key6432) `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString

if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false

$installerType = 'EXE' 

$silentArgs = '/S'

$validExitCodes = @(0, 3010, 1605, 1614, 1641)

$file = 'C:\Program Files (x86)\Pass4Win\uninstall.exe'

if ($shouldUninstall) {
 Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes -File $file

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
Pass4Win 1.0.6 342 Tuesday, September 8, 2015 Approved


Removed bug which resulted in a new version announcement at all times.


So accidentally I omitted the German language files from the release. Clever huh.
As added bonus:

Only instance can be active now
Fixed some compiler warnings


Added german language
rewrote configuration handling so it should work in more scenario's (work computers notably)
Added HidPI awareness
Several bug fixes and code cleanup thx too mapitman


Found some bugs, basically with 1.1.3 there are some issues with a new file, renaming etc.


Added Tree view
Added Italian translation
Rewrote file handling portion
Added context menu for the password details
Added toolbar, instead of the buttons
Cleaned up a lot of code
Using fody to weave most of the dll's into the exe
Using fody to handle null exceptions
Added uninstall on install

If you want to get the latest news follow on twitter @Pass4Win
New Gitter page to just ask questions that don't really belong in issues or whatever.




I really need translators and validators :-) the process is simple you don't need to know how to code, or to read code. Suggestions are made based on microsoft translate. Translating the entire program costs 10 minutes max after I set you up with access to Crowdin.

I'm using a lot more services, the build passes the coverity scan, builds are confirmed on travis-ci and unhandled exceptions are now sent through Bugsnag (also used by github for Atom).


Localisation currently in English (default) and Dutch. Depending on your OS settings the language will be chosen
Password generator
Toolbar with icons instead of the different buttons
Exceptions which are not handled will be fetched by Bugsnag
Search now has a delay of half a second and an autocomplete feature


Lot of bugfixes:

Key matching (on mail address)
GIT settings
Minimizes to systray, exit through right click menu


Installer is only silent when the /S flag is given, otherwise normal
Config is now handled in a smarter way and will transfer with a new version



Add password doesn't require multiple clicks anymore
Right click shows a disabled menu if no entry is selected
Check for a new version and yes even tells you about it when there is a new version


Checks if the keys defined in .gpg-id are in the gpg keystore before encrypting

Have fun with it.


Installation is silent now
Uninstall honors the /S flag
Added GPL notice to not generated source files
Added an about form
added version info
fixed remote bug on initial config
GitIsAlive and HTTPSisAlive don't throw exceptions anymore when the URL is not valid
Config validation fixed (issue #42)
Fixed remote server usability issues Issue #43

Discussion for the pass4win Package

Ground Rules:

  • This discussion is only about pass4win and the pass4win 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 pass4win, 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