Bug Report :: When Update keeps giving me please wait and try again later
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 13 comments · opened Aug 20, 2025
Bug Description
Environment Info
- Platform: darwin
- Terminal: WarpTerminal
- Version: 1.0.84
- Feedback ID: 9e9d788d-78eb-46f1-b56e-7a4627c7a71e
Errors
[{"error":"Error: Failed to install Claude CLI package: npm error code ENOTEMPTY\nnpm error syscall rename\nnpm error path /Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code\nnpm error dest /Users/yabasha/.claude/local/node_modules/@anthropic-ai/.claude-code-vbCcGUUB\nnpm error errno -66\nnpm error ENOTEMPTY: directory not empty, rename '/Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code' -> '/Users/yabasha/.claude/local/node_modules/@anthropic-ai/.claude-code-vbCcGUUB'\nnpm error A complete log of this run can be found in: /Users/yabasha/.npm/_logs/2025-08-20T17_44_38_530Z-debug-0.log\n at Qd (file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:1604:575)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:3374:10867","timestamp":"2025-08-20T17:44:39.051Z"},{"error":"Error: Failed to install Claude CLI package: npm error code ENOTEMPTY\nnpm error syscall rename\nnpm error path /Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code\nnpm error dest /Users/yabasha/.claude/local/node_modules/@anthropic-ai/.claude-code-vbCcGUUB\nnpm error errno -66\nnpm error ENOTEMPTY: directory not empty, rename '/Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code' -> '/Users/yabasha/.claude/local/node_modules/@anthropic-ai/.claude-code-vbCcGUUB'\nnpm error A complete log of this run can be found in: /Users/yabasha/.npm/_logs/2025-08-20T17_44_49_411Z-debug-0.log\n at Qd (file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:1604:575)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:3374:10867","timestamp":"2025-08-20T17:44:49.533Z"},{"error":"Error: 400 {\"type\":\"error\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"messages.0: all messages must have non-empty content except for the optional final assistant message\"},\"request_id\":\"req_011CSKNu4BxdpHDSbaPH48u5\"}\n at D6.generate (file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:942:2414)\n at aP.makeStatusError (file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:959:2101)\n at aP.makeRequest (file:///Users/yabasha/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:959:5315)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-08-20T17:45:17.240Z"}]
claude update
Current version: 1.0.84
Checking for updates...
New version available: 1.0.85 (current: 1.0.84)
Installing update...
Using local installation update method...
Error: Another instance is currently performing an update
Please wait and try again later
13 Comments
@claude still can't update ClaudeCode:
I had this problem and the solution for me was: in ~/.claude/local/node_modules/@anthropic-ai there were two folders, one
claude-codeand one with an appended randomly generated string. Removing that folder seems to have fixed the problem. Probably I was having issues once and did the renaming manually, or somewhere in some other update process something went wrong, but removing that, which is anyways old backup, fixed it and now it's back updating automagically 💯Hope this helps!
I'm experiencing this same issue on Linux with a slightly different manifestation:
Error message:
Root cause:
A stale lock directory at
~/.local/state/claude/locks/2.0.55.lockthat wasn't cleaned up from a previous update attempt. The directory was empty and there was no actual update process running.Platform:
Workaround:
This suggests the lock cleanup issue affects multiple locations:
~/.claude/local/node_modules/@anthropic-ai(original issue)~/.claude/.update.lock(mentioned in #559)~/.local/state/claude/locks/<version>.lock(this case)It appears Claude Code's update process has a systematic problem with cleaning up locks when updates fail or are interrupted.
Ran into this today on MacOS 26.2 RC, Claude Code 2.0.64
Another process is currently updating Claude. Please try again in a moment.Fix:
ls -la ~/.local/state/claude/locks/2.0.64.lockrm -rf ~/.local/state/claude/locks/2.0.64.lockclaude updateClaude update runs ok.
claude updateUpdate fails again.
not able to update on MacOS.
Same here. Stuck on 2.0.64.
Same here, stuck on 2.0.62. Removed the lock files and it worked. Thanks
Looks like Version 2.0.67 has a fix for this possibly, I'm not totally sure it's the same issue though. As mine was already on the latest when displaying the issue.
• Fixed false "Another process is currently updating Claude" error when running
claude updatewhile another instance is already on the latest versionAnd this fix might help others:
• Fixed
claude install --forcenot bypassing stale lock filesI'm using the native Windows Claude Code installation. For me, the locations to delete to fix the "Another instance is currently performing an update" problem are the following:
%USERPROFILE%\.local\share\claude\versions, delete the most recent version file that is 0 bytes long, e.g. file2.0.67%USERPROFILE%\.local\state\claude\locks\, delete the folder for the most recent version, e.g. folder2.0.67.lock(the folder was empty in my case)then run
claude updateThe update then succeeded.
Having the same issue, I'm getting a bash error it seems, already tried deleting the lock files from local
<img width="1188" height="870" alt="Image" src="https://github.com/user-attachments/assets/f3956123-58a7-4419-96f1-b9d8ee6d68e3" />
@000geid is there anything else showing in the claude folder? ie: ls -la ~/.local/state/claude
Maybe do a reboot after doing the RM commands?
The install error your seeing looks different than the ones from the lock issue, to me.
On MacOS, had the same issue and was able to resolve it through running
claude install --force. After that I ranclaude updatewhere it warned me that claude was installed in multiple locations.When trying to uninstall the npm claude instance, it didnt work so I had to manually delete the folder
~/.nvm/versions/node/v20.5.1/lib/node_modules/@anthropic-ai.Now everything works. Hope this helps someone.
in my case the lock was in
~/.claude/.update.lock(WSL2 setup)