›_ Claude Code Issues
Claude Code Issues / #57159

[BUG] Windows 11 Pro 24H2: segmentation fault during PowerShell install, and also when launching `claude.exe` after WinGet install

Status Closed — not planned
Reported on v2.1.132
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 12 comments · opened May 8, 2026 · closed Jul 8, 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?

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

  1. 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

  1. 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_

View original on GitHub ↗

12 Comments

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/50640
  2. https://github.com/anthropics/claude-code/issues/51464
  3. https://github.com/anthropics/claude-code/issues/55219

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

marvinwnc · 3 months ago

I think my issue is different from the three possible duplicate issues.

  1. Issue 50640:

According to the issue description, version v2.1.111 worked well. Howeve, I tried to download v.2.1.111. The issue is still there.
PS C:\Users\xxxx> & ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.111
....
panic(main thread): Segmentation fault at address 0x40FE0
panic: Segmentation fault at address 0x1B1B5CCFFE8

  1. Issue 51464:

The issue happened when running /init. However, my issue happened for both installation and running command claude.exe.

  1. Issue 55219:

It mentioned version 2.1.110 worked. However, I still could not download 2.1.110 successfully.
PS C:\Users\xxxx> & ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.110
....
panic(main thread): Segmentation fault at address 0x40FE0
panic: Segmentation fault at address 0x215109CFFE8

marvinwnc · 3 months ago

When I installed the claude by "winget install Anthropic.ClaudeCode" under Power Shell, it did not crash for running claude --version and claude --help. However, it crashed for "claude -p "hello" and "claude".
Even I tested "claude --debug -p "hello", there is no any debugging log but just segmentation message.

maglore9900 · 3 months ago

Can confirm same behavior:
"When I installed the claude by "winget install Anthropic.ClaudeCode" under Power Shell, it did not crash for running claude --version and claude --help. However, it crashed for "claude -p "hello" and "claude".
Even I tested "claude --debug -p "hello", there is no any debugging log but just segmentation message."

Windows 11, powershell

Note, I also have Zed installed and have Claude Agent set up and have it pointing to my local Claude install rather than the built in Claude binary. Within Zed Claude works, but Claude crashes in Powershell and in Command shell.

I have uninstalled and reinstalled a few times, no change in behavior.

marvinwnc · 3 months ago

Yes, I installed the claude by "winget install Anthropic.ClaudeCode" under Power Shell, it did not crash for running claude --version and claude --help. However, it crashed for "claude -p "hello" and "claude".

netanbi87 · 3 months ago

happend to me also
Still broken on app 1.8555.2, binary 2.1.149, 12 days now. claude.exe --print "hello" segfaults at address 0x40FE0 every time. --version works but anything else crashes. Windows 11 Pro, i7-12850HX.

what is the fix???

Giancarlos · 3 months ago

I'm seeing this one on Arch Linux as well:

Bun v1.3.14 (521eedd6) Linux x64 (baseline)
Linux Kernel v7.0.5 | glibc v2.43+tab to cycle) · esc to interrupt

panic(main thread): Segmentation fault at address 0x0
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

In my case it saying address 0x0 is a little odd though...

netanbi87 · 3 months ago

Still broken on app 1.9255.2, binary 2.1.149+, Windows 11 Pro 24H2, Intel i7-12850HX. Broken since May 12 (~16 days). WSL workaround works but desktop app and VS Code extension are completely unusable.

for what we still paying if the that not work ????????????? more the 16days

serkanz · 3 months ago

as we cannot upgrade to latest version, we cannot use opus 4.8. provide a fix asap.

netanbi87 · 2 months ago

i also have that more then 3 weeks , in windows pc cloade code
Still broken on binary 2.1.160, Windows 11 Pro 24H2, i7-12850HX. Same segfault at 0x40FE0. 3+ weeks with no fix.
Claude Code crashedTry sending your message again. If it keeps happening, share feedback so we can investigate.
Claude Code process exited with code 3 ============================================================ Bun v1.3.14 (521eedd6) Windows x64 (baseline) Windows v.win11_dt CPU: sse42 avx avx2 Args: "<home>\AppData\Roaming\Claude\claude-code\2.1.160\claude.exe" "--output-format" "stream-json" "--verbose" "--input-format" "stream-json" "--effort" "low" "--model" "claude-sonnet-4-6" "--permission-prompt-tool" "stdio" "-"... Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch jsc spawn(2) standalone_executable yaml_parse(2) 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" "no Elapsed: 401ms | User: 328ms | Sys: 78ms RSS: 0.29GB | Peak: 0.29GB | Commit: 0.40GB | Faults: 72188 | Machine: 34.03GB panic(main thread): Segmentation fault at address 0x40FE0 panic: Segmentation fault at address 0x1294103FFE8 panicked during a panic. Aborting.

netanbi87 · 2 months ago

Claude Code process exited with code 3

============================================================
Bun v1.3.14 (521eedd6) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "<home>\AppData\Roaming\Claude\claude-code\2.1.161\claude.exe" "--output-format" "stream-json" "--verbose" "--input-format" "stream-json" "--effort" "low" "--model" "claude-sonnet-4-6" "--permission-prompt-tool" "stdio" "-"...
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch jsc spawn(2) standalone_executable yaml_parse(2) 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" "no
Elapsed: 516ms | User: 359ms | Sys: 218ms
RSS: 0.29GB | Peak: 0.29GB | Commit: 0.40GB | Faults: 72925 | Machine: 34.03GB
panic(main thread): Segmentation fault at address 0x40FE0
panic: Segmentation fault at address 0x268D203FFE8
panicked during a panic. Aborting.

github-actions[bot] · 1 month ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

Same class of failure, ranked by community engagement — this issue is one of many, so it may not appear in the visible list: Windows & WSL problems, Crashes, hangs & freezes

Browse all Claude Code issue topics →