#### Chocolatey

0.10.0 | Updated: 8/11/2016

177,631,518

3,814,990

Maintainer(s):

Software Author(s):

• Rob Reynolds
• The Chocolatey Team

### All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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

>

This package was approved as a trusted package on 8/11/2016.

Description

Chocolatey is a package manager for Windows (like apt-get but for Windows). It was designed to be a decentralized framework for quickly installing applications and tools that you need. It is built on the NuGet infrastructure currently using PowerShell as its focus for delivering packages from the distros to your door, err computer.

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.

### Commands

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

• Help - choco -? or choco command -?
• Search - choco search something
• List - choco list -lo
• Config - choco config list
• Install - choco install baretail
• Pin - choco pin windirstat
• Outdated - choco outdated
• Uninstall - choco uninstall baretail

#### Alternative installation sources:

• 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

#### More

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?

We have some great guidance on how to do that. Where? I'll give you a hint, it rhymes with socks! Docs!

In that mess there is a link to the PowerShell Chocolatey module reference.

tools\chocolateyInstall.ps1
tools\chocolateyInstall\choco.exe
tools\chocolateyInstall\choco.exe.ignore
tools\chocolateyInstall\helpers\chocolateyInstaller.psm1
tools\chocolateyInstall\helpers\chocolateyProfile.psm1
tools\chocolateyInstall\helpers\chocolateyScriptRunner.ps1
tools\chocolateyInstall\helpers\ChocolateyTabExpansion.ps1
tools\chocolateyInstall\helpers\functions\Format-FileSize.ps1
tools\chocolateyInstall\helpers\functions\Get-CheckSumValid.ps1
tools\chocolateyInstall\helpers\functions\Get-ChocolateyUnzip.ps1
tools\chocolateyInstall\helpers\functions\Get-ChocolateyWebFile.ps1
tools\chocolateyInstall\helpers\functions\Get-EnvironmentVariable.ps1
tools\chocolateyInstall\helpers\functions\Get-EnvironmentVariableNames.ps1
tools\chocolateyInstall\helpers\functions\Get-FtpFile.ps1
tools\chocolateyInstall\helpers\functions\Get-OSArchitectureWidth.ps1
tools\chocolateyInstall\helpers\functions\Get-ToolsLocation.ps1
tools\chocolateyInstall\helpers\functions\Get-UACEnabled.ps1
tools\chocolateyInstall\helpers\functions\Get-UninstallRegistryKey.ps1
tools\chocolateyInstall\helpers\functions\Get-VirusCheckValid.ps1
tools\chocolateyInstall\helpers\functions\Get-WebFile.ps1
tools\chocolateyInstall\helpers\functions\Get-WebFileName.ps1
tools\chocolateyInstall\helpers\functions\Install-BinFile.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyEnvironmentVariable.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyFileAssociation.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyInstallPackage.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyPackage.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyPath.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyPowershellCommand.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyShortcut.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyVsixPackage.ps1
tools\chocolateyInstall\helpers\functions\Install-ChocolateyZipPackage.ps1
tools\chocolateyInstall\helpers\functions\Install-Vsix.ps1
tools\chocolateyInstall\helpers\functions\Set-EnvironmentVariable.ps1
tools\chocolateyInstall\helpers\functions\Set-PowerShellExitCode.ps1
tools\chocolateyInstall\helpers\functions\Uninstall-BinFile.ps1
tools\chocolateyInstall\helpers\functions\Uninstall-ChocolateyEnvironmentVariable.ps1
tools\chocolateyInstall\helpers\functions\Uninstall-ChocolateyPackage.ps1
tools\chocolateyInstall\helpers\functions\UnInstall-ChocolateyZipPackage.ps1
tools\chocolateyInstall\helpers\functions\Update-SessionEnvironment.ps1
tools\chocolateyInstall\helpers\functions\Write-ChocolateyFailure.ps1
tools\chocolateyInstall\helpers\functions\Write-ChocolateySuccess.ps1
tools\chocolateyInstall\helpers\functions\Write-FileUpdateLog.ps1
tools\chocolateyInstall\redirects\choco.exe
tools\chocolateyInstall\redirects\choco.exe.ignore
tools\chocolateyInstall\redirects\chocolatey.exe
tools\chocolateyInstall\redirects\chocolatey.exe.ignore
tools\chocolateyInstall\redirects\cinst.exe
tools\chocolateyInstall\redirects\cinst.exe.ignore
tools\chocolateyInstall\redirects\clist.exe
tools\chocolateyInstall\redirects\clist.exe.ignore
tools\chocolateyInstall\redirects\cpack.exe
tools\chocolateyInstall\redirects\cpack.exe.ignore
tools\chocolateyInstall\redirects\cpush.exe
tools\chocolateyInstall\redirects\cpush.exe.ignore
tools\chocolateyInstall\redirects\cuninst.exe
tools\chocolateyInstall\redirects\cuninst.exe.ignore
tools\chocolateyInstall\redirects\cup.exe
tools\chocolateyInstall\redirects\cup.exe.ignore
tools\chocolateyInstall\redirects\cver.exe
tools\chocolateyInstall\redirects\cver.exe.ignore
tools\chocolateyInstall\redirects\RefreshEnv.cmd
tools\chocolateyInstall\tools\7z.dll
tools\chocolateyInstall\tools\7z.exe
tools\chocolateyInstall\tools\7z.exe.ignore
tools\chocolateyInstall\tools\7z.exe.manifest
tools\chocolateyInstall\tools\checksum.exe
tools\chocolateyInstall\tools\checksum.exe.config
tools\chocolateyInstall\tools\checksum.exe.ignore
tools\chocolateyInstall\tools\detector.zip
tools\chocolateyInstall\tools\shimgen.exe
tools\chocolateyInstall\tools\shimgen.exe.ignore
tools\chocolateysetup.psm1
tools\init.ps1

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.

