A documented cause of Windows install errors is running the installer written for a different shell. Use install.ps1 in PowerShell, the curl install.cmd command in CMD, or the Linux installer inside WSL. Then open a new terminal and run claude --version. For update failures, the docs cover a dropped download, a missing PATH entry and an interrupted file swap.
One documented cause of Windows install errors is running the installer written for a different shell. In PowerShell run irm https://claude.ai/install.ps1 | iex. In CMD run curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd. Inside WSL, run the Linux installer, curl -fsSL https://claude.ai/install.sh | bash, from the WSL terminal. Then open a new terminal and run claude --version. Update failures have their own causes, covered below. The commands are the ones the advanced setup page gives.
This guide restates what the advanced setup and install troubleshooting pages document, as read in November 2026. The installers were not run for this guide, and no failure was reproduced. For live provider status, see the Claude Code status hub.
Which error do you have?
| What you see | Likely cause | What to do |
|---|---|---|
'irm' is not recognized | You are in CMD, not PowerShell | Open PowerShell, or use the CMD installer |
The token '&&' is not a valid statement separator | You are in PowerShell and ran the CMD command | Run the PowerShell installer |
A parameter cannot be found that matches parameter name 'fsSL' | macOS/Linux installer run in Windows PowerShell | Run the PowerShell installer |
'claude' is not recognized after install | %USERPROFILE%\.local\bin is not on your PATH | Add it to your User PATH, then open a new terminal |
The connection dropped while downloading the update | The connection closed and the retries did not recover | Run claude update again, set HTTPS_PROXY if needed |
Exec format error in WSL | WSL1 native-binary regression | Convert the distro to WSL2 |
claude.exe missing after an update | Moving the new version into place failed, and the backup could not be renamed back | Rename the newest claude.exe.old.* backup back |
How do I install on native Windows?
Claude Code supports Windows 10 1809 or later and Windows Server 2019 or later, with 4 GB of RAM or more. Run the installer from PowerShell or CMD; you do not need Administrator rights. Your prompt shows PS C:\ in PowerShell and C:\ without the PS in CMD. Git for Windows is optional: with it, Claude Code uses Git Bash for its Bash tool, and without it Claude Code uses PowerShell. If Git is installed but not found, set the path in settings.json:
{
"env": {
"CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
}
}
The docs say the file must be named bash.exe, sh.exe, bash or sh. Pointing at Git for Windows' git-bash.exe launcher is ignored. If you see "Claude Code does not support 32-bit Windows", you opened Windows PowerShell (x86); check [Environment]::Is64BitOperatingSystem and reopen the non-x86 entry.
Why does claude say not recognized after installing?
The native installer puts claude.exe in %USERPROFILE%\.local\bin and, per the docs, reports a setup note if that folder is not on PATH. It prints the fix but does not change PATH itself. The docs give these PowerShell checks and fix:
Test-Path "$env:USERPROFILE\.local\bin\claude.exe"
$env:PATH -split ';' | Select-String '\.local\\bin'
$currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
[Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')
Restart the terminal, then run claude --version. A terminal inside an editor takes its PATH from the editor, so quit and reopen the editor too. Installing the VS Code extension alone does not put claude on PATH.
How do I install in WSL?
Open your WSL distribution and run the Linux installer there. Do not launch it from PowerShell or CMD. WSL 2 supports sandboxing; WSL 1 does not. WSL setups do not need Git for Windows. Platform-specific WSL fixes from the docs:
Exec format erroron WSL1. Convert the distro withwsl --set-version <DistroName> 2from PowerShell. The docs track this as issue 38788.- npm installs:
exec: node: not found. WSL is probably using the Windows Node. Runwhich node; a path starting with/mnt/c/is the Windows binary. Install Node through your distro or nvm. This only applies to npm installs, not the native installer. - No browser opens at login. Press
cat the login prompt to copy the URL, sign in on your local machine, and paste the code back.claude auth loginis the fallback if pasting fails.
Why does claude update fail?
Native installs update in the background; Homebrew, WinGet and Linux package-manager installs do not, so run winget upgrade Anthropic.ClaudeCode for WinGet. If the footer shows Auto-update failed · Run claude doctor, the docs say you can keep working and should run claude update in your shell for the actual error. The docs also note that the Last update attempt: failed (install_failed) line in claude doctor gives a date but no cause.
Fixes from the docs for specific messages:
The connection dropped while downloading the update: runclaude updateagain. The docs say Claude Code retries a dropped download up to three attempts in total, and the message itself notes that proxies sometimes cut off large downloads. SetHTTPS_PROXYif your network needs one.Release verification failed for Claude Code: nothing was installed and your current version still works. Try the same command again later.The process cannot access the fileduring install: the docs say a previous install attempt is still running or antivirus software is scanning a partial download in%USERPROFILE%\.claude\downloads. Close other windows, wait, delete that folder and rerun the installer.claude.exemissing after an update: the docs explain that Windows updates rename the oldclaude.exeaside as a backup. Look forclaude.exe.old.*in%USERPROFILE%\.local\binand rename the newest one toclaude.exe, or reinstall.
Users have reported Windows update problems on GitHub that the docs do not cover, such as issue 105554 (update interrupted mid-swap) and issue 106716 (Windows ARM64). Both were still open when checked in November 2026 and are user reports, not confirmed behaviour. Authentication failures after a clean install are a different problem: see what "Authentication service was unavailable" means.
How do I confirm it worked?
Open a new terminal and run claude --version. A working install prints a version number; the docs' example is 2.1.211 (Claude Code). For a fuller read-only check, run claude doctor from your shell. Before reinstalling over a broken setup, do not delete ~/.claude: the docs warn that removing configuration files deletes all your settings, allowed tools, MCP server configurations and session history.
More practical writing for people building with AI tools is on the Lead Source blog.
Fixed? Two optional things
Check Anthropic’s status and get an alert when an incident is resolved: Claude Code status and alerts, an independent resource by Lead Source.
Official source: status.claude.com.
Written by the team at Lead Source, where the day job is lead source tracking: working out which marketing actually brings customers.