#### Chocolatey

0.10.4 | Updated: 3/30/2017

177,631,518

173,852

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 3/30/2017.

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\helpers\functions\Write-FunctionCallLogMessage.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.dll.manifest
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.4

We're dubbing this the "10-4 good buddy" release. We've added some major functionality and fixes we think you are going to find top notch - dare we say as smooth as really expensive chocolate? A lot of work for this release has been provided by the community. Remember that Chocolatey is only as good as the support that comes from the community! Be sure to thank other community members for the awesome that is Chocolatey and Chocolatey 10-4. We've closed over 30 bugs and added 39 enhancements!

Proxy support just got some major enhancements with the ability to not only specify proxy information at runtime, but also to set bypass lists and bypassing on local connections and configure source repositories to bypass proxies. A major issue with changing command execution timeout was just fixed. And there used to be a tiny chance you might corrupt the choco config when running multiple choco processes -but now that is much better handled.

We've also made package itself display download progress, which is great when software binaries are embedded in packages. For you folks looking to remove any progress (like when using Vagrant), now you can use --no-progress. When NuGet.Core has issues, those issues will have more visibility into why things are failing without needing a debugging log. Speaking of some extreme visibility, see network traffic with --trace.

We've got a few possible breaking changes that could affect you, see what we've written about them below.

This also marks the first release that uses the Chocolatey Software digital certificate for signing instead of the RealDimensions Software, LLC certificate.

Another major feature released in preview is using remembered arguments on upgrade. This is in preview in 0.10.4 and will be turned to 'on' automatically in a future release. We are going to be continually making it better and won't turn it on by default until it is ready. If you want to turn it on and start using it, once you have 0.10.4 installed, run choco feature enable -n useRememberedArgumentsForUpgrades. You can also do this per command with --use-remembered-arguments. You can also turn it off per command with --ignore-remembered-arguments. We've also really described a lot of important considerations and thoughts related to using this so there are no surprises. Please do read the issue notes at length if you plan to use this feature to reduce confusion.

### BREAKING CHANGES

• Run with highestAvailable Execution Level by default - see #1054

One longstanding request with Chocolatey was to have it always request admin privileges before running. This has been a hope that it would cut down on the accidental runs of Chocolatey in a command shell that is not elevated and needing to open one that is elevated. This UAC (User account control) setting is handled by something called an application manifest (app.manifest). We had it set to "asInvoker", or run with the context of the user that ran the command. We've moved this to "highestAvailable", which means if you are a non-admin, it will just run under your context, but if you are an admin in a non-elevated shell, it will ask for elevated permissions to run. There is also "requireAdministrator", which locks execution down to administrators only.

Moving to "highestAvailable" allows for that asking of privileges that you are used to, up front before it runs. However one additional thing we did here was give you more control over this setting now. We used to embed the app manifest into choco.exe. We now set it next to choco.exe (base install under $env:ChocolateyInstall, you will find choco.exe.manifest) so you have more freedom to adjust those execution levels as you see fit. There is one catch, you will need to do it on every install/upgrade of Chocolatey until #1206 is implemented. • When a prerelease is installed, it should upgrade to latest prerelease unless excluded - typically seen in choco upgrade all - see #686 When you run choco upgrade all, it never catches the prereleases. However if you run choco upgrade all --pre, it may upgrade some of your stable installs to prereleases. Neither of these situations are desirable. So by default, we've made it so that choco upgrade all just does the right thing, which is to upgrade your stable releases to the latest stable release and your prerelease packages will upgrade to the absolute latest available, whether that be stable or prerelease. If you need to change the behavior back to the old way for upgrade all, simply add the --exclude-prerelease option. • Fix - Passing Allow Downgrade To upgrade against a prerelease may downgrade it to last stable version - see #1212 This is a bug fix that was allowing a prerelease to be downgraded accidentally to the last stable version if you ran choco upgrade somepackage --allow-downgrade without a particular version and without --pre. Now while this would be less affected with #686 above, it could still happen. It's a bug. The only reason this was marked as breaking change is that someone could be depending on the buggy behavior. So heads up, this bug is now fixed. If you are attempting to downgrade, make sure you specify the version you want it to go down to. ### FEATURES • [Security][Preview] Use Remembered Arguments for a Package During Upgrades - You must opt in for this to work - see #797 • Show download progress for the packages themselves - see #1134 • Set Explicit Proxy Bypass List / Bypass On Local - see #1165 • Option/feature to stop installation when a package fails - see #1151 • Add File64 to Install-ChocolateyInstallPackage and Get-ChocolateyUnzip - see #1187 ### BUG FIXES • [Security] Fix - PowerShell sees authenticode hash as changed in scripts that were signed with Unix Line Endings (LF) - unable to use AllSigned - see #1203 • [Security] Fix - chocolatey setup - Use https for downloading .NET Framework 4x if not installed - see #1112 • Fix - chocolatey.config gets corrupted when multiple processes access simultaneously - see #1047 • Fix - "commandExecutionTimeoutSeconds" always reverts to 2700 when deprecated config setting is 0 - see #1059 • Fix - Allow Chocolatey version check with FIPS - see #1193 • Fix - Chocolatey doesn't always decompress downloads appropriately (support automatic decompression) - see #1056 • Fix - Load built-in Chocolatey functions, then load extensions - see #1200 • Fix - Use provided checksum type - see #1018 • Fix - MSU fails to install with space in path - see #1177 • Fix - Unable to disable failOnInvalidOrMissingLicense feature - see #1069 • Fix - PowerShell (Start-ChocolateyProcessAsAdmin) should only import the installerModule and not the profile - see #1013 • Fix - Automatic Uninstaller should skip when uninstaller executable does not exist - see #1035 • Fix - Package installation often fails with ERROR: You cannot call a method on a null-valued expression - see #1141 • Fix - Text file determination fails to throw an error because it catches it - see #1010 • Fix - Delete the .istext file before the content-type check - see #1012 • Fix - new command - don't add unparsed options as the name - see #1085 • Fix - Proxy settings ignored for local connections - see #497 • Fix - RefreshEnv / Update-SessionEnvironment changes current user to SYSTEM - see #902 • Fix - Set-EnvironmentVariable writes an error when installing Chocolatey as SYSTEM - see #1043 • Fix - Get-FtpFile fails with integer overflow when downloading file more than 2gb in size - see #1098 • Fix - Uninstall-ChocolateyPackage prints out warning if the passed file path starts and ends with quotes - see #1039 • Fix - Get-UninstallRegistryKey fixes/improvements - see #815 • Fix - Unzip specific folder feature is broken after introducing 7zip - see #676 • Fix - Join-Path error when installing Chocolatey as SYSTEM - see #1042 • Fix - $env:OS_NAME is 'Windows' for Windows 10 - see #1178
• Fix - choco install relativepath/to/some.nuspec fails - see #906
• Fix - When pointing to a nupkg, choco should use only that nupkg to install and not a newer version in the same directory - see #523
• Fix - Automatic uninstaller should split by quotes when necessary - see #1208
• [API] Fix - lib should merge the AlphaFS dependency - see #1148
• [API] Fix - don't reset loggers on setting custom automatically - see #1121
• [API] Fix - Chocolatey file cache adds a 'chocolatey' directory on each install - see #1210
• [API] Fix - Getting Local List of Package may leave config in undesirable state - see #1213
• Fix - Pro/Business - Chocolatey Licensed Feed May Show Up More Than Once - see #1166
• Fix - Pro/Business - Synchronized packages with DLLs are attempted to be imported by Chocolatey's PowerShell Extensions Loader - see #1041

