Packaging and install issues on Windows
Issues the maintainers labelled both platform:windows and area:packaging.
210 issues · 28 open · 182 resolved (87%) · first seen Jun 5, 2025
Is this getting better or worse?
This class of problem is holding steady. 38 new reports in the last 90 days vs 48 in the 90 before — -21%. The open backlog peaked at 42 in 2026-02 and sits at 28 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
126 of these reports name the Claude Code build they were running, spanning 75 releases. Heaviest reporters:
- Claude Code v2.1.39
- Claude Code v2.1.114
- Claude Code v2.1.112
- Claude Code v2.1.29
- Claude Code v2.1.15
- Claude Code v2.1.14
- Claude Code v2.1.229
- Claude Code v2.1.227
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 33 days across 182 closures. Of the 182 closures with a recorded reason, 34% were closed as completed and 120 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
64 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Native Windows(Powershell) install of Claude Code is not viable
- Ran into this same issue tonight. Found workarounds that might help others: The binary does exist It's bundled inside the VS Code extension: Workaround Open a new PowerShell window and should work. Note: When the VS Code…
Found in the thread of #14902 · resolved - [BUG] Cowork tab not showing on Windows 11 Pro x64 — "yukonSilver" marked as unsupported + CoworkVMService cannot be removed
- …ot appear in the non-admin user's Start menu.</p <p <strong Workaround found:</strong Running <code Add-AppxPackage</code manually as the target user installs the MSIX correctly for that user.</p <h2 Steps to Reproduce</…
Found in the description of #25136 · resolved - Feature Request: Native Windows Claude Code CLI
- …large segment of the enterprise development market. Current workarounds (pre-staging context, manual command execution) significantly reduce CC's value proposition for Windows developers. The enterprise .NET ecosystem re…
Found in the description of #2458 · resolved - [BUG] Bun v1.3.5 crashes on Windows with "integer does not fit in destination type" - prevents installation and startup
- …n which also started happening recently ([link]( For now my workaround is to use wsl instead of powershell or the GUI
Found in the thread of #18567 · still open - [BUG] Claude Code crashes with Bun panic in Visual Studio Code on Windows 11
- …settings / advanced settings / more advanced settings) is a workaround to fix this.
Found in the thread of #19666 · still open
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–100
Ranked by community engagement (reactions weighted over comments).
- [BUG] Native Windows(Powershell) install of Claude Code is not viable
- [BUG] Cowork tab not showing on Windows 11 Pro x64 — "yukonSilver" marked as unsupported + CoworkVMService cannot be removed
- Feature Request: Native Windows Claude Code CLI
- [BUG] CC crashes with new release of Nodejs v25
- [BUG] Bun v1.3.5 crashes on Windows with "integer does not fit in destination type" - prevents installation and startup
- [BUG] Claude Code crashes with Bun panic in Visual Studio Code on Windows 11
- No uninstall documentation for the native Claud Code build (Windows)
- [BUG] Windows installer reports success but fails to create claude.exe in target directory
- [VS Code Extension] v2.1.129 fails to activate on Windows: hardcoded Linux CI path in bundled SDK (regression)
- [BUG] Cowork for windows: yukonSilver not supported
- [BUG] Claude Desktop installer falsely detects Windows S Mode on Windows 10 IoT Enterprise LTSC
- Repeated Bun v1.3.5 segfaults -- 78 crashes, root cause identified (Windows + WSL)
- [BUG] Bun has crashed. This indicates a bug in Bun, not your code.
- [BUG] Claude Desktop opening when running "claude" in Powershell ( Windows )
- [BUG] VS Code extension v2.1.136 (win32-x64) fails to activate — hardcoded Linux CI path in createRequire (regression of #56549, #56725)
- [BUG] CRITICAL BUG: Claude Code keyboard input blocked after crash - Windows 11 24H2
- [BUG] VS Code extension installation fails with 'End of central directory record signature not found' on /status
- [BUG] Input freezes on Windows when launching Claude Code from certain directories (native installer)
- Auto-update breaks @file_path functionality, displays only subagent options
- Update notification always shown for winget installations due to npm version check
- [BUG] No win32-arm64 binary exists.
- [BUG] Cowork Windows - MSIX installs for elevating admin user, not calling standard user (split-account enterprise environment)
- [BUG] Version 2.1.0 released
- [BUG] - Native installation v2.1.15 interactive mode exits immediately on WSL (Ubuntu 20.04)
- [BUG] Update available! Run: winget upgrade Anthropic.ClaudeCode
- [BUG] Devcontainer init-firewall.sh duplicate ip failure
- [BUG] Auto-update failed error persists after manual update
- [BUG] claude CLI Not Recognized After Global Installation on Windows
- [BUG] Powershell Native Install does not copy claude.exe
- [BUG] Something keeps installing old version of Claude every day or so
- [BUG] 2.1.237 tagged `latest` with its linux-x64, win32-x64 and linux-x64-musl native packages never published - installs land on a dead 500-byte stub
- Native binary leaks ~7MB .node files to temp directory on each session (Windows)
- [BUG] Auto-update to 2.1.237 leaves broken stub on Windows: claude-code-win32-x64@2.1.237 missing from npm registry (incomplete release)
- [BUG] Silent graceful exit during Write/Bash operations on Windows (NPM installation)
- NVM Node Version Switch Breaks Claude Code Installation on Windows
- [BUG] Title: VS Code extension crashes on CPUs without AVX support (Bun panic)
- Bundled Bun 1.3.5 crashes on Windows with integer overflow
- [BUG] Installing native binary via PowerShell script installs 0KB claude.exe
- [BUG] — Claude Code Windows v2.1.175 launches as Bun instead of Claude
- Claude Code v2.1.112+ crashes with Segmentation Fault (0xc0000005) on Windows 11
- [BUG] claude was corrupted/removed durring an active session and unable to re-install
- [BUG] PowerShell installer crashes with Bun ENOTCONN error on Windows 11
- [BUG]
- [BUG] Restart to apply stuck, no way to update
- [BUG] Native install create zero bytes claude.exe
- Bun v1.3.11 panic (Internal assertion failure) on Windows 11 with AVX-512 CPU - regression since v2.1.85
- hello - what's going on? API Error: 500...
- File Search Returns No Results Despite Matching Content
- [BUG] Bun startup segfault on Windows 11 26200 + Intel Meteor Lake (Core Ultra 5 135U) — reproduced on current 2.1.170; prior report #55219 auto-closed as stale
- [BUG] Segmentation fault（Bun Canary v1.3.9-canary.51）with Windows 11 Powershell
- [BUG] update to 2.1.25 don't work on windows
- [BUG] Claude Code VScode completely broken on Windows - Bun 1.3.5 crashAll products crash on startup:
- [BUG] Both VS Code extension and CLI crash with Bun v1.3.5 "integer does not fit in destination type" on Windows 11 - v2.1.19 still affected
- [BUG] Native Windows executable crashes with segmentation fault (npm version works)
- [FEATURE] Publish to WinGet repository from release CI / CD
- [BUG] - CRITICAL
- [BUG] Existing Squirrel-based Claude Desktop users cannot upgrade to MSIX — silent failure (0x80073CFA)
- Claude Code 2.1.15 crashes on Windows 11 with Bun segmentation fault (address 0x113)
- [BUG] claude in Windows with side effects after using some commands
- Windows: .local\bin\claude.exe installs as plain Bun v1.4.0 instead of Claude Code
- [BUG] Deterministic Bun startup segfault at USER32.dll+0xbe584 / address 0x3C on Windows 11 build 26200 (claude.exe 2.1.114+) — distinct from 0xFFFFFFFFFFFFFFFF family
- Claude Code for VS Code 2.1.51 fails to launch
- npm install: silent crash to command prompt on large paste input (Windows)
- claude install reports installing v2.1.25 but actually keeps v2.1.23
- [Bug] Claude Code version not updating after npm install -g
- [BUG] Claude failing to copy on update.
- [BUG] Deterministic Bun segfault at 0xCD on Windows 10 — Trend Micro Apex One DLLs (TmUmEvt64 / Wtmmon64) in crash stack; 2.1.112 (Node) works, 2.1.113+ (Bun) crash
- [BUG] Persistent "update available" notification despite being on latest version
- [BUG] GetThreadDescription entry point error on Windows Server 2016 starting with v2.1.113/2.1.114
- [BUG] Native installer (claude.exe) freezes indefinitely in VS Code terminal on Windows
- [BUG] Update to 2.0.14 on Windows is broken
- [BUG] Windows native cannot update
- Update banner should show the new version (and ideally a one-line summary)
- [BUG] Possible Windows binary incompatibility in 2.1.113 (claude.exe fails to run)
- [BUG]
- [BUG] "ReferenceError: Bun is not defined" fires repeatedly on Windows (npm install), causes crashes
- Windows installer falsely detects concurrent installation, --force flag ignored
- Bun 1.3.14 integer overflow panic on Windows x64 after long-running session (low memory) - claude 2.1.145
- [BUG] False "Update available!" prompt persists after updating on Windows (winget release lag)
- Bun segfault crash (0xFFFFFFFFFFFFFFFF) on Windows during normal usage
- [BUG] uild/packaging bug in Claude Code v2.1.51
- [FEATURE] Ship Claude Code as a standalone binary (ideally Rust)
- [BUG] Claude code extension does not update
- [BUG] Double Ctrl+C deleted claude.exe, install.ps1 failed to reinstall (Windows)
- [BUG] 'Update available' banner checks npm latest but suggests winget upgrade — winget manifest lag makes the banner permanent on Windows
- [BUG] `claude update` on Windows downloads wrong platform binary — CLI completely broken after upgrading to 2.1.114**
- [BUG] @anthropic-ai/claude-code@2.1.114版本win11打开报错不支持16为应用
- [SYS-034] v2.1.113 native binary switch terminates running sessions on upgrade — API Error: terminated
- Claude code vscode extension is being updated too many times
- False warning: native installation path is not in PATH even though it already is (Windows)
- Claude Desktop Installer Hijacks Claude Code CLI Command
- [BUG] SyntaxError: Too many arguments (65535 limit) on restart after session crash - Node.js v22.22.0
- [BUG] Segmentation fault (exit code 3) on Windows 11 - Bun v1.3.6 crash at 0xCC/0xD0 during startup
- [BUG] 2.1.204.0 Just opens Bun instead of claude
- [BUG] Claude Code extension fails to activate in Cursor (and possibly VS Code)
- [BUG] Cowork's `spawnLocalProcess` fails immediately with `errno: -4094, code: 'UNKNOWN', syscall: 'spawn'` on enterprise Windows machines with WDAC (Windows Defender Application Control) kernel-mode enforcement enabled.
- MSYS2 fork failure (0xC0000142) makes all tools unusable even with Git in correct location
- [BUG] 2.1.32 cannot installed on arm64 (surface pro 11)
- [BUG] CC barfs unintelligble text to the terminal after native installer
- [BUG] Claude Code Non Interactive weird version error