I Installed This Yesterday – Here’s What the Docs Don’t Warn You About
If you want to install Claude Code on Windows, the command itself takes about a minute. Then I typed claude in a new terminal window and got “command not recognized,” even though the installer said it finished successfully. Turns out that’s a known, fairly common issue on Windows, not something I broke. This guide covers the actual install steps plus the fixes for the two things most likely to trip you up right after.
What Claude Code Actually Is
Claude Code is Anthropic’s AI coding tool that runs in your terminal – not a chatbot window where you copy-paste code back and forth, but an agent that reads your actual project files, writes and edits code directly, runs commands, and handles git operations, all from natural-language instructions. It’s a separate product from the Claude.ai chat website and the Claude Desktop app, though Desktop can now run Claude Code sessions inside it too.
Before you install: Claude Code needs a Claude Pro, Max, Team, Enterprise, or Anthropic Console (API) account. The free Claude.ai plan does not include Claude Code access.
Install Claude Code on Windows
Open PowerShell (not CMD) as a regular user – no admin rights needed – and run:
irm https://claude.ai/install.ps1 | iexThis is the native installer, the currently recommended method. It doesn’t require Node.js at all, unlike the older npm-based install.
Install Claude Code on Windows
- Confirm your Windows version. Press
Win + R, typewinver, and confirm you’re on Windows 10 (version 1809 or later) or Windows 11. - Open PowerShell as your regular user. Not Administrator – the native installer doesn’t need elevated permissions.
- Run the install command:
irm https://claude.ai/install.ps1 | iex - Close and reopen your terminal completely. Not just a new tab – fully close every PowerShell, CMD, and VS Code terminal window so the updated PATH actually loads.
- Verify it installed:
claude --version - Navigate to a project folder and start it:
cd your-project-folder claudeThe first run opens your browser for a one-time sign-in to your Anthropic account.
Native Installer vs. npm – Which One
| Native Installer | npm (legacy) | |
|---|---|---|
| Requires Node.js | No | Yes, 18.0+ |
| Anthropic’s recommended method | Yes | No – officially deprecated |
| Auto-updates | Yes, in background | No, manual reinstall |
| Good reason to use it anyway | – | You need to pin a specific version |
Unless you have a specific reason to pin a version, the native installer is the one to use. If you’re already on the npm version, migrating over preserves your existing settings (~/.claude/settings.json and project-level .claude/ configs).
Fix: “claude is not recognized” After a Successful Install
This is the most common post-install problem, and it’s a known upstream issue, not something specific to your machine. The installer places the binary at C:\Users\<username>\.local\bin\claude.exe but sometimes fails to add that folder to your PATH – this shows up more often on domain-joined work laptops, especially when the username contains a dot.
Fix it manually by running this in PowerShell:
$claudeBin = Join-Path $env:USERPROFILE ".local\bin"
$currentPath = [Environment]::GetEnvironmentVariable("PATH", "User")
if ($currentPath -notlike "*$claudeBin*") {
[Environment]::SetEnvironmentVariable("PATH", "$currentPath;$claudeBin", "User")
}Then fully close every terminal window (PowerShell caches PATH at session start, so a new tab in the same window won’t pick up the change) and open a fresh one.
Fix: “irm is not recognized”
This means you’re running the command in CMD, not PowerShell – irm is a PowerShell alias and doesn’t exist in CMD. Check your prompt: PS C:\Users\YourName> means PowerShell, C:\Users\YourName> without the “PS” means CMD. Open PowerShell specifically and re-run the install command there.
Do You Need Git for Windows?
It’s optional but genuinely recommended. Claude Code shells out to Bash internally for certain operations, even when you’re running everything from PowerShell. Without Git for Windows installed, Claude Code falls back to using PowerShell as its shell tool instead, which works but is a less predictable environment for the kind of Unix-style commands Claude Code tends to generate. Download Git for Windows
Native Windows vs. WSL – Which Should You Use
| Situation | Better fit |
|---|---|
| Your projects already live in Windows folders | Native Windows |
| You want the most Linux-native, predictable command behavior | WSL |
| You’re new to the terminal in general | Native Windows |
| Your team’s setup docs and scripts assume a Linux shell | WSL |
If you do go the WSL route, run the install from inside your WSL terminal, not PowerShell, and keep Git configured separately on the WSL side – Git on Windows and Git inside WSL are two separate installations with their own username/email settings.
Verify Everything’s Working
Once installed and signed in, run this inside a Claude Code session:
/doctorThis checks installation integrity, your active subscription, and general configuration, and flags common issues automatically. Green checkmarks across the board mean you’re set up correctly.
Frequently Asked Questions
Does Claude Code work with the free Claude.ai plan?
No. It requires a Claude Pro, Max, Team, Enterprise, or Console (pay-per-use API) account. Signing in with a free account won’t unlock Claude Code access.
Do I need to run the installer as Administrator?
No, and you shouldn’t need to. The native installer is designed to run under a regular user account without elevated permissions.
Subscription or API key – which is cheaper for regular use?
For frequent daily use, a Claude Max subscription gives you higher usage limits at a fixed monthly cost, which is generally more predictable than pay-per-token API billing. The API route makes more sense for CI/CD pipelines, automation, or lighter occasional use where a flat monthly fee wouldn’t get used up.
What’s the difference between Claude Code and Claude Desktop?
Claude Desktop is the Electron app with a chat interface, and as of 2026 it can also run Claude Code sessions inside it (a mode called Cowork handles broader agentic tasks). Claude Code itself is the terminal-first CLI tool – same underlying engine, different interface depending on whether you want a GUI or a pure command-line workflow.
My install seemed to work but nothing happens when I type “claude” – now what?
Almost always the PATH issue covered above. Run the PowerShell fix, then make sure you fully closed and reopened your terminal window rather than just opening a new tab in the same session.
Final Thoughts
To install Claude Code on Windows successfully, the two things worth remembering are: use PowerShell, not CMD, and fully restart your terminal after the install completes.
The actual install command is one line and takes under a minute. The friction almost always shows up right after, in the PATH not updating or running the command in the wrong shell – both are quick fixes once you know that’s what’s happening rather than assuming the install failed outright.
If you’re deciding whether Claude is even the right AI tool for your workflow in the first place, our Claude vs ChatGPT vs Gemini comparison breaks down the current differences.
Tested on: Windows 11 25H2 · PowerShell 7 – Updated August 2026
