Skip to content
Mia Automation
NLEN Sign in Put Mia to workGet started

How to install Claude Code on Windows

One PowerShell command installs Claude Code on Windows. On our stock Windows 10 test machine it finished in under half a minute, and then typing claude did nothing, because the installer didn't add its folder to PATH. Below: the install, the two-line PATH fix, native Windows versus WSL, and the errors you're most likely to see.

Claude in practiceUpdated 8 min read

Tested by us on 11 November 2026.

Before you start

  • Windows 10 version 1809 or later, Windows 11, or Windows Server 2019 or later.
  • At least 4 GB of RAM and a 64-bit processor (x64 or ARM64).
  • An internet connection while you work, not only during the install.
  • A paid plan: Claude Pro, Max, Ultra, Team or Enterprise, or a Console account with API credit. The free claude.ai plan does not include Claude Code.

You don't need admin rights. Everything lands in your own user folder under C:\Users\<you>\.local, and you don't need Node.js either, because the recommended install is a standalone program.

Install Claude Code in four steps

Animated diagram of the install: open PowerShell, paste the command and wait up to half a minute, add the folder to PATH, check the version in a new window, then start claude to sign in.
The whole install at a glance. The bar is the silent wait: leave the installer alone while it runs.
  1. Open PowerShell

    Search the Start menu for PowerShell and open Windows PowerShell. Your prompt starts with PS C:\. If there's no PS, you're in Command Prompt (CMD). That works too, but you'll need the CMD command from the table below these steps.

  2. Run the installer

    Paste this line and press Enter. The installer shows no progress while it downloads. In our two test runs the screen stayed blank for 26 and 15 seconds before the success message appeared, so don't cancel early.

    powershell
    irm https://claude.ai/install.ps1 | iex
  3. Add the install folder to PATH

    Read the output to the end. If it says Native installation exists but C:\Users\<you>\.local\bin is not in your PATH, Windows can't find the claude command yet. Not sure? Run $env:PATH -split ';' | Select-String '\.local\\bin'. No output means the folder is missing, and these two lines add it to your user PATH for good. Run them only once, even if claude still fails in this window: a second run adds the folder twice.

    powershell
    $currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
    [Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')
  4. Open a new window and check the version

    Close PowerShell and open a fresh window, because the old one still has the old PATH. Type claude --version. A version number such as our 2.1.322 (Claude Code) means you're done.

    powershell
    claude --version
Windows PowerShell after the install command: Claude Code successfully installed, version 2.1.322, with a setup note saying the .local\bin folder is not in PATH. (opens at full size)
Our screen after step 2. The Setup notes warning means the folder isn't on your PATH, so you need step 3. The empty boxes are emoji that PowerShell can't draw. We swapped the username for a placeholder.
A new PowerShell window where claude --version prints 2.1.322 (Claude Code). (opens at full size)
Step 4 in a fresh window: a version number means Windows can find the command.
Three ways to get the same program.
MethodCommandUpdates
PowerShell (recommended)irm https://claude.ai/install.ps1 | iexAutomatic, in the background
Command Prompt (CMD)curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmdAutomatic, in the background
WinGetwinget install Anthropic.ClaudeCodeManual: winget upgrade Anthropic.ClaudeCode

npm still works (npm install -g @anthropic-ai/claude-code, Node.js 22 or later), but we skip it on Windows. PowerShell's execution policy can block the launcher scripts npm creates, and according to the docs the npm package installs the same native binary as the installer.

Sign in

In PowerShell, go to your project folder and type claude. On the first run, Claude Code asks which text style reads best in your terminal: pick one with the arrow keys and press Enter. Your browser then opens a sign-in page. Log in with the account that pays for your plan, or with your Console account, then switch back to the terminal and start working.

Claude Code's first run in PowerShell: a welcome screen asking you to pick one of seven text styles, with a preview of a code change. (opens at full size)
The first time you type claude, you pick a text style. Sign-in comes right after.

Do you need Git for Windows?

It's optional, and we install it on every machine. Claude Code runs commands through a shell. With Git for Windows installed it uses Git Bash; without it, it falls back to PowerShell. Most scripts and examples you'll find assume Bash, and Git gives you version control, so you can roll back a change Claude Code made with one command.

If Git is installed but Claude Code can't find Git Bash, point it at bash.exe in settings.json, which lives in the .claude folder inside your user folder:

json
{
  "env": {
    "CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
  }
}

Native Windows or WSL?

Claude Code runs on Windows directly or inside WSL, the Linux environment built into Windows. Pick the one that matches where your projects live.

Native WindowsWSL 2
RequirementsNothing extra; Git for Windows is optionalWSL 2 enabled, with a Linux distribution
Where you installPowerShell or CMDThe WSL terminal, with the Linux command
Sandboxed commandsNot supportedSupported
Best forWindows projects and Windows toolsLinux toolchains such as Docker or Python servers

If your code and tools live on Windows, install natively. If your project runs on Linux, or you want commands to run in a sandbox, use WSL 2.

With WSL, watch where your project lives. Microsoft recommends keeping files in the Linux file system when you work from a Linux shell, so /home/<you>/project rather than /mnt/c/Users/<you>/project. On the mounted Windows drive, every file Claude Code reads or writes goes through a slower layer. We haven't tested the WSL route ourselves; this part follows the Anthropic and Microsoft documentation, including the sandbox support in the table.

For WSL, open your Linux distribution first and install there with curl -fsSL https://claude.ai/install.sh | bash. You then launch claude from that WSL terminal, not from PowerShell.

Check the install

claude doctor prints a health report of your installation without starting a session. Ours showed Running: native (2.1.322), Platform: win32-x64 and Auto-updates: enabled, plus a PATH warning that only went away in a new window.

The native install keeps itself current: updates download in the background and take effect the next time you start claude. A WinGet install stays on its version until you upgrade it yourself.

Common errors and fixes

We hit the PATH error and the && error ourselves on our test machine. The other errors and fixes come from the official troubleshooting guide; we didn't reproduce all of them.

ErrorCauseFix
'irm' is not recognizedYou're in CMD, not PowerShell.Open PowerShell, or use the CMD command from the table above.
The token '&&' is not a valid statement separatorYou pasted the CMD command into PowerShell.Run irm https://claude.ai/install.ps1 | iex instead.
'claude' is not recognized.local\bin isn't on your PATH.Do step 3, then open a new window.
Could not create SSL/TLS secure channelWindows PowerShell 5.1 is using an old TLS version.Run [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12, then the installer, in the same window.
Claude Code does not support 32-bit WindowsYou opened the 32-bit (x86) PowerShell.Open plain Windows PowerShell, without (x86) in the name.
The process cannot access the fileAn earlier attempt or your antivirus is holding the download.Close other PowerShell windows, delete .claude\downloads in your user folder and retry.

Uninstall

These two lines remove the program and every downloaded version. We ran them after our test, and nothing of the install was left behind.

powershell
Remove-Item -Path "$env:USERPROFILE\.local\bin\claude.exe" -Force
Remove-Item -Path "$env:USERPROFILE\.local\share\claude" -Recurse -Force

Your settings and session history live separately, in the .claude folder and the .claude.json file in your user folder. Delete those only if you want a clean slate. The VS Code extension and the desktop app recreate the folder if they're still installed.

Questions

Is Claude Code free on Windows?

Installing it is free, but you need a paid plan to use it: Claude Pro, Max, Ultra, Team, Enterprise, or a Console account with API credit. The free claude.ai plan has no Claude Code access.

Do I need admin rights to install Claude Code?

No. The installer writes only to your user folder, and the PATH change applies to your account, not the whole machine.

Does Claude Code work on Windows 10?

Yes, from version 1809 onwards. We tested on Windows 10 22H2 (64-bit) with the built-in Windows PowerShell 5.1. Windows 11 and ARM64 are in the official requirements too, but we haven't tried them ourselves.

Can I use Claude Code without the terminal?

Yes. The Claude desktop app for Windows gives you Claude Code in a regular window. If you've never used a terminal, that's the easiest place to start.

Sources