[BUG] Windows native cannot update
Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Activity 9 comments · opened Aug 13, 2025 · closed Aug 22, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.71 native
- Operating System: Windows 10
- Terminal: WindowsTerminal + powershell 7.5.2
Bug Description
cannot update,claude update is not work
Steps to Reproduce
claude update
Current version: 1.0.71
Checking for updates...
Successfully updated from 1.0.71 to version 1.0.77claude -v
1.0.71 (Claude Code)Expected Behavior
Upgrade to the new version normally
Actual Behavior
Although the claude update command shows a successful upgrade in the output, it actually remains on the old version
Additional Context
claude doctor --debug
[DEBUG] Using bash path: "C:\Program Files\Git\bin\bash.exe"
[DEBUG] Writing to temp file: C:\Users\Administrator\.claude.json.tmp.24816.1755051829373
[DEBUG] Preserving file permissions: 100666
[DEBUG] Temp file written successfully, size: 63013 bytes
[DEBUG] Applied original permissions to temp file
[DEBUG] Renaming C:\Users\Administrator\.claude.json.tmp.24816.1755051829373 to C:\Users\Administrator\.claude.json
[DEBUG] File C:\Users\Administrator\.claude.json written atomically
[DEBUG] MCP server "context7": Starting connection attempt
[DEBUG] MCP server "context7": No token data found
[DEBUG] MCP server "context7": No token data found
[DEBUG] MCP server "context7": No token data found
[DEBUG] MCP server "context7": Connection attempt completed in 1160ms - status: connected
[DEBUG] MCP server "context7": No token data found
Diagnostics
└ Currently running: native (1.0.71)
└ Path: native
└ Invoked: B:/~BUN/root/claude.exe
└ Config install method: native
└ Auto-updates enabled: true
Memory Files · 1k tokens
└ User (C:\Users\Administrator\.claude\CLAUDE.md): 0k tokens
└ Project (C:\github\test\mtga\CLAUDE.md): 0.9k tokens
MCP Tools · 0.4k tokens
└ mcp__context7__resolve-library-id (context7): 0.3k tokens
└ mcp__context7__get-library-docs (context7): 0.1k tokens
9 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Supplement:
You can update using the native installation command
irm https://claude.ai/install.ps1 | iexOnly the built-in update command
claude updatedoes not workThe only way I've been able to update the Windows Claude install is to remove the native binary from .local/bin and then running the PS install script. running claude update or claude doctor indicates that the update was successful but it never goes through.
@BumpyClock Yeah. But maybe removing the native binary from .local/bin is not necessary.I can update directly by running the native install command
irm https://claude.ai/install.ps1 | iex.It seems to me it is necessary as in my case running that install script didn't in fact override the existing version.
Ah, I see an issue--I had one claude instance running in the background that I forgot about and Windows doesn't handle modifying files in-use like UNIX-like systems. The problem is the script reports success where it should report failure.
claude updatestill doesn't work though.I've had mixed experiences. I close bun.exe and that usually nukes any claude processes but even if I don't have an instance running actively running I've had claude doctor sometimes leave a phantom process running so if I run claude doctor followed by claude update it will fail sometimes while the script reports success, then I have to run claude doctor again to verify if it updated or not. I just end up deleting claude.exe from .local/bin and then running claude update to ensure that the update actually goes through.
This should be working better in 1.0.87 - old versions will be renamed and cleaned up on next Claude process start (if no other Claude processes are running).
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.