How to Install Chocolatey on Windows: A Complete Setup Guide

Chocolatey is a command-line package manager for Windows that lets you install, update, and manage software from a single terminal window — no clicking through installers, no hunting for download links, no manually checking for updates. If you've used apt on Linux or brew on macOS, Chocolatey fills that same role on Windows.

For web developers especially, it's a practical way to maintain a consistent, reproducible toolchain across machines.

What Chocolatey Actually Does

When you run a command like choco install nodejs, Chocolatey fetches the latest approved installer from its community package repository, runs it silently in the background, and confirms when it's done. You can install dozens of tools in a single script — Node.js, Git, VS Code, Python, Docker — without touching a browser.

It also handles upgrades across all installed packages with one command: choco upgrade all. That alone saves significant time for developers managing multiple tools.

System Requirements Before You Start

Chocolatey has straightforward prerequisites:

Most modern Windows 10 and Windows 11 machines meet all of these out of the box. If you're on an older system or a locked-down corporate machine, administrator rights are the most common blocker — Chocolatey installs into C:ProgramDatachocolatey and modifies system PATH variables, which requires elevated privileges.

Step-by-Step: Installing Chocolatey via PowerShell 🛠️

This is the standard installation method recommended by the Chocolatey project.

Step 1: Open PowerShell as Administrator

Click Start, search for PowerShell, right-click the result, and select Run as Administrator. This is mandatory — the install will fail without elevated permissions.

Step 2: Check Your Execution Policy

Before running the install script, check whether your system allows script execution:

Get-ExecutionPolicy 

If it returns Restricted, you'll need to temporarily allow scripts to run:

Set-ExecutionPolicy AllSigned 

Or, for the install session only:

Set-ExecutionPolicy Bypass -Scope Process 

The Bypass scope is commonly used here because it only affects the current PowerShell session — it doesn't permanently change your system's security policy.

Step 3: Run the Install Command

Paste the following into your elevated PowerShell window:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1')) 

This command:

• Sets execution policy for the session
• Enforces TLS 1.2 for the download (required by Chocolatey's servers)
• Downloads and runs the official install script

The install takes under a minute on most machines.

Step 4: Verify the Installation

Close and reopen PowerShell as Administrator, then run:

choco --version 

If you see a version number returned, Chocolatey is installed and on your PATH. You're ready to use it.

Installing Your First Packages

Once installed, the basic command structure is simple:

choco install <packagename> -y 

The -y flag auto-confirms all prompts, which is useful when installing multiple packages at once. For example:

choco install git vscode nodejs python -y 

That single line installs four separate tools silently in sequence.

Variables That Affect Your Experience

How smoothly Chocolatey runs depends on a few factors worth understanding before you commit to it as part of your workflow.

Execution policy settings vary between personal machines, work laptops, and managed enterprise environments. IT-controlled systems often lock down PowerShell execution policies, which can block installation or require IT intervention.

Package availability matters too. Chocolatey's community repository hosts thousands of packages, but not every piece of software is there — or kept equally up to date. Widely-used developer tools (Git, Node, Python, VS Code, Docker) are reliably maintained. Niche or proprietary software may be absent entirely.

Free vs. licensed tiers change what's available. The free Community edition covers most developer needs. Chocolatey for Business adds features like package internalization (hosting packages on your own servers), which matters in offline or enterprise environments.

Windows version and architecture occasionally affects specific packages. Most packages support both x64 and x86, but ARM-based Windows devices (like Surface Pro X) can encounter compatibility gaps with certain packages.

Common Issues and What Causes Them 🔍

Antivirus software occasionally flags Chocolatey's scripts as suspicious due to the nature of what they do — modifying system paths, downloading executables. Whitelisting the Chocolatey install directory typically resolves this.

Chocolatey vs. Windows Package Manager (winget)

Microsoft now ships winget natively with Windows 10 and 11, which covers similar ground. The two aren't mutually exclusive — many developers use both, depending on which has better package coverage for a given tool. Chocolatey's community repository is larger and more mature; winget benefits from being built into the OS with no installation required.

Your specific toolchain, environment constraints, and whether you're working solo or in a team managing shared configuration scripts will shape which approach — or combination — fits your actual workflow.