[BUG] Native Windows executable crashes with segmentation fault (npm version works)

Resolved 💬 6 comments Opened Jan 25, 2026 by DamianReeves Closed Mar 26, 2026

Preflight Checklist

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

What's Wrong?

Environment:

OS: Windows (ARM64)
Node.js: v24.12.0 (via nvm/scoop)
Claude Code version: 2.1.7 & 2.1.19 (native binary)
Shell: Git Bash
Issue:
The native Windows executable (claude.exe) crashes with a segmentation fault when running commands like claude doctor or claude -p "test". The --version and --help flags work.

Error:

Exit code 139
Segmentation fault

ERROR Raw mode is not supported on the current process.stdin, which Ink uses as input stream by default.
Workaround:
Installing via npm (npm install -g @anthropic-ai/claude-code) works without issues.

Notes:

VSCode extension works fine (uses bundled runtime)
Issue started after switching from npm to native executable

What Should Happen?

Claude shouldn't crash

Error Messages/Logs

Exit code 139
Segmentation fault

ERROR Raw mode is not supported on the current process.stdin, which Ink uses as input stream by default.
Workaround:
Installing via npm (npm install -g @anthropic-ai/claude-code) works without issues.

Steps to Reproduce

Install the native version of claude 2.1.7 or 2.1.19 on windows 11 arm64

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.18

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Claude works fine in WSL2 (Ubuntu 24) on the same machine

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