### IMPROVEMENTS

• [Security] Username and password for choco apikey not encrypted in output - see #1106
• [Security] Sign Binaries / Authenticode Signatures with Chocolatey Software digital certificate - see #1214
• Setting commandExecutionTimeout to 0 means never time out - see #1202
• Configure sources to skip proxy - see #262
• Set proxy information at runtime - see #1173
• Add --no-progress cli switch for hidding progress bars - see #917
• Note web status errors on package install failures - see #1172
• Always let Nuget.Core log - see #1095
• Make choco get its proxy settings also from environment variables - see #605
• Remove quotes in process passed to Start-ChocolateyProcessAsAdmin / CommandExecutor - see #1167
• Trace network traffic - see #1182
• Upgrade 7Zip to 16.04 - see #1184
• Do not create .ignore file if outside of Chocolatey location - see #1180
• Help should exit zero if called with the help switch, otherwise non-zero on bad commands - see #473
• "Licensed messages" may address users in a somewhat unprofessional manner - see #1111
• Show the entire text to turn on the allowGlobalConfirmation flag - see #1053
• Running choco should produce name/version and further instructions - see #1083
• Typo in Install-ChocolateyPowershellCommand - see #1088
• Update choco new pkg template to give example of handling nested quoted paths - see #1067
• Add Aliases for Install-ChocolateyVsixPackage - see #1146
• Pro/Business - Feature to Disable Non-Elevated Warnings - see #1118
• Pro/Business - Allow version overrides for local packages - see #942
• Pro/Business - List include programs should not show items from Package Synchronizer's Programs and Features Package Sync - see #1205
• Pro/Business - PowerShell Functions should allow overriding urls - see #1117
• Pro/Business - Automatic Uninstaller - allow remove directly - see #1119
• Pro/Business - Ensure sync command can be machine parseable - quiet logging - see #1147
• Pro/Business - Configure a source to be allowed for self-service - see #1181

## 0.10.3

### BREAKING CHANGES

• Fix - Do Not Check $LastExitCode - Only error a package install if script errors or set a different exit code when it is specifically set - see #1000 Starting in v0.9.10, Chocolatey started checking $LASTEXITCODE in addition to the script command success as a way to be more helpful in determining package failures. This meant it offered the ability to capture when a script exited with Exit 1 and handle that accordingly. However that really has never been a recommended scenario for returning errors from scripts and is not seen in the wild anywhere so it is believed that those that may be affected are very few.

Checking $LastExitCode checks the last executable's exit code when the script specifically does not call Exit (which is . This can lead to very perplexing failures, such as running a successful xcopy that exits with 2 and seeing package failures without understanding why. Since it is not typically recommended to call Exit to return a value from PowerShell because of issues with different hosts, it's less of a concern to only look at explicit failures. For folks that may need it, allow failing a package again by the last external command exit code or exit from a PowerShell script. Note that it is not recommended to use exit with a number to return from PowerShell scripts. Instead you should use $env:ChocolateyExitCode or Set-PowerShellExitCode (first available in v0.9.10) to ensure proper setting of the exit code.

If you need the prior behavior, please turn on the feature scriptsCheckLastExitCode.

### BUG FIXES

• Fix - chocolateybeforemodify runs after modifying (moving) chocolatey lib package files - see #995
• Fix - The refreshenv command throws an error about Write-FunctionCallLogMessage when ran in PowerShell on 0.10.2 - see #996

## 0.10.2

We're dubbing this the "Every Joe" release in honor of a friend that just lost his fight with brain cancer. If you want to help further research, please make a donation to a cancer research association of your choosing (e.g. the American Brain Tumor Assocation).

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