Chocolatey CLI
C# PowerShell Other
Latest commit 73a799b Jan 15, 2017 @ferventcoder ferventcoder committed on GitHub Merge pull request #1140 from Dennis14e/patch-1
Use HTTPS in
Failed to load latest commit information.
.build.custom (build) change message Jan 3, 2017
.build (GH-501) allow shutting off sign when no network Apr 9, 2016
.github (doc) No really, ALL the output please Mar 21, 2016
.nuget adding solution Dec 13, 2013
docs (doc) update generated docs Dec 2, 2016
lib (GH-1075) Add Architect license type SKU Dec 2, 2016
nuget (GH-1112) ensure .NET Fx is downloaded over SSL Dec 28, 2016
src (GH-1041) Fix bad PowerShell script Jan 4, 2017
.editorconfig (maint) legal and notices Dec 14, 2013
.gitignore (maint) ignore .vscode folder Apr 21, 2016
.travis.yml (maint) Specify mono version for Travis-CI Jul 30, 2015
.uppercut (version) 0.10.3 Oct 7, 2016 (doc) update CHANGELOG/nuspec Oct 7, 2016 (doc) update licensed changelog Dec 28, 2016 (GH-870) Update deprecated links Aug 1, 2016 clarify word choice Aug 23, 2016
GenerateDocs.ps1 (doc) Ensure command reference urls Dec 2, 2016
LICENSE (maint) legal and notices Dec 14, 2013
NOTICE (doc) correct license notice for new choco Jan 15, 2015 Use HTTPS in Jan 15, 2017 (GH-598) Add output directory for choco pack Aug 9, 2016
appveyor.yml (build) configure Feb 7, 2015
build.bat (doc) attempt to document scenarios every run Jun 1, 2015 (build) update uc Aug 27, 2015
chocolatey.snk adding solution Dec 13, 2013
documentscenarios.bat (doc) update scenarios Jun 1, 2015
setup.cmd (maint) bringing in chocolatey nuspec Dec 15, 2013
setup.ps1 (maint) bringing in chocolatey nuspec Dec 15, 2013
test.bat (build) test.bat not quiet, no results Feb 16, 2015
zip.bat (build) upgrade to uc v1.4.5 Jan 24, 2015 (build) update uc Aug 27, 2015

Chocolatey - like yum or apt-get, but for Windows

You can just call me choco.

Chocolatey Logo

Issue Stats

Issue Stats

Build Status

TeamCity AppVeyor Travis
TeamCity Build Status AppVeyor Build Status Travis Build Status

Chat Room

Come join in the conversation about Chocolatey in our Gitter Chat Room


Or, you can find us in IRC at #chocolatey on freenode. IRC is not as often checked by committers, so it is recommended you stick to Gitter if you need more timely assistance.

Please make sure you've read over and agree with the etiquette regarding communication.

Support Chocolatey!

See Chocolatey In Action

Chocolatey FOSS install showing tab completion and refreshenv (a way to update environment variables without restarting your shell):


Chocolatey Pro showing private CDN download cache and virus scan protection:

install w/pro

Etiquette Regarding Communication

When requesting support, try to remember that we are all volunteers that have lives outside of open source and none of us are paid to ensure things work for you, so please be considerate of others' time when you are asking for things. Many of us have families that also need time as well and only have so much time to give on a daily basis. In the future, we hope that some of us are paid to do this full time and can provide better support when folks are running into issues, but until then a little consideration and patience can go a long way. After all, you are using a pretty good tool without cost. It may not be perfect (yet), and we know that.



Please see the docs

Give choco.exe /? a shot (or choco.exe -h). For specific commands, add the command and then the help switch e.g. choco.exe install -h.


  • .NET Framework 4.0
  • PowerShell 2.0+
  • Windows Server 2003+ / Windows 7+

License / Credits

Apache 2.0 - see LICENSE and NOTICE files.

Submitting Issues

submitting issues

Observe the following help for submitting an issue:


  • The issue has to do with choco itself and is not a package or website issue.
  • Please check to see if your issue already exists with a quick search of the issues. Start with one relevant term and then add if you get too many results.
  • You are not submitting an "Enhancement". Enhancements should observe CONTRIBUTING guidelines.
  • You are not submitting a question - questions are better served as emails or gitter chat questions.
  • Please make sure you've read over and agree with the etiquette regarding communication.

Submitting a ticket:

  • We'll need debug and verbose output, so please run and capture the log with -dv or --debug --verbose. You can submit that with the issue or create a gist and link it.
  • Please note that the debug/verbose output for some commands may have sensitive data (passwords or apiKeys) related to Chocolatey, so please remove those if they are there prior to submitting the issue.
  • choco.exe logs to a file in $env:ChocolateyInstall\log\. You can grab the specific log output from there so you don't have to capture or redirect screen output. Please limit the amount included to just the command run (the log is appended to with every command).
  • Please save the log output in a gist (save the file as and link to the gist from the issue. Feel free to create it as secret so it doesn't fill up against your public gists. Anyone with a direct link can still get to secret gists. If you accidentally include secret information in your gist, please delete it and create a new one (gist history can be seen by anyone) and update the link in the ticket (issue history is not retained except by email - deleting the gist ensures that no one can get to it). Using gists this way also keeps accidental secrets from being shared in the ticket in the first place as well.
  • We'll need the entire log output from the run, so please don't limit it down to areas you feel are relevant. You may miss some important details we'll need to know. This will help expedite issue triage.
  • It's helpful to include the version of choco, the version of the OS, and the version of PowerShell (Posh) - the debug script should capture all of those pieces of information.
  • Include screenshots and/or animated gifs whenever possible, they help show us exactly what the problem is.


If you would like to contribute code or help squash a bug or two, that's awesome. Please familiarize yourself with CONTRIBUTING.


Committers, you should be very familiar with COMMITTERS.

Compiling / Building Source

There is a build.bat/ file that creates a necessary generated file named SolutionVersion.cs. It must be run at least once before Visual Studio will build.



  • .NET Framework 4+
  • Visual Studio is helpful for working on source.
  • ReSharper is immensely helpful (and there is a .sln.DotSettings file to help with code conventions).

Build Process:

  • Run build.bat.

Running the build on Windows should produce an artifact that is tested and ready to be used.

Other Platforms

  • Install and configure Mono 3.12.0 (3.8.0 should also work).
# add the key

sudo apt-key adv --keyserver --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
# add the package repository
echo "deb wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
# Ubuntu 12.10/12.04 - add this deb as well
echo "deb wheezy-libtiff-compat main" | sudo tee -a /etc/apt/sources.list.d/mono-xamarin.list

# update package indexes
sudo apt-get update
# install
sudo apt-get install mono-devel -y
# add the EPEL
sudo yum install epel-release -y
# Add the key
sudo rpm --import ""

# Add the package repository
sudo yum-config-manager --add-repo

# update your system
sudo yum update -y

# Install mono-devel
sudo yum install mono-devel -y

  • Xamarin Studio is helpful for working on source.
  • Consider adding the following to your ~/.profile (or other relevant dot source file):
# mono
export PKG_CONFIG_PATH=/opt/local/lib/pkgconfig:/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig:$PKG_CONFIG_PATH
  • Set your permissions correctly:
chmod +x
chmod +x
Build Process:
  • Run ./

Running the build on Mono produces an artifact similar to Windows but may have more rough edges. You may get a failure or two in the build script that can be safely ignored.


Chocolatey is brought to you by quite a few people and frameworks. See CREDITS (just LEGAL/ in the zip folder)