[BUG] Windows Update KB5074109 Breaks Claude Code
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?
I have been using CC native install on Windows 11 (ARM) for many months.
Yesterday, Windows Update ran KB5074109. After this update was installed, claude code would not start and would say "Segmentation fault" whenever invoked.
Thinking that maybe my CC installation was corrupted, I completely uninstalled CC and then tried reinstalling using the PowerShell script for Windows native install. The script would complete successfully but the binary would not get written to the .local\bin directory. (Similar to #18183)
I manually uninstalled Windows update KB5074109, after which, CC was able to install and run fine.
I believe this may be related to x64 emulation on ARM64 Windows, as I do not have this issue on my native x64 machine.
KB5074109 is labeled by Microsoft as a required security update, so my corporate AD-joined computer doesn't have the ability to uninstall this update, and I imagine many other users will have this update installed automatically in the coming days.
What Should Happen?
Claude Code should install and/or run normally as it did prior to the installation of KB5074109.
Error Messages/Logs
Checking installation status...
Exit code: -1073741819 (Access violation)
AzureAD+RedactedUser@DEV-PC CLANGARM64 /c/LocalRepositories/RedactedPath
$ claude
Segmentation fault
Steps to Reproduce
Run windows update KB5074109 and then try to install or run CC on Windows 11 ARM.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
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_
22 Comments
ran into this all day working on electrobun, i thought I was losing my mind. Claude code doesn't open, but also the electrobun cli (which is a bun sfe) also exits with code 5.
I just reported this over at https://github.com/oven-sh/bun/issues/26150 before I found this issue
I'm in a windows ARM vm on a macbook m4 host, so windows x64 isn't an option.
I ran this in a powershell and restarted, and then reinstalled bun and then claude and bun/electrobun cli both work again
wusa /uninstall /kb:5074109gonna go think about how microsoft just sent me down this rabbit hole on the day I was finishing up windows compatibility for Electrobun v1

Same. Glad to see I'm not alone out there. My colleagues and I also use Windows 11 in Parallels on M4 Pro Mac Minis.
Glad I'm not alone, would love a fix though
The VSCode claude extension still works, but cant reference folders in it so feels gimped
Confirming this issue on Windows 11 ARM64 in Parallels Desktop (Mac host)
Environment:
Segmentation faultimmediately when runningclaudeObservations:
claude --versionandclaude --helpwork fineclaude doctor,claude -p "test") crashes with segfaultWorking workaround:
The npm installation works without issues, confirming this is specific to the native binary + x64 emulation on ARM64.
Request: A native
win32-arm64binary would resolve this permanently. With the growing adoption of ARM64 Windows devices (Surface Pro, Snapdragon X Elite laptops, Parallels VMs on Apple Silicon), native ARM64 support is increasingly important.Starting last night CC on Parallels, without the KB installed (have an uninstall script I use to keep it off)... it just refuses to load now, well I see the interface, then it crashes a few seconds later.
So fun
<img width="361" height="29" alt="Image" src="https://github.com/user-attachments/assets/e78f9b67-324f-4246-a269-c0cc4e6ff4ac" />
v2.1.41 today
@sitefinitysteve Thanks for the update, I appreciate it. Have you tested to see if it's working as expected?
Moved back to native from NPM, she's not crashing here, says I have all my windows updates, Latest Parallels on M3 Max Windows 11 ARM. Cautiously optomitic.
Does that mean win32-arm64 releases are coming?
Pete
Microsoft
It’s here
Thanks. I really asked the wrong question.
Are fully functional windows Arm64 builds, equivalent to macOS functionality, coming as a result of this?
<img width="993" height="677" alt="Image" src="https://github.com/user-attachments/assets/544233a6-2cc2-4259-9b1d-eb3a730281fe" />
Thanks.
Claude Code (the CLI) 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)
Bringing local sessions to Claude Code on desktop for Windows ARM64 - we're working on this!
Fantastic! Thank you :)
Pete
Microsoft
On this, did you create your own Bun Arm64 release, or is Bun not a dependency for the CLI?
Pete
Microsoft
My recollection is that they use node.js not bun.
Actually, I take that back. Using the current CC ARM64 2.1.47 (native install) shows:
Bun v1.3.10 (1423d3c8) Windows arm64That's unexpected. On the Bun repo, it shows as still not building for Windows. Maybe a late fix?
Pete
Microsoft
From Bun's blog:
Windows ARM64
We've added JIT & interpreter support for Windows ARM64 to JavaScriptCore. This was the main blocker for unblocking Windows ARM64 support in Bun. We don't yet support Windows ARM64 in Bun, but it's coming soon.
Bun now has Arm64 support in their canary builds, as of yesterday. :)
Pete
Microsoft
Not Just Windows Update — Bun v1.3.10 Is Fundamentally Unstable on Windows
While Windows updates may trigger or expose this, the root cause is in Bun v1.3.10's N-API layer. 20+ separate crash issues, 90 unique users — segfaults, "switch on corrupt value" panics (7 issues), TUI escapes, pipe write crashes. All Windows, all Bun v1.3.10.
Community root cause analysis on #21875 (27 memory dumps, WinDbg traces, N-API race condition identified). high-priority + oncall labels for 30+ days, zero staff response. v2.1.53's 4 crash fixes didn't help.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.