All Versions
Latest Version
Avg Release Cycle
97 days
Latest Release
761 days ago

Changelog History
Page 3

  • v0.10.1 Changes

    September 19, 2016

    ๐Ÿš€ We're dubbing this the "Shhh! Keep that secret please" release. We've found that when passing in passwords and other sensitive arguments, those items can end up in the logs in clear text. We've addressed this in #948 and #953. When it comes to passing sensitive arguments through to native installers, you can set up environment variables with those sensitive args and pass those arguments directly through to Start-ChocolateyProcessAsAdmin. If you prefer a better experience, the licensed version allows passing sensitive options directly through choco.exe as --install-arguments-sensitive and --package-parameters-sensitive. Read more in the Licensed CHANGELOG.

    ๐Ÿš€ Perhaps the biggest improvement in this release is that Chocolatey will automatically look to see if it can download binaries over HTTPS when provided an HTTP url. If so, Chocolatey will switch to downloading the binaries over SSL. This provides better security in downloading and knowing you are getting the binary from the source location instead of a possible man in the middle location, especially when the package does not provide checksums for verification.

    ๐Ÿ”’ Another improvement you may not even notice, but we think you will love is that Chocolatey now supports TLS v1.2 transport which presents a nice transparent increase in security. You will need to have at least .NET Framework 4.5 installed to take advantage of this feature.


    • [Security] Support TLS v1.2 - see #458
    • [Security] Attempt to download packages via HTTPS connection - see #746
    • [Security] Pro/Business - Pass sensitive arguments to installers - see #948
    • Search (and info) by version - see #935

    ๐Ÿ› BUG FIXES

    • [Security] Fix - Passwords in command line options are logged in clear text - see #953
    • [Security] Fix - For PowerShell v2 - if switch down to SSLv3 protocol fails, go back to original protocol - see #958
    • Fix - Unzipping to ProgramFiles/System32 is Subject to File System Redirection - see #960
    • Fix - Run without login - see #945
    • Fix - Support Long Paths - see #934
    • Fix - help should not issue warning about elevated command shell - see #893
    • Fix - Licensed Feed cannot be disabled - see #959
    • Fix - Choco with unknown command should show help menu - see #938
    • Fix - Get-FtpFile error when file is missing (called through Get-ChocolateyWebFile) - see #920
    • Fix - Skip Get-WebFileName for FTP - see #957
    • Fix - Chocolatey-InstallChocolateyPackage fix for double chocolatey folder name is not also applied to the passed in file name - see #908
    • Fix - Start-ProcessAsAdmin - working directory should be from the location of the executable - see #937
    • [POSH Host] Fix - PowerShell Host - Package scripts setting values can affect packages that depend on them - see #719
    • Fix - Transactional install - pending check may fail if the lib folder doesn't exist - see #954
    • Fix - Start-ChocolateyProcessAsAdmin Module Import for PowerShell causes errors - see #901


    • Transactional Install - Improve concurrent operations (pending) - see #943
    • Uninstall-ChocolateyPackage should set unrecognized fileType to exe - see #964
    • Powershell functions - Allow access to package title, not only ID - see #925
    • Option to apply package parameters / install arguments to dependent packages - see #839
    • Get-ChocolateyWebFile download check enhancements - see #952
    • Do not treat unknown checksum types as MD5 - see #932
    • Pro/Business - Install-ChocolateyPackage - UseOriginalLocation - see #950
    • Auto determine checksum type - see #922
    • Ensure PowerShell functions have parameter name parity - see #941
    • Output from installer should go to verbose log - see #940
  • v0.10.0 Changes

    August 11, 2016

    ๐Ÿ”’ What was planned for is now 0.10.0. This is due partly to a breaking change we are making for security purposes and a move to provide better a better versioning scheme for the remainder of the sub-v1 versions of Chocolatey. Instead of 0.y.z.0 being considered where major verions occur in the sub 1 series, 0.y.0 will now be considered where those major versions occur. We also are moving right along towards v1 (and hope to be there in 2017).

    ๐Ÿ”’ 0.10.0 carries the fixes for and includes a major security enhancement (checksum requirement).


    • [Security] Checksum requirement and enhancements - see #112

    ๐Ÿš€ Checksums in package scripts are meant as a measure to validate the originally intended downloaded resources used in the creation of a package are the same files that are received at a future date. This also ensures that the same files that are checked by all parts of moderation (if applicable) are the same files that are received by users for a package. This is seen mostly on the community repository because it is public and packages are subject to copyright laws (distribution rights), which typically requires the package scripts to download software from the official distribution locations. The Chocolatey framework has had the ability to use checksums in package scripts since July 2014.

    What is the requirement? choco will now fail if a package download resources from HTTP/FTP and does not use checksums to verify those downloaded resources. The requirement for HTTP/FTP is #112. We are considering also requiring it for HTTPS (#895) as well. You can optionally set a feature (allowEmptyChecksumsSecure) to ensure packages using HTTPS also use checksums.

    How does this protect the community anymore than before? During moderation review, there is a check of these downloaded binaries against VirusTotal (which verifies these binaries against 50-60+ different virus scanners). The binaries are also verified for installation purposes against a test computer. With an independent 3rd party checksum in the package itself, it guarantees that the files received by a user from those remote sources are the exact same files that were used in the verification process.

    Why the requirement, and why now? This is a measure of protection for the Chocolatey community. HTTP is easy to hack with both DNS poisoning and MITM (man in the middle) attacks. Without independent verification of the integrity of the downloaded resources, users can be left susceptible to these issues. We've been planning a move to require checksums for awhile now, with a planned longer and smoother transition for package maintainers to get packages updated to reduce breakages. Unfortunately there was a recent event with FOSSHub getting hacked (the community repository had 8 possibly affected packages and we quickly took action), which necessitated a need for us to move in a much swifter fashion to ensure the protection of the community sooner, rather than later. The changes in Chocolatey represented by the checksum changes are a major step in the process to ensure protection. Requiring for HTTPS as well will mitigate any future compromises of software distribution sites that are used with Chocolatey packages.

    ๐Ÿ“ฆ Can I shut this behavior off or opt out per package? You can shut off the checksum requirement by enabling the feature allowEmptyChecksums. This will return Chocolatey to previous behavior. We strongly recommend against it.

    โฌ†๏ธ You can shut it off or turn it per package install/upgrade with --allow-empty-checksums and --require-checksums, respectively. See /

    ๐Ÿ“ฆ You can also disable the feature allowEmptyChecksumsSecure to enforce checksums for packages that download from secure locations (HTTPS).

    Other things I should know? Users also now have the ability to pass their own checksums and checksumtypes into the install. See /



    • Pro/Business - Download a package without installing it - see #108

    ๐Ÿ› BUG FIXES

    • Fix - Installing choco on Windows 10 Vagrant box stops Vagrant from being able to manage the box - see #834
    • Fix - 64bit 7z.exe on 32bit system in chocolatey\tools - see #836
    • Fix - [POSH Host] PowerShell exit code does not reset between packages in a single run - see #854
    • Fix - Uninstall-ChocolateyZipPackage is failing - see #871
    • Fix - "C:\Program Files\WindowsPowerShell\Modules" is missing in PSModulePath for cmd.exe #830
    • Fix - Environment variables update fixes #840
    • Fix - Handle null items better - see #853
    • Fix - HKCU may not have Environment (Install of Chocolatey) - see #375
    • Fix - Progress of download does not clear the whole output line - see #875
    • Fix - Wrong download progress reported during package upgrade - see #872
    • Fix - Uninstall not supporting side-by-side => ChocolateyUninstall.ps1 not run - see #862
    • Fix - Uninstall ignores the version parameter - see #861
    • Fix - Search by exact or by id only is case sensitive for remote sources - see #889
    • Fix - Deprecated links inserted in .nuspec files created by choco new ... - see #870
    • Fix - Get-OSArchitectureWidth doesn't do what it says it does - see #828
    • Fix - When Choco fails to get a package from NuGet Core, fail the package with exit code 1 - see #867
    • Fix - Illegal characters in path - see #857
    • Fix - Get-OSArchitectureWidth doesn't do what it says it does - see #828
    • Fix - Pro/Business - Choco install config file fails on licensed assembly - see #866
    • Fix - DISM /all doesn't run anywhere but Windows 6.2 -- no dependencies get installed - see #897


    • Do not install tab completion (edit of profile) under certain conditions - see #833
    • Choco install with packages.config should print out the packages to install - see #878
    • Larger default log file size and retention - see #852
    • Allow getting installer type to be overridden - see #885
    • Pack - Add optional output folder option - see #598
    • Little command name correction on init.ps1 - see #595
    • Tab completion - don't query if there is a file in the folder that meets completion - see #847
  • v0.9.10 Changes

    June 17, 2016

    ๐Ÿ“„ Chocolatey Logo

    ๐Ÿš€ The "I got 99 problems, but a package manager ain't one" release. With the release of 0.9.10 (or if you prefer, we're about to make everything 100% better in your Windows package management world. We've addressed over 100 features and bugs in this release. We looked at how we could improve PowerShell and we've come out with a competely internal host that can Prompt and Read-Host in a way that times out and selects default values after a period of time. Speaking of PowerShell, how about some tab completion choco <tab> to choco install node<tab>? How about never having to close and reopen your shell again?

    ๐Ÿ Alternative sources (-source webpi, -s windowsfeature, etc) are back! I mean, am I right?! Have you heard of auto uninstaller? If Chocolatey has installed something that works with Programs and Features, Chocolatey knows how to uninstall it without an uninstall script about 90+% of the time. This feature was in beta for the 0.9.9 series, it is on by default in 0.9.10 (unless you disabled it after trying it, you will need to reenable it, see choco feature for more details).

    Here's one you probably never knew existed - extensions. Chocolatey has had the ability to extend itself by adding PowerShell modules for years, and most folks either didn't know it existed or have never used them. We've enhanced them a bit in preparation for the licensed version of Chocolatey.

    ๐Ÿ“ฆ We redesigned our choco new default packaging template and we've made managing templates as easy as managing packages.

    ๐Ÿ‘€ choco search/choco list has so many enhancements, you may not need to visit dot org again. See it in action.

    ๐Ÿš€ There are 150 tickets closed for this release! We've included remediation steps for when a breaking change affects you. Mostly if you have been using Chocolatey in a recommended way, you won't even notice any adverse changes. There are a number of things we thought to highlight, and quite a few security enhancements coming in this release (look for the [Security] tag on the ticket summary).


    • Only fail automation scripts (chocolateyInstall.ps1) if the script returns non-zero exit code - see #445

    ๐Ÿ“ฆ The 0.9.8 series would only fail a package with terminating errors. The 0.9.9 series took that a bit further and started failing packages if anything wrote to stderr. It turns out that is a bad idea. Only when PowerShell exits with non-zero (which comes with terminating errors) should the package fail due to this. If you need the old behavior of the 0.9.9 series, you can get it back with a switch (--fail-on-standard-error and its aliases) and/or a feature flip (failOnStandardError).

    • Fix - Force reinstall, force upgrade, and uninstall should delete the download cache - see #590

    If you set a custom cache directory for downloads, it will no longer use a "chocolatey" subdirectory under that. You may need to make any adjustments if this is going to affect you.

    • Exit with the same exit code as the software being installed - see #512

    There are more exit codes from Chocolatey now that indicate success -0, 1605, 1614, 1641, and 3010. You may need to adjust anything you were using that would only check for 0 and nonzero. ๐Ÿ“ฆ If you need the previous behavior, be sure to disable the feature usePackageExitCodes or use the --ignore-package-exit-codes switch in your choco commands.

    • PowerShell module functions adjusted for automatic documentation - see #697

    If you were using any of the functions in a non-recommended way or not compliant with the examples, you are going to find breakages in the functions as some of the things that were called out as non-optional are now enforced. This shouldn't affect most folks.

    • [Security] Explicit permissions - remove inheritance/lock down to admins - see #398

    ๐Ÿ”’ This further restricts the default installation location by removing all permissions and inheritance of permissions, explicitly giving Administrator/LocalSystem to Full access, and Users are granted Read and Execute. In prior installations, we ensured Modify access to the installing user, but that has been removed for security reasons. Should you need the previous behavior, set $env:ChocolateyInstallAllowCurrentUser="true".



    • Alternative Sources - see #14
    • [POSH Host] Use Internal PowerShell Host - see #8
    • Run a script before uninstall/upgrade (chocolateyBeforeModify.ps1) to allow for things like services to shutdown - see #268
    • Manage package templates with a specially named package and special package folder - see #542
    • Support for custom headers - see #332
    • [Security] Show moderation-related information in search results - see #493
    • New Helper - Get-ToolsLocation helper (replacement for Get-BinRoot) - see #631
    • Choco list/search should have exact filter search - see #453
    • RefreshEnv (Refresh Environment Variables) Should also work in PowerShell - see #664
    • Provide PowerShell tab completion for Chocolatey - see #412
    • [Security] Sign the powershell scripts and assemblies - see #501
    • Add a choco info command to show info for one package - see #644
    • Mark packages pending until install completes successfully - see #198
    • Resolve sources by name - see #356
    • Uninstall-ChocolateyEnvironmentVariable function - see #772
    • Get-UninstallRegistryKey function - see #739
    • Pro/Business - Ubiquitous Install Directory Switch - see #258
    • Pro/Business - Runtime Virus Scanning - see virus scanning
    • Pro/Business - Private CDN cache for downloads - see private CDN cache
    • Pro/Business - Sync "choco installed status" with "Windows installed status" - see #567

    ๐Ÿ› BUG FIXES

    • [Security] Fix - Only load the Chocolatey PowerShell module from a known location - see #560
    • [Security] Fix - Package source authentication at http://location/path doesn't also use http://location/ (base url) - see #466
    • [Security] Fix - When defining a proxy without credentials - proxy password is shown in plain text - see #503
    • [Security] Fix - Fully qualify shutdown command - see #702
    • [Security] Fix - MSI packages fail install with Could not find 'msiexec' - see #723
    • Fix - Force should set allow-downgrade to true - see #585
    • Fix - Do not use NuGet package cache - see #479
    • Fix - Pack doesn't include chocolatey-specific metadata - see #607
    • Fix - TEMP environment variable is 8.3 Path on some systems - see #532
    • Fix - $packageName should be present for zip uninstalls in uninstall script template - see #534
    • Fix - Debug/Verbose messages not logged in automation scripts (chocolateyInstall.ps1) - see #520
    • Fix - Escape log output for variables that have data from external sources - see #565
    • Fix - Choco new silentargs can't pass in args in the param=value format - see #510
    • Fix - Exception if no source is enabled - see #490
    • Fix - Chocolatey command help output written to standard error instead of standard out - see #468
    • Fix - Logger doesn't clear cached NullLoggers - see #516
    • Fix - DISM "/All" argument in the wrong position - see #480
    • Fix - Pro/Business - Installing/uninstalling extensions should rename files in use - see #594
    • Fix - Running Get-WebFileName in PowerShell 5 fails and sometimes causes package errors - see #603
    • Fix - Merging assemblies on a machine running .Net 4.5 or higher produces binaries incompatible with .Net 4 - see #392
    • Fix - [API] - Incorrect log4net version in chocolatey.lib dependencies - see #390
    • [POSH Host] Fix - Message after Download progress is on the same line sometimes - see #525
    • [POSH Host] Fix - PowerShell internal process - "The handle is invalid." - see #526
    • [POSH Host] Fix - The handle is invalid - when output is being redirected and a package attempts to write to a filestream - see #572
    • [POSH Host] Fix - Write-Host adding multiple line breaks - see #672
    • [POSH Host] Fix - PowerShell Host doesn't show colorization overrides - see #674
    • [POSH Host] Fix - $profile is empty string when installing packages - does not automatically install the ChocolateyProfile - see #667
    • [POSH Host] Fix - Getting LCID doesn't work properly with the built-in PowerShell - see #741
    • [POSH Host] Fix - Host.Version should return actual PowerShell version - see #708
    • Fix - Verbose shows in output on debug switch - see #611
    • Fix - Get-ChocolateyUnzip captures files that don't belong to the package / Unzip should not do a full disk scan - see #616 and #155
    • Fix - Package succeeds but software install silently fails when Install-ChocolateyInstallPackage has the wrong arguments - see #629
    • Fix - ShimGen handling of spaces and arguments that have shimgen in them - see #647
    • Fix - PowerShell v2 - Choco installer messages can't actually be warnings (causes FileStream errors) - see #666
    • Fix - Installing chocolatey removes $env:PSModulePath changes for current PowerShell session - see #295
    • Fix - Notice for Get-BinRoot deprecation won't be displayed - see #673
    • Fix - choco new creates a bad ChocolateyUninstall.ps1 script which does not work. - see #460
    • Fix - ShimGen fails when file metadata has strings that need literals - see #677
    • Fix - Install-ChocolateyPath Expands Variables in PATH, Overwriting Preexisting Variables - see #303
    • Fix - Install-ChocolateyShortcut gives invalid warning when target is a web url - see #592
    • Fix - Argument Parsing failures should be reported as warnings and not debug messages - see #571
    • Fix - choco pack returns zero exit code when Nuget.Core validation errors - see #469
    • Fix - Install-ChocolateyPath updates PATH to REG_SZ, which may break using Windows dir and system32 tools - see #699
    • Fix - Removing environment variables sets empty environment variables - see #724
    • Fix - Environment Variable Changes Require Reboot - see #728
    • Fix - Get-WebFileName determines strange file name - see #727
    • Fix - Package params are also applied to dependent package - see #733
    • Fix - Use package name/version from environment, not parameters - see #751
    • Fix - Get-WebFileName Does Not Match on Invalid Characters - see #753
    • Fix - choco new cannot introduce multistage folder hierarchy template - see #706
    • Fix - Empty $env:ChocolateyToolsLocation combine error - see #756
    • Fix - Installing chocolatey removes $env:PSModulePath changes for current powershell session - see #295
    • Fix - Some environment variables are set too early for options/switches to have an effect - see #620
    • [API] Fix - Issue when attempting to execute run command through API - see #769
    • Fix - Logging of upgrade messages - placement of some messages is incorrect - see #557
    • Fix - Get-WebFile fails with - The term '//continue' is not recognized as the name of a cmdlet - see #789
    • Fix - Unable to read registry snapshot file - see #487
    • Fix - Pro/Business - Licensed version has an incorrect dependency on PowerShell assemblies and will only load v3 and above - see #799
    • Fix - Exit codes in package scripts should work - see #802
    • Fix - Running choco new creates a bad nuspec - see #801


    • AutoUninstaller is on by default - see #308
    • Use the actual download file name instead of providing one - see #435
    • Unset Configuration Values - see #551
    • Ability to run "choco upgrade all" ignoring specific packages - see #293
    • Extensions enhancements - see #588
    • Show human-readable file sizes when downloading - see #363
    • [Security] Warn about environment changes - see #563
    • Warn when execution timeout has elapsed - see #561
    • Update nuspec to make it easier to get started - see #535
    • Suppress verbose output to verbose - like with 7-zip - see #476
    • Choco push moderation message only on push to dot org - see #601
    • Allow tools/bin root to be root of the drive again - see #628
    • File description of ShimGen shims should match original as closely as possible - see #374
    • Shim Generation should automatically detect GUI - see #634
    • Don't show 32 bit wording unless there is explicitly both versions available - see #642
    • Allow passing arbitrary key/value arguments to new command when generating packages from templates - see #658
    • Choco search/list should be able to search just by Id - see #663
    • Search by approved, by not broken, by download cache - see #670
    • Save nuspec files with package installs - see #623
    • Show a prompt character when asking a multiple choice question - see #184
    • When prompting for a user yes/no answer, use a short [y/n] representation - see #181
    • Default package template should include LICENSE.txt and VERIFICATION.txt for packages with binaries - see #675
    • choco list/search aliases for -v - '-detail' and '-detailed' - see #646
    • Log normal output to a secondary log - see #682
    • Display Package test status information on install/upgrade - see #696
    • Report when reboots are necessary from package installs - see #712
    • Report loaded extensions - see #715
    • Exit with specific codes on certain actions - see #707
    • Determine if Downloaded File is HTML or Plain Text - see #649
    • Interactively prompt with timeout on some questions - see #710
    • [POSH Host] Exit code from PowerShell Host should be useful - see #709
    • Update environment for scripts after setting environment variables - see #729
    • Clean up any temp nuget folder actions after NuGet operations - see #622
    • Ensure Web Requests and Responses Do Not Timeout - make configurable - see #732
    • Combine timeout from push and execution timeout as one parameter - see #752
    • Override autouninstaller / failonautouninstaller fail with switches for uninstall - see #515
    • Offer to remove actual package (.install/.portable) when removing meta/virtual package - see #735
    • Provide more info in package summary - see #455
    • Report install location - see #689
    • Track MSI Information Better - see #755
    • Support for client certificates - see #399
    • choco feature list formatting enhancements - see #742
    • choco new --original-template - see #737
    • Update Get-FtpFile with fixes for Get-WebFile - see #765
    • Rename Get-ProcessorBits as a more appropriately named Get-OSArchitectureWidth - see #713
    • Allow passing no 32-bit url and fail the package on 32-bit systems - see #527
    • Enhance Install-ChocolateyShortcut to support WindowStyle, Pin to Taskbar and Run As Administrator checkbox - see #519
    • [Security] Allow hashing files for checksums with FIPS compliant algorithms - see #446
    • After upgrading provide summary of upgraded packages - see #759
    • Web functions - Check for local file and return early - see #781
    • Refresh environment variables after each install - see #439
    • Capture Arguments for a Package during Install/Upgrade - see #358
    • If config update fails, log to debug instead of warn - see #793
    • Remove extra empty lines when doing choco upgrade all - see #796
    • Mention required permissions if user has no access - see #794
    • Pro/Business - Also check for license in User Profile location - see #606
    • Pro/Business - Set download cache information if available - see #562
    • Pro/Business - Allow commands to be added - see #583
    • Pro/Business - Load/Provide hooks for licensed version - see #584
    • Pro/Business - On valid license, add pro/business source automatically - see #604
    • Pro/Business - Add switch to fail on invalid or missing license - see #596
    • Pro/Business - add ignore invalid switches/parameters - see #586
    • Pro/Business - Don't prompt to upload file for virus scanning if it is too large - see #695
    • Pro/Business - add 'support' command - see #745
    • Pro/Business - Adjust environment settings warning to suggest upgrade - see #795
    • API - Add the ability to retrieve package count for a Source - see #431
    • API - Chocolatey Lib still marks vital package information as internal - see #433
    • API - Add paging to list command - see #427
    • API - Choco search should sort by version - see #668
    • API - Switch dll to .NET Client Profile - see #680
  • v0.9.10.3 Changes

    June 23, 2016

    ๐Ÿ› BUG FIXES

    • Fix - Ignore ValidPackage Exit Codes for Real - see #827
    • Fix - Cache folder running under SYSTEM account should be C:\Windows\TEMP - see #826
    • Fix - Built-in 7zip doesn't behave properly - see #775
    • Fix - Successful installer exit codes not recognized by choco should return 0 - see #821
    • Fix - NotSilent fails with "Cannot bind argument to parameter statements because it is an empty string" - see #819
    • Fix - Silent Args being passed as a string array cause package failure - see #808


    • Hold pending check for 10 seconds / provide means of explicitly overriding the transactional install cleanup - see #822
    • Pro/Business - Add runtime skip option to allow skipping the virus scanner - see #786
  • v0.9.10.2 Changes

    June 19, 2016

    ๐Ÿ› BUG FIXES

    • Fix - Chocolatey Licensed is unable to find 0.9.10.x (only - see #814
    • Fix - Logging is broken in some packages due to new TEMP directory - see #813
    • [API] Fix - When performing an Install/Uninstall/Upgrade operation through the API, an error is throw for "chocolatey.resources" - see #811


    • Ensure log file path exists - and fix the log file arguments if necessary - see #758
  • v0.9.10.1 Changes

    June 18, 2016

    ๐Ÿ› BUG FIXES

    • Fix - Cannot bind argument to parameter 'exitCode' because it is null - see #810


    • [Security] Upgrade to 7zip 16.02 to overcome CVE-2016-2334/CVE-2016-2335 - see #812
  • v0.9.9 Changes

    March 03, 2015

    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 and 'cinstm' have been removed. They were deprecated awhile ago, so this should not be a surprise. For equivalent functionality see the plain install/cinst commands.
      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.


    ๐Ÿ› BUG FIXES

    ๐Ÿ›  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
  • v0.9.9.9 Changes

    October 02, 2015

    ๐Ÿš€ With this release you can completely configure choco from the command line (including the priority of sources). Choco now allows you to create custom package templates. Choco has proper proxy support now. We also squashed up some bugs, like the infinite download loop that happens if the connection is lost. We've also improved the installation experience of Chocolatey itself, unpacking all of the required setup files in the chocolatey package and improving the messaging output during the bootstrapping process. Chocolatey also doesn't try to write config updates every command, unless something actually changes in the config file. And last but not least for mentions, the issue of choco not recognizing itself as needing upgraded after being installed by the bootstrapper is now fixed.


    • Config Command - see #417
    • Create Custom Package Templates - see #76
    • Proxy Support - see #243

    ๐Ÿ› BUG FIXES

    • Fix - [Security] Remove rollback should validate it exists in choco install backup directory - see #387
    • Fix - Ensure chocolatey is installed into the lib folder during initial install - see #414
    • Fix - Infinite loop downloading files if connection is lost - see #285
    • Fix - list / search results blocking until completion instead of streaming output - see #143
    • Fix - default template install script for MSI silentArgs are bad - see #354
    • Fix - Deleting read-only files fails - see #338 and #263
    • Fix - If the package uses $packageParameters instead of $env:PackageParameters, quotes are removed - see #406
    • Fix - Choco upgrade not downloading new installer if current installer is the same size - see #405
    • Fix - Exit with non-zero code if install/upgrade version and a newer version is installed - see #365
    • Fix - Chocolately can permanently corrupt the config file if an operation is interrupted - see #355
    • Fix - Handle PowerShell's InitializeDefaultDrives Error (that should just be a warning) - see #349
    • Fix - Checksumming can not be turned off by the feature flag - see #33
    • Fix - Process with an id of is not running errors on - see #346
    • Fix - Export cmdlets for automation scripts - see #422


    • [Security] Add SHA-2 (sha256 / sha512) to checksum - see #113
    • Sources should have explicit priority order- see #71
    • Unpack the powershell files just before packaging up the nupkg (Installing chocolatey meta) - see #347
    • API - List --localonly not working by default - see #223
    • API - Expose package results - see #132
    • API - Externalize IPackage and its interfaces - see #353
    • Enhance "Access to path is denied" message on no admin rights - see #177
    • Only update chocolatey.config if there are changes - see #364
    • Modify source when attempting to add a source with same name but different URL - see #88
    • Features should contain description - see #416
    • Chocolatey Installer - removing modules not loaded - see #442
    • Chocolatey Installer - Don't use Write-Host - see #444
    • Set environment variables once configuration is complete - see #420
    • Enhance Package Template for - see #366
  • v0.9.9.8 Changes

    June 26, 2015

    ๐Ÿ› BUG FIXES

    • Fix - [Security] choco install -y C: deletes all files - see #341
    • Fix - Read-Host halts scripts rather than prompt for input - see #219


    • Download Progress Bar is Missing - see #56
  • v0.9.9.7 Changes

    June 20, 2015

    ๐Ÿ“ฆ "Fix Everything. Fix All The Things" - There have been some things bugging us for a long time related to limitations with NuGet, so we decided to fix that. Like nuspec enhancements, that crazy content folder restriction has been removed (I know, right?!), and we're working around badly behaved packages quite a bit more to bring you more feature parity.

    ๐Ÿš€ Let's talk about a couple of big, like really big, BIG features just added with this release. No more packages rebooting Windows. We fixed (#304 / #323) and enhanced up the Auto Uninstaller Service quite a bit to ensure things are working like you would expect (It goes on by default in 0.9.10 - we'll start documenting more about it soon). But wait, there's more! I haven't even told you about the big features yet

    The first big feature is enhancing the nuspec. I mentioned this I know, but now you can use packageSourceUrl in the nuspec to tell folks where you are storing the source for the package! We also added projectSourceUrl, docsUrl, mailingListUrl, and bugTrackerUrl. What's even better is that the community feed has already been enhanced to look for these values. So have the templates from choco new. And it's backwards compatible, meaning you can still install packages that have these added nuspec enhancements without issue (but we will need to provide a fix for Nuget Package Explorer).

    โฌ†๏ธ The second is Xml Document Transformations (XDT), which I think many folks are aware of but may not realize what it can provide. NuGet has allowed transformations for quite awhile to allow you to make changes to an app.config/web.config on install/uninstall. We are following in similar footsteps to allow you to do similar when installing/upgrading packages. We will look for *.install.xdt files in the package (doesn't matter where) and they will apply to configuration files with the same name in the package. This means that during upgrades we won't overwrite configuration files during upgrades that have opted into this feature. It allows you to give users a better experience during upgrades because they won't need to keep making the same changes to the xml config files each time they upgrade your package.


    • Allow XDT Configuration Transforms - see #331
    • Prevent reboots - see #316
    • Enhance the nuspec - first wave - see #205
    • Uninstaller Service Enhancements - see #305

    ๐Ÿ› BUG FIXES

    • When uninstall fails, do not continue removing files - see #315
    • Do not run autouninstaller if the package result is already a failure - see #323
    • Fix - Auto Uninstaller can fail if chocolateyUninstall.ps1 uninstalls prior to it running - see #304
    • Fix - Packages with content folders cannot have a dependency without also having a content folder - see #290
    • Remove ShimGen director files on upgrade/uninstall - see #326
    • If feature doesn't exist, throw an error - see #317
    • Fix - The operation completed successfully on stderr - see #249
    • Fix - When specific nuget version is needed by a package it is the chocolatey version that is used - see #194
    • When installing with *.nupkg, need to get package name from package, not file name - see #90
    • Fix - Choco pin list is not returning a list - see #302
    • Fix - A pin is not created for existing installations (prior to new choco) - see #60


    • Allow upgrade to always install missing packages - see #300
    • Enhance Templates - see #296
    • Always log debug output to the log file - see #319
    • Warn when unable to snapshot locked files - see #313
    • Use %systemroot% in place of %windir%. PATH exceed 2048 breaks choco - see #252
    • Add fault tolerance to registry snapshot checks - see #337