HTTPS clone URL
Subversion checkout URL
- Hosting Chocolatey Packages on MyGet
- How To Deprecate A Chocolatey Package
- How To Mount An Iso In Chocolatey Package
- How To Parse PackageParameters Argument
- Migrate Old Chocolatey Directory to ProgramData
- Proxy Settings for Chocolatey
This wiki is for versions LESS THAN 0.9.9.x. If you are on a newer version, please see https://github.com/chocolatey/choco/wiki instead
How to use Chocolatey
- Complete Reference
- Install Missing
Clone this wiki locally
FOR 0.9.9+ use https://github.com/chocolatey/choco/wiki/Installation instead
Chocolatey installs in seconds...
There are a few ways to install chocolatey. Chocolatey exists as a nuget package so virtually any way you can get a nuget package, you have the opportunity to then install it.
If you have Visual Studio 2010 and the NuGet extension installed, perhaps the quickest method is to use NuGet Package Manager. Three commands in succession and you are done. See below.
Great question - why chocolatey installs where it does
Can I install chocolatey to another location? Yes
- Create a machine level (user level will also work) environment variable named
ChocolateyInstalland set it to the folder you want chocolatey to install to prior to installation (this environment variable must be set globally or available to PowerShell- it is not enough to simply make it available to your current command prompt session). Keep in mind the restrictions though!
- Create the folder manually.
- If you have already installed (and want to change the location after the fact):
- Follow the above steps.
- Install chocolatey again.
- Copy/Move over the items from the old lib/bin directory.
- Delete your old install directory.
- You must choose a different location than the default. The default is a more secure location that only administrators can write to.
- Follow that with the command line / powershell methods of installation.
This really is the easiest method because it requires no configuration of powershell prior to executing it. Open a command line, paste the following and press <Enter>:
@powershell -NoProfile -ExecutionPolicy unrestricted -Command "(iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))) >$null 2>&1" && SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin
This is the second-most easy method. Open a powershell command line and paste in the following and press <Enter>:
(iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1')))>$null 2>&1
Note: You must have your execution policy set to unrestricted (or at least in bypass) for this to work (
Set-ExecutionPolicy Unrestricted). There have been reports that RemoteSigned is enough for the install to work.
It downloads and runs (https://chocolatey.org/install.ps1).
NOTE: This method will give you a deprecated warning.
This is the best method if you want to repeat it or include it in source control. It requires no change to your existing powershell to allow for remote unsigned scripts.
Download the two items from chocolateyInstall.
installChocolatey.cmd and it will install and update to the latest version of chocolatey.
When you have Visual Studio 2010 and the NuGet extension installed, you can simply type the following three commands and you will have chocolatey installed on your machine.
You can also use nuget command line to download chocolatey:
nuget install chocolatey or
nuget install chocolatey -pre
Once you download it, open powershell (remote unsigned), navigate to the tools folder and run:
You can also just download and unzip the chocolatey package (
.nupkg is a fancy zip file):
- Download the Chocolatey package.
- Unzip it using any application that supports
- Open a PowerShell command shell and navigate into the unzipped package's tools folder.
- NOTE: Ensure PowerShell execution policy is set to at least bypass or remote signed (if you have issues, you may need to set it to Unrestricted).
& .\chocolateyInstall.ps1to allow Chocolatey to install.