Chocolatey 0.10.15-beta-20190531 747 Friday, May 31, 2019 Approved
Chocolatey 0.10.14 506737 Thursday, May 30, 2019 Approved
Chocolatey 0.10.14-beta-20190418 5167 Thursday, April 18, 2019 Approved
Chocolatey 0.10.14-beta-20190402 2566 Tuesday, April 2, 2019 Approved
Chocolatey 0.10.14-beta-20190321 2134 Friday, March 22, 2019 Approved
Chocolatey 0.10.13 7590516 Friday, March 15, 2019 Approved
Chocolatey 0.10.12 151913 Friday, March 15, 2019 Approved
Chocolatey 0.10.12-beta-20181011 14882 Friday, October 12, 2018 Approved
Chocolatey 0.10.12-beta-20181009 524 Tuesday, October 9, 2018 Approved

## 0.10.0

What was planned for 0.9.10.4 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 0.9.10.4 and includes a major security enhancement (checksum requirement).

### BREAKING CHANGES

• [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 https://chocolatey.org/docs/commands-install / https://chocolatey.org/docs/commands-upgrade.

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 https://chocolatey.org/docs/commands-install / https://chocolatey.org/docs/commands-upgrade. You can also disable allowEmptyChecksumsSecure to ensure HTTPS checksums are also .

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

### IMPROVEMENTS

• 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

## 0.9.10.3

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

### IMPROVEMENTS

• 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

## 0.9.10.2

### BUG FIXES

• Fix - Chocolatey Licensed is unable to find 0.9.10.x (only 0.9.10.0) - 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

### IMPROVEMENTS

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

## 0.9.10.1

### BUG FIXES

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

### IMPROVEMENTS

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

## 0.9.10

The "I got 99 problems, but a package manager ain't one" release. With the release of 0.9.10 (or if you prefer 0.9.10.0), 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 &lt;tab&gt; to choco install node&lt;tab&gt;? 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.
* search -v provides moderation related information and a world of nuspec information
* search by id only
* search by id exact
* sort by version
* search with paging

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

### BREAKING CHANGES

• 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". ### KNOWN ISSUES ### FEATURES • 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 - 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

### IMPROVEMENTS

• AutoUninstaller is on by default - see #308
• Unset Configuration Values - see #551
• Ability to run "choco upgrade all" ignoring specific packages - see #293
• Extensions enhancements - see #588
• [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
• 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
• 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 - Don't prompt to upload file for virus scanning if it is too large - see #695
• 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

This package has no dependencies.

Discussion for the Chocolatey Package