[BUG] Native windows install fails

[gattimassimo]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Context: I have a Surface 7 ARM laptop and latest Windows updates, Powershell.

While I'm not able to install Claude code using Powershell (the claude.exe is not dropped in C:\Users\magatti.local\bin\claude.exe) I read about multiple issues and workarounds and none of them unblocks, the issue still persists.

Then I switched over to use cmd as documented in the claude code setup steps and I found a bug which blocks the installation. See repro steps.

It seems that if I download the cmd file and run it locally it works, but if I use the one line command it doesn't.

Thanks

What Should Happen?

The setup steps documented on this page should work.

https://code.claude.com/docs/en/quickstart#step-1:-install-claude-code

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

Error Messages/Logs

I'd be happy to know how to get some logs, better error messages during the install process.

Steps to Reproduce

`
C:\Users\magatti\claudeDowloadSetup>curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
Setting up Claude Code...

Installing Claude Code native build latest...
Installation failed

C:\Users\magatti\claudeDowloadSetup>curl -fsSL https://claude.ai/install.cmd -o install.cmd

C:\Users\magatti\claudeDowloadSetup>install.cmd
Setting up Claude Code...

√ Claude Code successfully installed!

Version: 2.1.7

Location: C:\Users\magatti.local\bin\claude.exe

Next: Run claude --help to get started
Warning: Could not remove temporary file: C:\Users\magatti.claude\downloads\claude-2.1.7-win32-x64.exe

Installation complete!

C:\Users\magatti\claudeDowloadSetup>
`

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.7

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[nocdoggo]

Have you tried to use npm to install manually? This would give an usable version for Windows on ARM.

[gattimassimo]

Npm works fine.

[Deathhush]

Got same issue here. And my machine is also Surface 7 ARM. It suddenly stops working today. Not sure if it is due to claude code upgrading to 2.1.7 or it is due to Windows Update. After I uninstall and tried to install a specific version again, hit the same issue.

Using NPM install solves the problem and 2.1.7 now runs fine on the machine. But it still prompts that "settings say it is native installation but actually is npm installation". Does anyone know how to fix that?

Also, what's the problem with native installation on Windows ARM?

[shanselman]

I'm here also and Naive on windows is broken completely. I am also on Windows Arm

 └ Currently running: native (2.1.19)
 └ Path: C:\Users\scottha\.local\bin\claude.exe
 └ Invoked: C:\Users\scottha\.local\bin\claude.exe
 └ Config install method: native
 └ Search: OK (bundled)

 Updates
 └ Auto-updates: enabled
 └ Auto-update channel: latest
 └ Stable version: 2.1.7
 └ Latest version: 2.1.19

 Version Locks
 └ No active version locks

 Press Enter to continue…

run it...LONG pause and then it's gone.

[nocdoggo]

Second on this, so far only the npm install works, and then once installed, running claude update is a hit or miss, sometimes won't get through.

Also, have the banner saying that npm method is deprecating.

[chrsdrhm]

Same here. Looks like the native install on arm is pulling the x64 binary for Claude, whereas the npm install appears to be the arm64 binary.

[ant-kurt]

Claude Code is now available for Windows ARM64 via install.ps1, install.cmd, and winget - see https://code.claude.com/docs/en/quickstart#step-1-install-claude-code (starting with version 2.1.41 for installer scripts, 2.1.42 for winget)

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.