claude-code - 💡(How to fix) Fix [Bug] Native installer on Surface Pro 13 (ARM64) defaults to win32-x64 and causes Segmentation Fault

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On a Surface Pro 13 (ARM64) running Windows 11, the native installation method incorrectly installs the win32-x64 binary instead of the win32-arm64 version. This leads to frequent Segmentation Fault (ACCESS_VIOLATION) crashes when running the claude command due to emulation layer issues.

Error Message

Error Messages/Logs

Root Cause

On a Surface Pro 13 (ARM64) running Windows 11, the native installation method incorrectly installs the win32-x64 binary instead of the win32-arm64 version. This leads to frequent Segmentation Fault (ACCESS_VIOLATION) crashes when running the claude command due to emulation layer issues.

RAW_BUFFERClick to expand / collapse

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?

Description

On a Surface Pro 13 (ARM64) running Windows 11, the native installation method incorrectly installs the win32-x64 binary instead of the win32-arm64 version. This leads to frequent Segmentation Fault (ACCESS_VIOLATION) crashes when running the claude command due to emulation layer issues.

Environment info (from claude doctor)

  • Platform: win32-x64 (Incorrectly detected on ARM64 device)
  • Path: C:\Users\liang.local\bin\claude.exe
  • Config install method: native
  • Commit: c900a8c71aa9
  • Stable version: 2.1.140

What Should Happen?

Entering Claude Code CLI interface.

Error Messages/Logs

Steps to Reproduce

  1. Use a Windows ARM64 device (e.g., Surface Pro 13 with Snapdragon X Elite).
  2. Install via the native PowerShell command.
  3. Run claude.
  4. The CLI frequently crashes with a segmentation fault.

Expected Behavior

The installer should detect the ARM64 architecture and install the native win32-arm64 binary.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.140

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Git bash on Windows

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Native installer on Surface Pro 13 (ARM64) defaults to win32-x64 and causes Segmentation Fault