




Downloads of v


Last update

This is not the latest version of Chocolatey available.


There are no package test results for this package

This package was approved as a trusted package on 3/7/2015.


Chocolatey is brought to you by the work and inspiration of the community, the work and thankless nights of the Chocolatey Team, with Rob heading up the direction.

You can host your own sources and add them to Chocolatey, you can extend Chocolatey's capabilities, and folks, it's only going to get better.


There are quite a few commands you can call - you should check out the command reference. Here are the most common:

  • Search - choco search something
  • List - choco list -lo
  • Install - choco install baretail
  • Pin - choco pin windirstat
  • Upgrade - choco upgrade baretail
  • Uninstall - choco uninstall baretail

    Alternative installation sources (TEMPORARILY DISABLED IN 0.9.9):

  • Install ruby gem - choco install compass -source ruby
  • Install python egg - choco install sphynx -source python
  • Install windows feature - choco install IIS -source windowsfeatures
  • Install webpi feature - choco install IIS7.5Express -source webpi

For more advanced commands and switches, use choco -? or choco command -h. You can also look at the command reference, including how you can force a package to install the x86 version of a package.

Create Packages?


In that mess there is a link to the Helper Reference.


C:\> choco install chocolatey --version


C:\> choco upgrade chocolatey --version


  • tools\chocolateyInstall.ps1 Show
    $toolsPath = (Split-Path -parent $MyInvocation.MyCommand.Definition)
    # ensure module loading preference is on
    $PSModuleAutoLoadingPreference = "All";
    $modules = Get-ChildItem $toolsPath -Filter *.psm1
    $modules | ForEach-Object {
    														$psm1File = $_.FullName;
    														$moduleName = $([System.IO.Path]::GetFileNameWithoutExtension($psm1File))
    														remove-module $moduleName -ErrorAction SilentlyContinue;
    														import-module -name  $psm1File;
  • tools\chocolateyInstall\choco.exe
  • tools\chocolateyInstall\choco.exe.ignore
  • tools\chocolateysetup.psm1 Show
    $thisScriptFolder = (Split-Path -parent $MyInvocation.MyCommand.Definition)
    $chocInstallVariableName = "ChocolateyInstall"
    $sysDrive = $env:SystemDrive
    $tempDir = $env:TEMP
    $defaultChocolateyPathOld = "$sysDrive\Chocolatey"
    #$ErrorActionPreference = 'Stop'
    $debugMode = $false
    function Initialize-Chocolatey {
        This will initialize the Chocolatey tool by
          a) setting up the "nugetPath" (the location where all chocolatey nuget packages will be installed)
          b) Installs chocolatey into the "nugetPath"
                c) Instals .net 4.0 if needed
          d) Adds chocolaty to the PATH environment variable so you have access to the chocolatey|cinst commands.
      .PARAMETER  NuGetPath
        Allows you to override the default path of (C:\Chocolatey\) by specifying a directory chocolaty will install nuget packages.
        C:\PS> Initialize-Chocolatey
        Installs chocolatey into the default C:\Chocolatey\ directory.
        C:\PS> Initialize-Chocolatey -nugetPath "D:\ChocolateyInstalledNuGets\"
        Installs chocolatey into the custom directory D:\ChocolateyInstalledNuGets\
      [Parameter(Mandatory=$false)][string]$chocolateyPath = ''
      Write-Debug "Initialize-Chocolatey"
      if ($env:ChocolateyEnvironmentDebug -eq 'true') {
        $debugMode = $true
      $chocoNew = Join-Path $thisScriptFolder 'chocolateyInstall\choco.exe'
      if ($debugMode) {
        & $chocoNew unpackself -fdv
      } else {
        & $chocoNew unpackself -f
      $installModule = Join-Path $thisScriptFolder 'chocolateyInstall\helpers\chocolateyInstaller.psm1'
      Import-Module $installModule -Force
      if ($chocolateyPath -eq '') {
        $programData = [Environment]::GetFolderPath("CommonApplicationData")
        $chocolateyPath = Join-Path "$programData" 'chocolatey'
      # variable to allow insecure directory:
      $allowInsecureRootInstall = $false
      if ($env:ChocolateyAllowInsecureRootDirectory -eq 'true') { $allowInsecureRootInstall = $true }
      # if we have an already environment variable path, use it.
      $alreadyInitializedNugetPath = Get-ChocolateyInstallFolder
      if ($alreadyInitializedNugetPath -and $alreadyInitializedNugetPath -ne $chocolateyPath -and ($allowInsecureRootInstall -or $alreadyInitializedNugetPath -ne $defaultChocolateyPathOld)){
        $chocolateyPath = $alreadyInitializedNugetPath
      else {
        Set-ChocolateyInstallFolder $chocolateyPath
      Create-DirectoryIfNotExists $chocolateyPath
      Ensure-UserPermissions $chocolateyPath
      #set up variables to add
      $chocolateyExePath = Join-Path $chocolateyPath 'bin'
      $chocolateyLibPath = Join-Path $chocolateyPath 'lib'
      if ($tempDir -eq $null) {
        $tempDir = Join-Path $chocolateyPath 'temp'
        Create-DirectoryIfNotExists $tempDir
      $yourPkgPath = [System.IO.Path]::Combine($chocolateyLibPath,"yourPackageName")
    We are setting up the Chocolatey package repository.
    The packages themselves go to `'$chocolateyLibPath`'
      (i.e. $yourPkgPath).
    A shim file for the command line goes to `'$chocolateyExePath`'
      and points to an executable in `'$yourPkgPath`'.
    Creating Chocolatey folders if they do not already exist.
    "@ | Write-Output
      Write-Warning "You can safely ignore errors related to missing log files when `n  upgrading from a version of Chocolatey less than 0.9.9. `n  'Batch file could not be found' is also safe to ignore. `n  'The system cannot find the file specified' - also safe."
      #create the base structure if it doesn't exist
      Create-DirectoryIfNotExists $chocolateyExePath
      Create-DirectoryIfNotExists $chocolateyLibPath
      Install-ChocolateyFiles $chocolateyPath
      Ensure-ChocolateyLibFiles $chocolateyLibPath
      Install-ChocolateyBinFiles $chocolateyPath $chocolateyExePath
      $chocolateyExePathVariable = $chocolateyExePath.ToLower().Replace($chocolateyPath.ToLower(), "%DIR%..\").Replace("\\","\")
      Initialize-ChocolateyPath $chocolateyExePath $chocolateyExePathVariable
      Process-ChocolateyBinFiles $chocolateyExePath $chocolateyExePathVariable
      $realModule = Join-Path $chocolateyPath "helpers\chocolateyInstaller.psm1"
      Import-Module "$realModule" -Force
      if (-not $allowInsecureRootInstall -and (Test-Path($defaultChocolateyPathOld))) {
        Upgrade-OldChocolateyInstall $defaultChocolateyPathOld $chocolateyPath
        Install-ChocolateyBinFiles $chocolateyPath $chocolateyExePath
    Chocolatey (choco.exe) is now ready.
    You can call choco from anywhere, command line or powershell by typing choco.
    Run choco /? for a list of functions.
    You may need to shut down and restart powershell and/or consoles
     first prior to using choco.
    "@ | write-Output
      if (-not $allowInsecureRootInstall) {
        Remove-OldChocolateyInstall $defaultChocolateyPathOld
    function Set-ChocolateyInstallFolder {
      Write-Debug "Set-ChocolateyInstallFolder"
      $environmentTarget = [System.EnvironmentVariableTarget]::User
      # removing old variable
      Install-ChocolateyEnvironmentVariable -variableName "$chocInstallVariableName" -variableValue $null -variableType $environmentTarget
      if (Test-ProcessAdminRights) {
        Write-Debug "Administrator installing so using Machine environment variable target instead of User."
        $environmentTarget = [System.EnvironmentVariableTarget]::Machine
        # removing old variable
      } else {
        Write-Warning "Setting ChocolateyInstall Environment Variable on USER and not SYSTEM variables.`n  This is due to either non-administrator install OR the process you are running is not being run as an Administrator."
      Write-Output "Creating $chocInstallVariableName as an environment variable (targeting `'$environmentTarget`') `n  Setting $chocInstallVariableName to `'$folder`'"
      Write-Warning "It's very likely you will need to close and reopen your shell `n  before you can use choco."
      Install-ChocolateyEnvironmentVariable -variableName "$chocInstallVariableName" -variableValue "$folder" -variableType $environmentTarget
    function Get-ChocolateyInstallFolder(){
      Write-Debug "Get-ChocolateyInstallFolder"
    function Create-DirectoryIfNotExists($folderName){
      Write-Debug "Create-DirectoryIfNotExists"
      if (![System.IO.Directory]::Exists($folderName)) { [System.IO.Directory]::CreateDirectory($folderName) | Out-Null }
    function Ensure-UserPermissions {
      Write-Debug "Ensure-UserPermissions"
      if (!(Test-ProcessAdminRights)) {
        Write-Warning "User is not running elevated, cannot set user permissions."
      try {
        # get current user
        $currentUser = [Security.Principal.WindowsIdentity]::GetCurrent()
        # get current acl
        $acl = Get-Acl $folder
        # define rule to inject
        $rights = "Modify"
        $userAccessRule = New-Object System.Security.AccessControl.FileSystemAccessRule($currentUser.Name, $rights, "Allow")
        # this is idempotent
        Write-Output "Adding Modify permission for current user to '$folder'"
        Set-Acl $folder $acl
      } catch {
        Write-Warning "Not able to set permissions for user."
    function Upgrade-OldChocolateyInstall {
      [string]$chocolateyPathOld = "$sysDrive\Chocolatey",
      [string]$chocolateyPath =  "$($env:ALLUSERSPROFILE)\chocolatey"
      Write-Debug "Upgrade-OldChocolateyInstall"
      if (Test-Path $chocolateyPathOld) {
        Write-Output "Attempting to upgrade `'$chocolateyPathOld`' to `'$chocolateyPath`'."
        Write-Warning "Copying the contents of `'$chocolateyPathOld`' to `'$chocolateyPath`'. `n This step may fail if you have anything in this folder running or locked."
        Write-Output 'If it fails, just manually copy the rest of the items out and then delete the folder.'
        Write-Host "!!!! ATTN: YOU WILL NEED TO CLOSE AND REOPEN YOUR SHELL !!!!" -ForegroundColor Magenta -BackgroundColor Black
        $chocolateyExePathOld = Join-Path $chocolateyPathOld 'bin'
        'Machine', 'User' |
        % {
          $path = Get-EnvironmentVariable -Name 'PATH' -Scope $_
          $updatedPath = [System.Text.RegularExpressions.Regex]::Replace($path,[System.Text.RegularExpressions.Regex]::Escape($chocolateyExePathOld) + '(?>;)?', '', [System.Text.RegularExpressions.RegexOptions]::IgnoreCase)
          if ($updatedPath -ne $path) {
            Write-Output "Updating `'$_`' PATH to reflect removal of '$chocolateyPathOld'."
            try {
              Set-EnvironmentVariable -Name 'Path' -Value $updatedPath -Scope $_ -ErrorAction Stop
            } catch {
              Write-Warning "Was not able to remove the old environment variable from PATH. You will need to do this manually"
        Copy-Item "$chocolateyPathOld\lib\*" "$chocolateyPath\lib" -force -recurse
        $from = "$chocolateyPathOld\bin"
        $to = "$chocolateyPath\bin"
        $exclude = @("choco.exe", "chocolatey.exe", "cinst.exe", "clist.exe", "cpack.exe", "cpush.exe", "cuninst.exe", "cup.exe", "cver.exe", "RefreshEnv.cmd")
        Get-ChildItem -Path $from -recurse -Exclude $exclude |
          % {
            Write-Debug "Copying $_ `n to $to"
            if ($_.PSIsContainer) {
              Copy-Item $_ -Destination (Join-Path $to $_.Parent.FullName.Substring($from.length)) -Force -ErrorAction SilentlyContinue
            } else {
              $fileToMove = (Join-Path $to $_.FullName.Substring($from.length))
              try {
               Copy-Item $_ -Destination $fileToMove -Exclude $exclude -Force -ErrorAction Stop
              catch {
                Write-Warning "Was not able to move `'$fileToMove`'. You may need to reinstall the shim"
    function Remove-OldChocolateyInstall {
      [string]$chocolateyPathOld = "$sysDrive\Chocolatey"
      Write-Debug "Remove-OldChocolateyInstall"
      if (Test-Path $chocolateyPathOld) {
        Write-Warning "This action will result in Log Errors, you can safely ignore those. `n You may need to finish removing '$chocolateyPathOld' manually."
        try {
          Get-ChildItem -Path "$chocolateyPathOld" | % {
            if (Test-Path $_.FullName) {
              Write-Debug "Removing $_ unless matches .log"
              Remove-Item $_.FullName -exclude *.log -recurse -force -ErrorAction SilentlyContinue
          Write-Output "Attempting to remove `'$chocolateyPathOld`'. This may fail if something in the folder is being used or locked."
          Remove-Item "$($chocolateyPathOld)" -force -recurse -ErrorAction Stop
        catch {
          Write-Warning "Was not able to remove `'$chocolateyPathOld`'. You will need to manually remove it."
    function Install-ChocolateyFiles {
      Write-Debug "Install-ChocolateyFiles"
      Write-Debug "Removing install files in chocolateyInstall, helpers, redirects, and tools"
      "$chocolateyPath\chocolateyInstall", "$chocolateyPath\helpers", "$chocolateyPath\redirects", "$chocolateyPath\tools" | % {
        #Write-Debug "Checking path $_"
        if (Test-Path $_) {
          Get-ChildItem -Path "$_" | % {
            #Write-Debug "Checking child path $_ ($($_.FullName))"
            if (Test-Path $_.FullName) {
              Write-Debug "Removing $_ unless matches .log"
      Write-Debug "Attempting to move choco.exe to choco.exe.old so we can place the new version here."
      # rename the currently running process / it will be locked if it exists
      $chocoExe = Join-Path $chocolateyPath 'choco.exe'
      if (Test-Path ($chocoExe)) {
        Write-Debug "Renaming '$chocoExe' to '$chocoExe.old'"
        try {
          Remove-Item "$chocoExe.old" -force -ErrorAction SilentlyContinue
          Move-Item $chocoExe "$chocoExe.old" -force -ErrorAction SilentlyContinue
        catch {
          Write-Warning "Was not able to rename `'$chocoExe`' to `'$chocoExe.old`'."
      Write-Debug "Unpacking files required for Chocolatey."
      $chocInstallFolder = Join-Path $thisScriptFolder "chocolateyInstall"
      $chocoExe = Join-Path $chocInstallFolder 'choco.exe'
      $chocoExeDest = Join-Path $chocolateyPath 'choco.exe'
      Copy-Item $chocoExe $chocoExeDest -force
      if ($debugMode) {
        & $chocoExeDest unpackself -fdv
      } else {
        & $chocoExeDest unpackself -f
    function Ensure-ChocolateyLibFiles {
      Write-Debug "Ensure-ChocolateyLibFiles"
      $chocoPkgDirectory = Join-Path $chocolateyLibPath 'chocolatey'
      if ( -not (Test-Path("$chocoPkgDirectory\chocolatey.nupkg")) ) {
        Write-Output "Ensuring '$chocoPkgDirectory' exists."
        Create-DirectoryIfNotExists $chocoPkgDirectory
        $chocoPkg = Get-ChildItem "$thisScriptFolder/../../" | ?{$ -match "^chocolatey.*nupkg"} | Sort name -Descending | Select -First 1
        if ($chocoPkg -ne '') { $chocoPkg = $chocoPkg.FullName }
        "$tempDir\", "$chocoPkg" | % {
          if ($_ -ne $null -and $_ -ne '') {
            if (Test-Path $_) {
              Copy-Item $_ "$chocoPkgDirectory\chocolatey.nupkg" -force -ErrorAction SilentlyContinue
    function Install-ChocolateyBinFiles {
      [string] $chocolateyPath,
      [string] $chocolateyExePath
      Write-Debug "Install-ChocolateyBinFiles"
      Write-Debug "Installing the bin file redirects"
      $redirectsPath = Join-Path $chocolateyPath 'redirects'
      if (!(Test-Path "$redirectsPath")) {
        Write-Warning "$redirectsPath does not exist"
      $exeFiles = Get-ChildItem "$redirectsPath" -include @("*.exe","*.cmd") -recurse
      foreach ($exeFile in $exeFiles) {
        $exeFilePath = $exeFile.FullName
        $exeFileName = [System.IO.Path]::GetFileName("$exeFilePath")
        $binFilePath = Join-Path $chocolateyExePath $exeFileName
        $binFilePathRename = $binFilePath + '.old'
        $batchFilePath = $binFilePath.Replace(".exe",".bat")
        $bashFilePath = $binFilePath.Replace(".exe","")
        if (Test-Path ($batchFilePath)) { Remove-Item $batchFilePath -force -ErrorAction SilentlyContinue }
        if (Test-Path ($bashFilePath)) { Remove-Item $bashFilePath -force -ErrorAction SilentlyContinue }
        if (Test-Path ($binFilePathRename)) {
          try {
            Write-Debug "Attempting to remove $binFilePathRename"
            Remove-Item $binFilePathRename -force -ErrorAction Stop
          catch {
            Write-Warning "Was not able to remove `'$binFilePathRename`'. This may cause errors."
        if (Test-Path ($binFilePath)) {
         try {
            Write-Debug "Attempting to rename $binFilePath to $binFilePathRename"
            Move-Item -path $binFilePath -destination $binFilePathRename -force -ErrorAction Stop
          catch {
            Write-Warning "Was not able to rename `'$binFilePath`' to `'$binFilePathRename`'."
        try {
          Write-Debug "Attempting to copy $exeFilePath to $binFilePath"
          Copy-Item -path $exeFilePath -destination $binFilePath -force -ErrorAction Stop
        catch {
          Write-Warning "Was not able to replace `'$binFilePath`' with `'$exeFilePath`'. You may need to do this manually."
        $commandShortcut = [System.IO.Path]::GetFileNameWithoutExtension("$exeFilePath")
        Write-Debug "Added command $commandShortcut"
    function Initialize-ChocolateyPath {
      [string]$chocolateyExePath = "$($env:ALLUSERSPROFILE)\chocolatey\bin",
      [string]$chocolateyExePathVariable = "%$($chocInstallVariableName)%\bin"
      Write-Debug "Initialize-ChocolateyPath"
      Write-Debug "Initializing Chocolatey Path if required"
      $environmentTarget = [System.EnvironmentVariableTarget]::User
      if (Test-ProcessAdminRights) {
        $environmentTarget = [System.EnvironmentVariableTarget]::Machine
      } else {
        Write-Warning "Setting ChocolateyInstall Path on USER PATH and not SYSTEM Path.`n  This is due to either non-administrator install OR the process you are running is not being run as an Administrator."
      Install-ChocolateyPath -pathToInstall "$chocolateyExePath" -pathType $environmentTarget
    function Process-ChocolateyBinFiles {
      Write-Debug "Process-ChocolateyBinFiles"
      $processedMarkerFile = Join-Path $chocolateyExePath '_processed.txt'
      if (!(test-path $processedMarkerFile)) {
        $files = get-childitem $chocolateyExePath -include *.bat -recurse
        if ($files -ne $null -and $files.Count -gt 0) {
          Write-Debug "Processing Bin files"
          foreach ($file in $files) {
            Write-Output "Processing $($file.Name) to make it portable"
            $fileStream = [System.IO.File]::Open("$file", 'Open', 'Read', 'ReadWrite')
            $reader = New-Object System.IO.StreamReader($fileStream)
            $fileText = $reader.ReadToEnd()
            $fileText = $fileText.ToLower().Replace("`"" + $chocolateyPath.ToLower(), "SET DIR=%~dp0%`n""%DIR%..\").Replace("\\","\")
            Set-Content $file -Value $fileText -Encoding Ascii
        Set-Content $processedMarkerFile -Value "$([System.DateTime]::Now.Date)" -Encoding Ascii
    function Install-DotNet4IfMissing {
      Write-Debug "Install-DotNet4IfMissing"
      if ([IntPtr]::Size -eq 8) {$fx="framework64"} else {$fx="framework"}
      Write-Debug "Installing .NET Framework 4.0 if it is missing"
      if (!(test-path "$env:windir\Microsoft.Net\$fx\v4.0.30319")) {
        $NetFx4ClientUrl = ''
        $NetFx4FullUrl = ''
        Install-ChocolateyPackage "NetFx4.0" 'exe' -silentArgs "/q /norestart /repair /log `'$tempDir\NetFx4Install.log`'" -url "$NetFx4FullUrl" -url64bit "$NetFx4FullUrl" -validExitCodes @(0, 3010)
    Export-ModuleMember -function Initialize-Chocolatey;
  • tools\init.ps1 Show
    $modules = Get-ChildItem $ToolsPath -Filter *.psm1
    $modules | ForEach-Object { import-module -name  $_.FullName }
    Welcome to Chocolatey, your local machine repository built on the NuGet infrastructure. Chocolatey allows you to install application packages to your machine with the goodness of a #chocolatey #nuget combo. 
    Application executables get added to the path automatically so you can call them from anywhere (command line/powershell prompt), not just in Visual Studio.
    Lets get Chocolatey!
    Visual Studio -
    Please run Initialize-Chocolatey one time per machine to set up the repository. 
    If you are upgrading, please remember to run Initialize-Chocolatey again.
    After you have run Initiliaze-Chocolatey, you can safely uninstall the chocolatey package from your current Visual Studio solution.
    Alternative NuGet -
    If you are not using NuGet in Visual Studio, please navigate to the directory with the chocolateysetup.psm1 and run that in Powershell, followed by Initialize-Chocolatey.
    Upgrade is the same, just run Initialize-Chocolatey again.
    Once you've run initialize or upgrade, you can uninstall this package from the local project without affecting your chocolatey repository.
    "@ | Write-Host

Virus Scan Results


Chocolatey Pro provides runtime protection from possible malware.


This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Rob Reynolds
  • The Chocolatey Team


RealDimensions Software, LLC - 2011-Present


Release Notes

See all -


  • Fix - Allow passing install arguments again (regression in 0.9.9 series) - see #150
  • Fix - Allow apostrophes to be used as quotes - quoting style that worked with previous client - see #141
  • Fix - Shims write errors to stderr - see #142 and ShimGen #14


  • Upgrade -r should always return a value - see #153


  • Fix - Get-BinRoot broken - see #144


This also includes issues that were being tracked in the old Chocolatey repository: Chocolatey 0.9.9.

The two links above will not capture everything that has changed, since this is a complete rewrite. We broke everything. If this were a v1+, it would be a major release. But we are less than v1, so 0.9.9 it is! ;)

Okay, so we didn't really break everything. We have maintained nearly full compatibility with how you pass options into choco, although the output may be a bit different (but better, we hope) and in at least one case, additional switches (or a feature setting) is/are required - we limited this to security related changes only.

We also fixed and improved a bunch of things, so we feel the trade off is well worth the changes.

We'll try to capture everything here that you should know about. Please call choco -? or choco.exe -h to get started.


  • Known Issues
  • TEMPORARY install all is missing - this is expected to be back in 0.9.10 - see #23
  • Alternative sources (webpi,ruby,python,cygwin, windowsfeature) do not work yet. This is expected to be fixed in 0.9.10 - see #14
  • Progress bar is missing when downloading until we are using internal posh components for Packages - see #56
  • See Feature Parity for items not yet reimplemented from older PowerShell Chocolatey client (v0.9.8.32 and below).


  • [Security] Prompt for confirmation: For security reasons, we now stop for confirmation before changing the state of the system on most commands. You can pass -y to confirm any prompts or set a value in the config that will globally confirm - see #52 (NOTE: This is one of those additional switches we were talking about)
  • [Security] If your default installation is still at c:\Chocolatey, this version will force a move to ProgramData and update the environment settings - see #7
  • Configuration Breaking Changes:

    1. You now have one config file to interact with in %ChocolateyInstall%\config - your user config is no longer valid and can be removed once you migrate settings to the config.

    2. The config will no longer be overwritten on upgrade.

    3. Choco no longer interacts with NuGet's config file at all. You will need to reset all of your apiKeys (see features for apikey). On the plus side, the keys will work for all users of the machine, unlike NuGet's apiKeys (only work for the user that sets them).

    4. This also means you can no longer use useNugetForSources. It has been removed as a config setting.

  • Packaging Changes:

    1. Choco now installs packages without version numbers on folders. This means quite a few things...

    2. Upgrading packages doesn't install a new version next to an old version, it actually upgrades.

    3. Dependencies resolve at highest available version, not the minimum version as before - see Chocolatey #415

  • Package Maintenance Changes:

    1. Read the above about apikey changes

    2. Read above about dependency resolution changes.

  • Deprecated/Removed Commands:

    1. installmissing has been removed. It was deprecated awhile ago, so this should not be a surprise.

    2. choco version has been deprecated and will be removed in v1. Use choco upgrade pkgName --noop or choco upgrade pkgName -whatif instead.

    3. Write-ChocolateySuccess, Write-ChocolateyFailure have been deprecated.

    4. update is now upgrade. update has been deprecated and will be removed/replaced in v1. Update will be reincarnated later for a different purpose. Hint: It rhymes with smackage pindexes.



Probably a lot of bug fixes that may not make it here, but here are the ones we know about.


  • [Security] Allow keeping c:\chocolatey install directory with environment variable - see #17
  • [Security] Require switch on unofficial build - see #36
  • Install script updates - see #7
  • Ensure Chocolatey pkg is installed properly in lib folder - This means you can take a dependency on a minimum version of Chocolatey (we didn't like that before) - see #19
  • Uninstall - allow abort - see #43
  • Support for HTTPS basic authorization - see Chocolatey #128
  • Smooth out success/failure logging - see Chocolatey #154
  • Add $env:CHOCOLATEY_VERSION - see Chocolatey #251
  • Replace ascii cue with visual cues - see Chocolatey #376
  • Uninstall all versions of an app - see Chocolatey #389
  • Add parameters in packages.config files - see Packages.config, Chocolatey #472, and #10
  • Choco pack should support -version - see Chocolatey #526
  • Enhancements to Start-ChocolateyProcessAsAdmin - see Chocolatey #564
  • Install-ChocolateyFileAssociation - add label to new file types - see Chocolatey #564
  • Clean up the verobsity of Chocolatey - see Chocolatey #374
  • Compact choco upgrade --noop option - see Chocolatey #414
  • Remove references to the Chocolatey gods - see Chocolatey #669
  • Shims now have noop (--shimgen-noop) and help (--shimgen-help) switches - see ShimGen #8 and ShimGen #10
  • Shims will terminate underlying process on termination signal - see ShimGen #11
  • Shims now have gui (--shimgen-gui) and exit (--shimgen-exit) switches - see ShimGen #13 and ShimGen #12
  • Dat help menu tho. I mean srsly guise - see Chocolatey #641

Version History

Version Downloads Last updated Status
Chocolatey 0.10.15-beta-20190531 700 Friday, May 31, 2019 approved
Chocolatey 0.10.14 506638 Thursday, May 30, 2019 approved
Chocolatey 0.10.14-beta-20190418 5148 Thursday, April 18, 2019 approved
Chocolatey 0.10.14-beta-20190402 2553 Tuesday, April 2, 2019 approved
Chocolatey 0.10.14-beta-20190321 2119 Friday, March 22, 2019 approved
Chocolatey 0.10.13 7573822 Friday, March 15, 2019 approved
Chocolatey 0.10.12 151857 Friday, March 15, 2019 approved
Chocolatey 0.10.12-beta-20181011 14772 Friday, October 12, 2018 approved
Chocolatey 0.10.12-beta-20181009 508 Tuesday, October 9, 2018 approved
Show More

Discussion for the Chocolatey Package

Ground rules:

