Windows install guide
Claude Code Windows install: choose your method, then get it running
Updated November 17, 202611 min read
Claude Code on Windows installs with one PowerShell command, irm https://claude.ai/install.ps1 | iex, and runs natively on Windows 10 (version 1809 or newer) and Windows 11, so WSL is optional. Start by picking the install method that suits you, copy its exact command, and if something goes wrong, find your error message in the table further down.
The short version
- Most people should use the native installer in PowerShell. It needs no admin rights and updates itself.
- WinGet and npm installs work too, but you run the upgrade yourself.
- Choose WSL 2 if your project needs Linux tools or you want Claude Code's sandboxing.
- You need a Pro, Max, Ultra, Team, Enterprise or Console account, because Claude's free tier leaves Claude Code out.
- Nearly every install error comes from the wrong shell, a 32-bit PowerShell window or a missing PATH entry.
Pick a Claude Code install method before you type anything
There are five ways to get Claude Code onto a Windows PC. The first four all give you the same claude command, so the choice comes down to how you like to install and update software. The fifth is a separate app you click instead of type into.
Native installer (PowerShell or CMD)
you want the easy path. No Node.js, no Administrator window, and it keeps itself up to date in the background. Anthropic recommends this one.
WinGet
you already install your apps with the Windows Package Manager (Microsoft's command line app store) and like updating everything in one go.
npm
you already have Node.js 22 or newer and keep your developer tools in npm. It installs the same Claude Code program as the native installer.
WSL 2
your project is built for Linux, or you want sandboxing (a fenced-off space for the commands Claude runs). Native Windows does not support sandboxing.
Claude desktop app
you searched for a Claude Code download for Windows because you would rather click than type. Get it from claude.com/download.
Whichever you pick, check that your PC meets Anthropic's system requirements first (as of November 2026):
- Windows 10 version 1809 or newer, Windows 11, or Windows Server 2019 or newer. Claude Code on Windows 11 needs nothing special.
- 4 GB of RAM or more and an x64 or ARM64 processor. 32-bit Windows is not supported.
- An internet connection, and you must be in one of Anthropic's supported countries.
- A Claude Pro, Max, Ultra, Team or Enterprise plan, or a Claude Console account (prepaid API credits).
How to install Claude Code on Windows with the native installer
- 1
Open the right PowerShell
Press the Windows key, type PowerShell and open Windows PowerShell. Skip the entry that ends in (x86): it runs as a 32-bit program and the installer refuses it. Your prompt should start with
PS C:\. - 2
Paste the install command
Copy the command below, paste it and press Enter. It shows no progress bar while it downloads, so wait until the prompt comes back.
- 3
Open a fresh terminal window
Close the window and open a new one. The old window still holds the old PATH (the list of folders Windows searches for programs), so it cannot see
claudeyet. - 4
Check the version
Type
claude --version. A working install prints a number followed by (Claude Code). If Windows says the command is not recognized, go to the error table below. - 5
Start it in a project and sign in
Move into your project folder with
cd, for examplecd C:\code\my-app, then typeclaude. Your web browser pops up and asks you to sign in to Claude. The login is saved, so you only do this once.
Claude Code PowerShell install command
irm https://claude.ai/install.ps1 | iexInstalling from CMD (Command Prompt) instead
If your prompt reads C:\Users\YourName> with no PS in front, you are in CMD. This version downloads a small installer file, runs it, then deletes it:
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmdChoosing the stable channel or one exact version
By default you get every new release as soon as it ships. The stable channel is usually about a week behind and skips releases with major bugs. To install it from PowerShell, run the first line. Swap stable for a number such as 2.1.89 when you need one exact release.
& ([scriptblock]::Create((irm https://claude.ai/install.ps1))) stableClaude Code CLI install on Windows with WinGet
- 1
Install the package
Run the first command below in PowerShell. WinGet downloads Claude Code and puts it on your PATH.
- 2
Confirm it worked
Open a new terminal and run
claude --version, the same check as the native method. - 3
Keep it current
WinGet copies do not update themselves by default. Run the upgrade command every week or two. If you would like Claude Code to run that upgrade for you, set the
CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATEsetting to1. - 4
Close Claude before upgrading
Windows locks a program file while it is running, so an upgrade can fail if Claude Code is open. Quit every session, then try again.
winget install Anthropic.ClaudeCode
winget upgrade Anthropic.ClaudeCode
winget uninstall Anthropic.ClaudeCodeWinGet is also the fallback Anthropic suggests when the native installer keeps failing on your network, because it downloads through a different route.
Installing with npm if you already use Node.js
- 1
Check your Node.js version
Run
node --version. The npm package asks for Node.js 22 or later. On an older version npm prints anEBADENGINEwarning but still finishes, because Claude Code itself does not run on Node. - 2
Install it globally
Run the npm command below in a normal window. Do not use an Administrator prompt, since Claude Code updates itself without one.
- 3
Upgrade with the same command
To move to the newest release, run the install command again. Avoid
npm update -g, which can leave you on an older version. - 4
Unblock PowerShell if it refuses
If PowerShell says
claude.ps1 cannot be loaded because running scripts is disabled on this system, allow local scripts for your user with the second command below, or typeclaude.cmdinstead ofclaude.
npm install -g @anthropic-ai/claude-code@latestSet-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserTip
The execution policy only blocks script files. The PowerShell installer (irm ... | iex) is never affected, which is one more reason most people find it easier than npm.
Claude Code WSL setup for Linux projects
- 1
Turn on WSL
Open PowerShell as Administrator, run
wsl --installand restart when asked. This sets up Ubuntu, a Linux system that runs inside Windows. - 2
Create your Linux user
Open Ubuntu from the Start menu. It asks you to pick a Linux username and password the first time.
- 3
Run the Linux installer inside Ubuntu
Paste the command below into the Ubuntu window, not into PowerShell. A copy installed in PowerShell cannot be used from WSL, and the other way round.
- 4
Start Claude Code in your project
Use
cdto reach your project, then typeclaude. You do not need Git for Windows for a WSL setup. - 5
Sign in if no browser opens
WSL sometimes cannot open your Windows browser. Press
cat the login prompt to copy the login link, open it in your browser, sign in, then paste the code it shows back into the terminal.
curl -fsSL https://claude.ai/install.sh | bashTo let Claude Code open your Windows browser next time, point the BROWSER setting at it, for example export BROWSER="/mnt/c/Program Files/Google/Chrome/Application/chrome.exe", then run claude. Stick with WSL 2. On WSL 1 the program can fail with Exec format error, and sandboxing only works on WSL 2.
Claude Code with Git Bash or PowerShell as its shell
When Claude Code runs a command for you, it uses a shell (the program that reads typed commands). On native Windows it picks one of two:
- With [Git for Windows](https://git-scm.com/downloads/win) installed, Claude Code uses Git Bash for its Bash tool. The PowerShell tool is still there too, and it is on by default for claude.ai and Console accounts.
- Without Git for Windows, Claude Code runs everything through PowerShell. That works fine, so Git for Windows stays optional.
Claude Code looks for Git Bash in C:\Program Files\Git, then C:\Program Files (x86)\Git, then wherever the git on your PATH lives. If yours is somewhere else, run where.exe git in PowerShell to find it, then add its bin\bash.exe path to your settings file (%USERPROFILE%\.claude\settings.json):
{
"env": {
"CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
}
}The file name at the end must be bash.exe or sh.exe. If you point it at git-bash.exe, the launcher you click in the Start menu, Claude Code ignores the setting and searches on its own again.
Claude Code Windows errors and what each one means
Copy the first line of your error and find it below. All of these come from Anthropic's install troubleshooting page.
| Error you see | What it means | Fix |
|---|---|---|
'irm' is not recognized as an internal or external command | You are in CMD. irm only exists in PowerShell. | Use the CMD command, or open PowerShell |
The token '&&' is not a valid statement separator | You pasted the CMD command into PowerShell | Use irm https://claude.ai/install.ps1 | iex |
'bash' is not recognized as the name of a cmdlet or A parameter cannot be found that matches parameter name 'fsSL' | You pasted the Mac and Linux command into PowerShell | Use the PowerShell command instead |
| CMD prints script text and nothing installs | curl ran without -o, so it showed the file instead of saving it | Run the full CMD command, including -o install.cmd |
'claude' is not recognized | The install folder is not on your PATH yet | Open a new terminal. If it still fails, add the folder to PATH (below) |
'claude' is not recognized right after an update | The update moved the old claude.exe aside and the new one never landed | Rename the backup file back (below) |
Claude Code does not support 32-bit Windows | You opened Windows PowerShell (x86) | Open the plain Windows PowerShell entry |
The process cannot access the file ... because it is being used by another process | An earlier install is still running, or antivirus is scanning the download | Close other installer windows, delete %USERPROFILE%\.claude\downloads, run the installer again |
running scripts is disabled on this system | PowerShell blocks the script launchers npm creates | Run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser or use claude.cmd |
Claude Code on Windows requires either Git for Windows (for bash) or PowerShell | It found neither shell | Add C:\Windows\System32\WindowsPowerShell\v1.0\ to PATH, or install Git for Windows with Add to PATH ticked |
System.Xml.XmlDocument or HTML in a PowerShell parse error | The download returned a web page, not the install script | Wait a few minutes and retry, check your proxy, or install with WinGet |
App unavailable in region | Claude Code is not offered in your country | See Anthropic's supported countries list |
CRYPT_E_NO_REVOCATION_CHECK or CRYPT_E_REVOCATION_OFFLINE | Your network blocks the certificate check, common on work networks | Add --ssl-revoke-best-effort after curl in the CMD command, or use the PowerShell installer |
cannot execute binary file: Exec format error in WSL | You are on WSL 1 | Run wsl --set-version <DistroName> 2 in PowerShell |
Typing claude opens the desktop app | An older Claude Desktop registered its own Claude.exe | Update Claude Desktop to the latest version |
Add Claude Code to your PATH by hand
The installer puts claude.exe in %USERPROFILE%\.local\bin. The first line checks the file is there. The other two add that folder to your user PATH for good. Open a new terminal afterwards.
Test-Path "$env:USERPROFILE\.local\bin\claude.exe"
$currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
[Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')VS Code and other editors keep the PATH they had when they started, so quit and reopen the editor before testing its built-in terminal.
Bring back a missing claude.exe after an update
During an update Claude Code renames the old program to a backup called claude.exe.old. plus a number. If the swap fails halfway, this line renames the newest backup back. Then run claude --version. If there is no backup, run the installer again.
Get-ChildItem "$env:USERPROFILE\.local\bin\claude.exe.old.*" | Sort-Object Name | Select-Object -Last 1 | Rename-Item -NewName claude.exeFor anything not listed here, run claude doctor. It checks your install and settings without starting a session and prints suggested fixes.
After the install: your first 10 minutes with Claude Code
Once claude opens, work through this list in a real project. Each item takes a minute or so and teaches you one habit that matters later.
- Ask
what does this project do?Claude reads files as it needs them, so you never paste code in by hand. - Type
/init. It writes aCLAUDE.mdfile, the notes Claude reads at the start of every session. Add your build command and any rules, such as which folders it must not touch. - Ask for something small, like
add a hello world function to the main file. When it asks to make the change, pick Yes. - Press
Shift+Tabto cycle permission modes, which control what Claude may do without asking. One of them is plan mode, where it proposes before editing. See our plan mode guide. - Ask
what files have I changed?, thencommit my changes with a descriptive message. Git questions work in plain English. - Type
/rewindto see how to roll the chat or the code back to an earlier point if an edit goes wrong. - Type
/usageto see how much of your plan's limit you have used. - Leave with
/exit. Next time,claude -cpicks up the last conversation in that folder, andclaude -rlets you choose an older one.
If you prefer a slower start, our how to use Claude Code guide walks through prompts, permissions and reviewing changes, and the Claude Code tips page collects the habits that save the most time. To compare plans and limits, read Claude Code pricing.
When one terminal window is no longer enough
One Claude Code session in one window is easy. The trouble starts at three or four: windows pile up, you miss the moment a session is waiting for a yes, and a usage limit catches you by surprise. Mac and Linux users often reach for tmux, but tmux does not run natively on Windows (see Claude Code and tmux).
A grid of 12 agents
VibeCodingDeck runs the Claude Code you just installed in up to 12 panes, each on its own project, with up to 6 decks one click apart.
Lights that tell you who needs you
Every pane shows working, idle, waiting or done, with alert sounds, so a stuck session never sits for long.
Usage you can see
A live meter shows daily and weekly limits for every Claude login you use, plus a context meter on each pane.
Sessions that come back
Close the app and reopen it: the layout and the real conversations return.
Safe copies and save points
Agents can each work on their own copy of a project, and you can take a save point before anything risky.
Voice typing on your PC
Talk instead of typing. It transcribes on your own computer, GPU-accelerated on Windows.
It is a desktop app for Windows 10 and 11 (and Apple silicon Macs) that uses your own Claude subscription, so there is no second AI bill. It costs $29/month or $249/year with every feature on every plan, as of November 2026. See how to run multiple Claude Code agents or go straight to pricing.
Claude Code on Windows: quick answers
Can I run Claude Code on Windows without WSL?
+
Yes. Claude Code runs natively from PowerShell or CMD on Windows 10 (1809 or newer) and Windows 11. WSL 2 is only needed if you want Linux tools or sandboxing.
Where does Claude Code install on Windows?
+
The native installer puts claude.exe in %USERPROFILE%\.local\bin and keeps its version files in %USERPROFILE%\.local\share\claude. Your settings live in %USERPROFILE%\.claude.
How do I uninstall Claude Code on Windows?
+
For a native install, run Remove-Item -Path "$env:USERPROFILE\.local\bin\claude.exe" -Force and Remove-Item -Path "$env:USERPROFILE\.local\share\claude" -Recurse -Force in PowerShell. Use winget uninstall Anthropic.ClaudeCode or npm uninstall -g @anthropic-ai/claude-code if you installed that way.
Does Claude Code work on Windows on ARM laptops?
+
Yes. Anthropic supports both x64 and ARM64 processors, and the npm package includes a Windows ARM64 build.
Is Claude Code free on Windows?
+
Installing it costs nothing, but signing in needs a Pro, Max, Ultra, Team or Enterprise plan or a Console account with API credits. A free Claude account cannot sign in to it.
Do I need Git Bash to use Claude Code on Windows?
+
No. Without Git for Windows, Claude Code runs commands through PowerShell. Installing Git for Windows adds Git Bash, which Claude Code then uses for its Bash tool.
Sources
Run up to 12 AI coding agents in one window.
Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.
Get startedKeep reading
Terminal multiplexers
Claude Code and tmux for beginners: panes, keys and Windows options
Parallel agents
How to run multiple Claude Code agents at once: four ways, easiest last
Walkthrough
Claude Code desktop: download it, open the Code tab, and learn its limits
Beginner lesson plan
How to use Claude Code: a six-lesson course for beginners
Cost calculator
Claude Code pricing: plans, API rates and which one fits you
Windows setup
Codex on Windows: the app or the CLI, and how to set up each one