Chocolatey

0.9.10-beta-20160330 | Updated: 3/31/2016

174,901,830

379

Maintainer(s):

Software Author(s):

• Rob Reynolds
• The Chocolatey Team

Tags:

Some Checks Have Failed or Are Not Yet Complete

1 Pending Test and 1 Passing Test

Verification Testing Pending

Validation Testing Passed

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

>
This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
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 sticky! Wiki!

In that mess there is a link to the Helper 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-FileName.ps1
tools\chocolateyInstall\helpers\functions\Get-FtpFile.ps1
tools\chocolateyInstall\helpers\functions\Get-ProcessorBits.ps1
tools\chocolateyInstall\helpers\functions\Get-ToolsLocation.ps1
tools\chocolateyInstall\helpers\functions\Get-UACEnabled.ps1
tools\chocolateyInstall\helpers\functions\Get-VirusCheckValid.ps1
tools\chocolateyInstall\helpers\functions\Get-WebFile.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\Set-EnvironmentVariable.ps1
tools\chocolateyInstall\helpers\functions\Uninstall-BinFile.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\7za.exe
tools\chocolateyInstall\tools\7za.exe.ignore
tools\chocolateyInstall\tools\7za.exe.manifest
tools\chocolateyInstall\tools\checksum.exe
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 739 Friday, May 31, 2019 approved
Chocolatey 0.10.14 506709 Thursday, May 30, 2019 approved
Chocolatey 0.10.14-beta-20190418 5156 Thursday, April 18, 2019 approved
Chocolatey 0.10.14-beta-20190402 2557 Tuesday, April 2, 2019 approved
Chocolatey 0.10.14-beta-20190321 2128 Friday, March 22, 2019 approved
Chocolatey 0.10.13 7583367 Friday, March 15, 2019 approved
Chocolatey 0.10.12 151901 Friday, March 15, 2019 approved
Chocolatey 0.10.12-beta-20181011 14866 Friday, October 12, 2018 approved
Chocolatey 0.10.12-beta-20181009 515 Tuesday, October 9, 2018 approved

0.9.10

What will be highlighted:

• Alternative sources (webpi, windowsfeature, cygwin, etc) are back (finally, right?)!
• Use an internal PowerShell host to take advantage of quite a few improvements!
• Introduce managing package templates, reintroduce extensions.
• Talk about the improvements in search information
• Talk about tab completion and refreshenv!
• Talk a little about what's coming with pro

BREAKING CHANGES

• Only fail automation scripts (chocolateyInstall.ps1) if the script returns non-zero exit code - see #445
• Fix - Force reinstall, force upgrade, and uninstall should delete the download cache - see #590

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

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

FEATURES

• Alternative Sources - see #14
• [POSH Host] Use Internal PowerShell Host - see #8
• 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

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
• 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-FileName 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
• 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: PowerShell v2 - Choco installer messages can't actually be warnings (can cause FileStream errors) - see #666
• 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

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
• Pro - Also check for license in User Profile location - see #606
• Pro - Set download cache information if available - see #562
• Pro - Allow commands to be added - see #583
• 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

This package has no dependencies.

Discussion for the Chocolatey Package