Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Windows 11 Pro 24H2: segmentation fault during PowerShell install, and also when launching `claude.exe` after WinGet install

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 Windows 11 Pro 24H2, Claude Code hits a segmentation fault in two related scenarios on the same machine:

  1. During installation via the official PowerShell installer: irm https://claude.ai/install.ps1 | iex
  2. After installation via WinGet, when launching claude.exe in interactive mode

In the WinGet case, claude.exe --version works, but claude.exe crashes immediately with a segmentation fault.

This appears to affect both the installer path and the runtime startup path in the same environment.

Error Message

Error Messages/Logs

Root Cause

On Windows 11 Pro 24H2, Claude Code hits a segmentation fault in two related scenarios on the same machine:

  1. During installation via the official PowerShell installer: irm https://claude.ai/install.ps1 | iex
  2. After installation via WinGet, when launching claude.exe in interactive mode

In the WinGet case, claude.exe --version works, but claude.exe crashes immediately with a segmentation fault.

This appears to affect both the installer path and the runtime startup path in the same environment.

Code Example

irm https://claude.ai/install.ps1 | iex

### What Should Happen?

Scenario One (installation via the official PowerShell installer):
The installer should complete without crashing.

ScenarioTwo (After installation via WinGet, when launching `claude.exe` in interactive mode):
claude.exe should start normally and enter the interactive CLI.

### Error Messages/Logs
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?

Summary

On Windows 11 Pro 24H2, Claude Code hits a segmentation fault in two related scenarios on the same machine:

  1. During installation via the official PowerShell installer: irm https://claude.ai/install.ps1 | iex
  2. After installation via WinGet, when launching claude.exe in interactive mode

In the WinGet case, claude.exe --version works, but claude.exe crashes immediately with a segmentation fault.

This appears to affect both the installer path and the runtime startup path in the same environment.

Environment

  • OS: Windows 11 Pro 24H2
  • Architecture: x64
  • Claude Code version: 2.1.132
  • Bun runtime shown in output: v1.3.14
  • Shell: PowerShell

Scenario 1: Official PowerShell installer crashes during install

Command

irm https://claude.ai/install.ps1 | iex

### What Should Happen?

Scenario One (installation via the official PowerShell installer):
The installer should complete without crashing.

ScenarioTwo (After installation via WinGet, when launching `claude.exe` in interactive mode):
claude.exe should start normally and enter the interactive CLI.

### Error Messages/Logs

```shell
Scenario One:
PS C:\Users\xxxx> irm https://claude.ai/install.ps1 | iex
Setting up Claude Code...
============================================================
Bun v1.3.14 (0a466a11) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\xxxx\.claude\downloads\claude-2.1.132-win32-x64.exe" "install" "latest"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc spawn(2) standalone_executable yaml_parse claude_code
Builtins: "bun:ffi" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:readline" "node:stream" "node:stream/consumers" "node:stream/promises" "node:string_decoder" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "undici" "ws" "node:http2"
Elapsed: 1134ms | User: 640ms | Sys: 531ms
RSS: 0.35GB | Peak: 0.35GB | Commit: 0.47GB | Faults: 86852 | Machine: 17.01GB

panic(main thread): Segmentation fault at address 0x40FE0

panic: Segmentation fault at address 0x224DB95FFE8
panicked during a panic. Aborting.

✅ Installation complete!

PS C:\Users\xxxx>

Scenario Two:
winget install Anthropic.ClaudeCode

PS C:\Users\xxxx> claude.exe --version
2.1.132 (Claude Code)

S C:\Users\xxxx> claude.exe
============================================================
Bun v1.3.14 (0a466a11) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\xxxx\AppData\Local\Microsoft\WinGet\Packages\Anthropic.ClaudeCode_Microsoft.Winget.Source_8wekyb3d8bbwe\claude.exe"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch jsc spawn(2) standalone_executable yaml_parse claude_code
Builtins: "bun:ffi" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:readline" "node:stream" "node:stream/consumers" "node:stream/promises" "node:string_decoder" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "ws" "node:http2"
Elapsed: 1209ms | User: 828ms | Sys: 515ms
RSS: 0.35GB | Peak: 0.35GB | Commit: 0.44GB | Faults: 87513 | Machine: 17.01GB

panic(main thread): Segmentation fault at address 0x40FE0

panic: Segmentation fault at address 0x25CD944FFE8
panicked during a panic. Aborting.
PS C:\Users\xxxx>

Steps to Reproduce

Scenario One:

  1. Enter Power Shell
  2. Run the following: irm https://claude.ai/install.ps1 | iex

Scenario Two:

  1. Enter Power Shell
  2. Run the following to install claude.exe winget install Anthropic.ClaudeCode
  3. Open another Power Shell and run the followings: claude.exe --version claude.exe

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.132

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

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…
#installation#batch processing#GPU compatibility#latency issue#model 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