3 people reported
All time, since Sep 18.
Update leaves claude.exe stub
“On Windows, claude update on an npm-global install reports success but leaves bin\claude.exe as the 500-byte placeholder script.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/3200/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Update leaves 500-byte stub in place of claude.exe. On npm global installs, claude update or auto-update reports success but bin/claude.exe stays the placeholder script, so every claude command fails.
Is this your bug?
File my report- Where
- npm global install
- Error text
Error: claude native binary not installed.- Versions
- 2.1.276
- Platforms
- Linux, macOS, Windows
- How bad
- Breaks a normal workflow. Most reports say it used to work.
Original reports3, newest first
- npm auto-update during network outage replaces working install with 500-byte stub#101150
- [Windows] claude update (npm global) reports success but leaves 500-byte placeholder claude.exe: 'not a valid application for this OS platform'#96265
claude upgradereports success but leavesbin/claude.exeas the fallback stub — native binary not linked#95297