[BUG] `claude update` on Windows downloads wrong platform binary — CLI completely broken after upgrading to 2.1.114**

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?

After running claude update to upgrade from version 2.1.112 to 2.1.114, the claude.exe binary became corrupted or was replaced with an incompatible binary. The CLI completely stops working — even claude update itself fails. Windows reports that the executable is not a valid application for this OS platform. Additionally, Windows shows a popup dialog saying:

"Unsupported 16-bit Application — This program or feature '\??\C:\Users\Administrator\AppData\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe' cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available."

This suggests the claude.exe binary downloaded during the update is either a corrupted file, a 16-bit binary, or a binary built for a non-Windows platform (e.g., Linux ELF). Reinstalling via npm uninstall -g + npm install -g does NOT fix the issue — the same broken binary is downloaded from the registry.

What Should Happen?

The claude update command should download the correct platform-specific binary (Windows x64) and the CLI should continue to work after the update.

Error Messages/Logs

ResourceUnavailable: C:\Users\Administrator\AppData\Roaming\npm\claude.ps1:14
Line |
  14 |    & "$basedir/node_modules/@anthropic-ai/claude-code/bin/claude.exe"  …
     |    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Program 'claude.exe' failed to run: An error occurred trying to start process
     | 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe' with working directory 'E:\workspace\PPQ'. The
     | specified executable is not a valid application for this OS platform.At C:\Users\Administrator\AppData\Roaming\npm\claude.ps1:14 char:3 +   &
     | "$basedir/node_modules/@anthropic-ai/claude-code/bin/claude.exe"  … +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.


Windows popup dialog:

Unsupported 16-bit Application
The program or feature "\??\C:\Users\Administrator\AppData\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.

Steps to Reproduce

1. Have Claude Code installed globally on Windows 10/11 (x64) at version 2.1.112
2. Run claude update in PowerShell
3. Update completes successfully, upgrading from 2.1.112 → 2.1.114
4. Run claude — it fails with the error above
5. Run claude update — same error (cannot self-repair)
6. Try clean reinstall:

``powershell
npm uninstall -g @anthropic-ai/claude-code
npm cache clean --force
npm install -g @anthropic-ai/claude-code
``

1. Run claude — still the same error

Environment

• Node.js architecture: x64 (node -p "process.arch" → x64)
• OS: Windows (64-bit)
• Shell: PowerShell
• Claude Model: N/A (cannot launch CLI to check)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.112

Claude Code Version

Cannot run claude --version — the CLI is broken. Last known version before update: 2.1.112. Attempted update target: 2.1.114.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

The fact that Windows detects claude.exe as a "16-bit application" is likely a generic error message — what's probably happening is the binary is for a different platform entirely (e.g., Linux x64 ELF binary), and Windows misidentifies it. This points to a bug in the update mechanism that downloads the wrong platform's binary during claude update on Windows. The npm registry package may also be shipping the wrong binary for the win32-x64 platform.