Plenty of guides assume you will spin up a full Linux subsystem before you touch an AI coding agent, but running Claude Code on Windows without WSL is now the simpler path for most people. Claude Code runs natively on Windows 10 build 1809 and later and on Windows 11, with no Linux subsystem, no Docker and no Node install required. The one piece worth adding first is Git for Windows, because it gives the agent a proper shell to run commands through -- though even that became optional in mid-2026.

Quick Answer

Install Git for Windows, then run the native installer in PowerShell with one command and launch with claude. With Git for Windows present, Claude Code uses Git Bash for shell commands; without it, it falls back to its built-in PowerShell tool, which still works for most workflows.

Why Install Git for Windows First

Claude Code needs a shell to execute the commands it writes. Git for Windows ships Git Bash, a POSIX-style shell, and when it is on your system the agent routes shell work through Bash. That matters because a large amount of tooling, scripts and documentation assumes Bash syntax, forward-slash paths and Unix utilities. Skip it and Claude Code falls back to PowerShell, which is perfectly usable but means some commands behave differently and a few common shell idioms will not translate cleanly.

Install Git for Windows from the official Git project, accept the defaults, and confirm it works by opening Git Bash and running a quick git --version. That single dependency is the whole difference between the no-WSL path and the WSL2 path.

The Native Install, Step by Step

Once Git for Windows is in place, the rest is short:

  1. Open PowerShell. You do not need an administrator window for the default user install.
  2. Run the official installer command: irm https://claude.ai/install.ps1 | iex. WinGet is an alternative if you prefer a package manager.
  3. Close and reopen your terminal so the updated PATH is loaded.
  4. Run claude --version to confirm the binary is on your PATH and see the version.
  5. Run claude in your project folder to start the first session and sign in when prompted.

If claude --version reports that the command is not found, the usual cause is a terminal that has not reloaded PATH. Restart the terminal and try again before assuming the install failed. A capable machine makes the whole experience smoother, and the AI-focused PC range at Evetech is built for exactly this kind of local development load.

What Differs From a WSL2 Setup

The practical gap is the shell. On WSL2 you are inside a real Linux environment, so file paths, permissions and tooling all behave the Linux way, and the Bash tool is native to that world. On native Windows with Git for Windows, you get Git Bash for shell commands but you are still on the Windows filesystem with Windows line endings and Windows path conventions.

For most front-end, scripting and general project work the native path is faster to stand up and avoids the overhead of a second operating system running alongside Windows. WSL2 still earns its place if your project genuinely depends on Linux-only binaries or a Linux build chain. For everything else, native plus Git for Windows is the leaner choice. Buyers shopping for a development machine often start from the best-selling desktop PCs at Evetech to find something with the cores and memory headroom an agent appreciates.

The PowerShell Tool and the Removal of the Git Dependency

Version 2.1.139, released in May 2026, shipped a native Claude Code PowerShell tool that replaces Bash as the default shell on Windows. The practical effect is that Git for Windows is no longer required: Claude Code on this version and later uses PowerShell natively for all shell commands without a fallback path. If you install on a fresh machine today and prefer not to add Git separately, you can skip it. The trade-off is losing Git Bash compatibility for scripts and tools that expect POSIX paths, which still matters for some workflows. For projects that do not depend on any POSIX tooling, a modern install without Git for Windows works cleanly from first launch.

If you are on an older installation, updating to 2.1.139 or later is straightforward. Run the installer command again and it overwrites the existing binary while keeping your configuration. After the update, the PowerShell tool is available regardless of whether Git for Windows is installed.

Troubleshooting Common Windows Install Issues

A few failure modes come up repeatedly on native Windows.

PATH not refreshed. This accounts for most "command not found" reports. The installer writes the binary to ~/.local/bin and updates your user PATH, but any terminal already open does not see the change. Close every terminal window and open a fresh one before testing.

32-bit PowerShell. The installer must run from a 64-bit PowerShell session. If you launched from the x86 version of Windows PowerShell, the binary will be the wrong architecture. Open the standard 64-bit PowerShell from the Start menu and re-run the install command.

Corporate proxy. If you are behind a strict firewall or a proxy that inspects TLS, the installer script may fail to download the binary. Try from a personal network or ask your network team to allow the claude.ai domain.

Frequently Asked Questions

Do I really not need WSL anymore?

Correct. Claude Code runs natively on Windows 10 build 1809 and up and Windows 11, with no WSL, Node or Docker required. WSL2 remains an option, not a requirement.

What does Git for Windows actually add?

It provides Git Bash, a POSIX-style shell, so Claude Code can run shell commands through Bash instead of falling back to its PowerShell tool. As of version 2.1.139 it is optional, but recommended for projects that rely on POSIX-style tooling.

How do I install it without admin rights?

The default PowerShell installer performs a per-user install, so you can run irm https://claude.ai/install.ps1 | iex without an elevated terminal. Reopen the terminal afterwards so PATH refreshes.

Claude says command not found after install. What now?

Almost always a stale PATH. Close every terminal window and open a fresh one so it reloads the environment, then run claude --version again before troubleshooting further.

Can I still use it from CMD or Git Bash?

Yes. Once installed and on your PATH, the claude command launches from PowerShell, CMD or Git Bash, so you can use whichever terminal you prefer.

Setting up a local AI coding workflow? Build it on a machine that keeps up by exploring the AI-ready PC range at Evetech and get started without the WSL overhead.