Install Claude Code on Windows: Native and WSL Options

Claude Code installation guidance changes as Anthropic updates supported platforms and installers. Windows users should start with the current official quickstart, choose native Windows or Windows Subsystem for Linux based on the development environment, and validate security and repository behavior before using it on important code.

Choose the environment first

Use native Windows when the repository, shell, dependencies, and automation are designed for Windows. Use WSL when the project expects Linux commands, permissions, containers, or package behavior. Avoid editing the same working tree simultaneously through incompatible Windows and Linux toolchains without understanding file, path, and permission effects.

Verify the current installation source

Open Anthropic’s current quickstart immediately before installation and use only the supported vendor method for the chosen environment. Enterprise users should review downloaded or piped installer scripts under organizational policy rather than copying old commands from an article. Confirm architecture, shell, Git, authentication, proxy, certificate, and endpoint requirements.

Prepare a safe repository

• Create or switch to a task branch.
• Inspect the full working tree and protect unrelated changes.
• Remove secrets from files and terminal history.
• Set least-privilege repository and service credentials.
• Confirm tests, formatting, and rollback commands.
• Back up unique uncommitted work before experimentation.

Validate permissions and behavior

Begin with inspection and a small reversible change. Read every proposed command and diff, especially package installation, deletion, credential, network, and Git operations. Run project tests, review changed files, and confirm the tool did not modify unrelated work or access an unintended repository.

Operate and update deliberately

Record the installed version, source, update method, policy, account, and supported environment. Review Anthropic guidance before upgrades. If behavior changes, stop automation, preserve evidence, remove unnecessary credentials, and use the project’s normal rollback process rather than deleting broad directories.

Next step for your environment

Choose native Windows or WSL from the project’s actual toolchain, then follow the current official quickstart in a disposable test repository.

Record the accountable owner, baseline, source date, decision, exceptions, acceptance evidence, and review trigger. Test consequential changes in a bounded environment, maintain a rollback path, and verify the real result before closing the work. Product names, availability, pricing, legal requirements, and security guidance can change; recheck the primary sources whenever the decision is renewed or the environment changes.

If you need an independent baseline before changing production systems, start with an ITECS technology and security assessment and keep the resulting evidence with the decision record.

Sources and update trigger

• Anthropic — Claude Code quickstart
• Microsoft — Install WSL

Review trigger: Review after Claude Code installer, prerequisite, security, authentication, Windows, WSL, Git, or project-toolchain changes.