[BUG] Claude Code Auto-Updater Not Replacing Active Executable on Windows
Resolved 💬 3 comments Opened Aug 18, 2025 by asfar-decmil Closed Aug 20, 2025
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x] Other: Claude Code
- Claude CLI version: 1.0.67
- Operating System: Windows 11
- Terminal: Windows Powershell
Bug Description
Environment
- OS: Windows (PowerShell)
- Claude Code Version: 1.0.67 (attempting to update to 1.0.83)
- Installation Type: Native Windows installation with auto-updates enabled
Issue Description
The claude update command reports successful updates but the active executable is not replaced, causing the old version to continue running.
Steps to Reproduce
- Run
claude update - Receive message:
Successfully updated from 1.0.67 to version 1.0.83 - Run
claude --versionor/statuswithin Claude - Version still shows as
1.0.67
Investigation Findings
- Active executable location:
C:\Users\[username]\.local\bin\claude.exe(remains at old version) - New versions downloaded to:
C:\Users\[username]\.local\share\claude\versions\ - Version 1.0.83 successfully downloaded as:
C:\Users\[username]\.local\share\claude\versions\1.0.83 - The updater downloads new versions but fails to copy them to the active bin location
Current Workaround
Manually copying the new version:
Copy-Item "C:\Users\[username]\.local\share\claude\versions\1.0.83" -Destination "C:\Users\[username]\.local\bin\claude.exe" -ForceThis issue has 3 comments on GitHub. Read the full discussion on GitHub ↗