[BUG] update to 2.1.25 don't work on windows
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 tried to upgrade from 2.1.23 to solve beta error , and installation end with success but bin is not overwriten.
I tried install.sh , update same result, not admin account.
I don't have lock file
Finally I have renamed claude.exe and installation suceed
PS C:\Users\pp> irm https://claude.ai/install.ps1 | iex
Setting up Claude Code...
✔ Claude Code successfully installed!
Version: 2.1.25
Location: C:\Users\piotr.palka\.local\bin\claude.exe
Next: Run claude --help to get started
✅ Installation complete!
PS C:\Users\pp>
PS C:\Users\pp> claude --version
2.1.23 (Claude Code)
What Should Happen?
update should change version
Error Messages/Logs
no error msg
Steps to Reproduce
update from 2.1.23 to 2.1.25
windows 11
irm https://claude.ai/install.ps1 | iex
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.23
Claude Code Version
2.1.25
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
PowerShell
Additional Information
_No response_
11 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Workaround
The binary can be downloaded directly from Google Cloud Storage and manually replaced:
Direct download URL for 2.1.25 (Windows x64):
Steps:
``
bash
``curl -o claude_new.exe "https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.25/win32-x64/claude.exe"
~/.local/bin/claude.exe):``
bash
``mv ~/.local/bin/claude.exe ~/.local/bin/claude_old.exe
mv claude_new.exe ~/.local/bin/claude.exe
``
bash
``claude --version
# Should output: 2.1.25 (Claude Code)
Note: Replace
2.1.25in the URL with any desired version number for other releases.I did the workaround, but probably it's not only me who facing this issue.
[like] Ionut Babencu reacted to your message:
________________________________
From: Palkers76 @.*>
Sent: Friday, January 30, 2026 8:33:26 AM
To: anthropics/claude-code @.*>
Cc: Ionut Babencu @.>; Comment @.>
Subject: Re: [anthropics/claude-code] [BUG] update to 2.1.25 don't work on windows (Issue #21815)
[https://avatars.githubusercontent.com/u/59801882?s=20&v=4]Palkers76 left a comment (anthropics/claude-code#21815)<https://github.com/anthropics/claude-code/issues/21815#issuecomment-3822513453>
I did the workaround, but probably it's not only me who facing this issue.
—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/21815#issuecomment-3822513453>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWJOXJ4FMD3HXKECQHHOY5T4JMJNNAVCNFSM6AAAAACTL5E6DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRSGUYTGNBVGM>.
You are receiving this because you commented.Message ID: @.***>
same issue here
claude update
Current version: 2.1.23
Checking for updates to latest version...
Successfully updated from 2.1.23 to version 2.1.25
claude
╭─── Claude Code v2.1.23 ──────────────────────────────────────────────────────────────────────────────────────────────╮
had the same issue. manually downloaded and copied into the proper path and it updated. not sure if this was an isolated .23 bug. but confirming authenticity of bug.
[like] Ionut Babencu reacted to your message:
________________________________
From: s @.*>
Sent: Friday, January 30, 2026 4:23:11 PM
To: anthropics/claude-code @.*>
Cc: Ionut Babencu @.>; Comment @.>
Subject: Re: [anthropics/claude-code] [BUG] update to 2.1.25 don't work on windows (Issue #21815)
[https://avatars.githubusercontent.com/u/223721492?s=20&v=4]s070681 left a comment (anthropics/claude-code#21815)<https://github.com/anthropics/claude-code/issues/21815#issuecomment-3824568025>
had the same issue. manually downloaded and copied into the proper path and it updated. not sure if this was an isolated .23 bug. but confirming authenticity of bug.
—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/21815#issuecomment-3824568025>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWJOXJ7HJT6X6IVTXOMWPLT4JOAO7AVCNFSM6AAAAACTL5E6DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRUGU3DQMBSGU>.
You are receiving this because you commented.Message ID: @.***>
Me acaba de pasar lo mismo para tratar de actualizar Claude Code de 2.1.31 a 2.1.34
Solución
Ejecuta esto en PowerShell antes de actualizar:
1. Renombra el binario actual
Rename-Item "$env:USERPROFILE\.local\bin\claude.exe" claude_old.exe
2. Ahora sí, actualiza
irm https://claude.ai/install.ps1 | iex
3. Verifica
claude --version
Root cause identified: The Windows binary replacement function (internally
N3Ein the bundled source) short-circuits when the existing and new binaries have the same file size:This means any version bump where the
win32-x64binary size is unchanged will silently skip the update — even though the content (and checksums) differ. The GCS manifest confirms identical sizes across affected version pairs, e.g.:size: 235398304, checksum95d1412c...size: 235398304, checksum533f6345...This size check is the only guard before the atomic rename+copy path on Windows. On non-Windows platforms, the function takes a different branch (symlink-based), which is why this is Windows-specific.
Suggested fix: Replace the size comparison with a checksum comparison against the staged binary's known hash (already available from the manifest verification step), or remove the short-circuit entirely — the atomic rename+copy that follows is already safe and idempotent.
This also explains why the rename workaround reported earlier in this thread works: removing the existing file means the
staton the destination throws, the size check is skipped, and the fresh-copy branch executes instead.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.