Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] claude update reports success but never installs new version (Windows, ESAI NuGet distribution) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46301•Fetched 2026-04-11 06:23:55
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
NickEricsonNickEricson
Participants
github-actions[bot]github-actions[bot]NickEricsonNickEricson
Timeline (top)
labeled ×4commented ×1

claude update reports "Successfully updated from 2.1.92 to version 2.1.100" but no new version is created. The CurrentVersion symlink remains pointed at the old version. Repeatable across sessions — new shells still show 2.1.92.

Environment

  • OS: Windows 11 Pro for Workstations 10.0.26200.7985
  • Install method: Microsoft ESAI NuGet feed (Anthropic.Claude.CLI.win-x64 package)
  • Install location: C:\Users\<user>\.claude-cli\
  • Current version: 2.1.92
  • Node: v22.16.0, npm 11.7.0
  • PATH entries: .claude-cli/CurrentVersion (symlink → 2.1.92/)

Repro steps

  1. Open a terminal (no other claude instances running)
  2. Run claude update
  3. Observe output: 
    Current version: 2.1.92
Checking for updates to latest version...
Successfully updated from 2.1.92 to version 2.1.100
  4. Open a new terminal (new shell process)
  5. Run claude --version → still shows 2.1.92
  6. Run claude update again → same "Successfully updated" message, still 2.1.92

Observed state

C:\Users\<user>\.claude-cli\
├── 2.1.86/
├── 2.1.90/
├── 2.1.92/
│   ├── claude.exe          (240 MB, dated 2026-04-06)
│   ├── Anthropic.Claude.CLI.win-x64.nuspec  (version: 2.1.92)
│   ├── [Content_Types].xml
│   ├── _rels/
│   └── package/
└── CurrentVersion -> C:\Users\<user>\.claude-cli\2.1.92\

No 2.1.100 folder is ever created. The update claims success but produces no artifacts.

Expected behavior

After claude update:

  1. A 2.1.100/ folder should be created with the new claude.exe
  2. The CurrentVersion symlink should be updated to point to 2.1.100/
  3. New shell sessions should resolve claude --version as 2.1.100

Additional context

  • The .nuspec shows this is the ESAI feed distribution (owners: Microsoft ESAI), not npm or direct download
  • where claude returns nothing (not on PATH as a standard exe — resolved via the CurrentVersion symlink in PATH)
  • npm list -g @anthropic-ai/claude-code shows empty — not installed via npm
  • npx @anthropic-ai/claude-code@latest runs ephemerally but does not update the .claude-cli installation
  • No logs found in ~/.claude/logs/ or ~/.claude/*.log
  • Previous updates (2.1.86 → 2.1.90 → 2.1.92) worked correctly based on folder timestamps

Hypothesis

The claude update command may be designed for the npm install path and doesn't know how to update the NuGet/ESAI distribution. It detects a newer version exists, prints success, but never downloads/extracts the binary or updates the symlink.

Error Message

Error Messages/Logs

No Error

Root Cause

claude update reports "Successfully updated from 2.1.92 to version 2.1.100" but no new version is created. The CurrentVersion symlink remains pointed at the old version. Repeatable across sessions — new shells still show 2.1.92.

Environment

  • OS: Windows 11 Pro for Workstations 10.0.26200.7985
  • Install method: Microsoft ESAI NuGet feed (Anthropic.Claude.CLI.win-x64 package)
  • Install location: C:\Users\<user>\.claude-cli\
  • Current version: 2.1.92
  • Node: v22.16.0, npm 11.7.0
  • PATH entries: .claude-cli/CurrentVersion (symlink → 2.1.92/)

Repro steps

  1. Open a terminal (no other claude instances running)
  2. Run claude update
  3. Observe output: 
    Current version: 2.1.92
Checking for updates to latest version...
Successfully updated from 2.1.92 to version 2.1.100
  4. Open a new terminal (new shell process)
  5. Run claude --version → still shows 2.1.92
  6. Run claude update again → same "Successfully updated" message, still 2.1.92

Observed state

C:\Users\<user>\.claude-cli\
├── 2.1.86/
├── 2.1.90/
├── 2.1.92/
│   ├── claude.exe          (240 MB, dated 2026-04-06)
│   ├── Anthropic.Claude.CLI.win-x64.nuspec  (version: 2.1.92)
│   ├── [Content_Types].xml
│   ├── _rels/
│   └── package/
└── CurrentVersion -> C:\Users\<user>\.claude-cli\2.1.92\

No 2.1.100 folder is ever created. The update claims success but produces no artifacts.

Expected behavior

After claude update:

  1. A 2.1.100/ folder should be created with the new claude.exe
  2. The CurrentVersion symlink should be updated to point to 2.1.100/
  3. New shell sessions should resolve claude --version as 2.1.100

Additional context

  • The .nuspec shows this is the ESAI feed distribution (owners: Microsoft ESAI), not npm or direct download
  • where claude returns nothing (not on PATH as a standard exe — resolved via the CurrentVersion symlink in PATH)
  • npm list -g @anthropic-ai/claude-code shows empty — not installed via npm
  • npx @anthropic-ai/claude-code@latest runs ephemerally but does not update the .claude-cli installation
  • No logs found in ~/.claude/logs/ or ~/.claude/*.log
  • Previous updates (2.1.86 → 2.1.90 → 2.1.92) worked correctly based on folder timestamps

Hypothesis

The claude update command may be designed for the npm install path and doesn't know how to update the NuGet/ESAI distribution. It detects a newer version exists, prints success, but never downloads/extracts the binary or updates the symlink.

Code Example

Current version: 2.1.92
     Checking for updates to latest version...
     Successfully updated from 2.1.92 to version 2.1.100

---

C:\Users\<user>\.claude-cli\
  ├── 2.1.86/
  ├── 2.1.90/
  ├── 2.1.92/
  │   ├── claude.exe          (240 MB, dated 2026-04-06)
  │   ├── Anthropic.Claude.CLI.win-x64.nuspec  (version: 2.1.92)
  │   ├── [Content_Types].xml
  │   ├── _rels/
  │   └── package/
  └── CurrentVersion -> C:\Users\<user>\.claude-cli\2.1.92\

---

No Error
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Summary

claude update reports "Successfully updated from 2.1.92 to version 2.1.100" but no new version is created. The CurrentVersion symlink remains pointed at the old version. Repeatable across sessions — new shells still show 2.1.92.

Environment

  • OS: Windows 11 Pro for Workstations 10.0.26200.7985
  • Install method: Microsoft ESAI NuGet feed (Anthropic.Claude.CLI.win-x64 package)
  • Install location: C:\Users\<user>\.claude-cli\
  • Current version: 2.1.92
  • Node: v22.16.0, npm 11.7.0
  • PATH entries: .claude-cli/CurrentVersion (symlink → 2.1.92/)

Repro steps

  1. Open a terminal (no other claude instances running)
  2. Run claude update
  3. Observe output: 
    Current version: 2.1.92
Checking for updates to latest version...
Successfully updated from 2.1.92 to version 2.1.100
  4. Open a new terminal (new shell process)
  5. Run claude --version → still shows 2.1.92
  6. Run claude update again → same "Successfully updated" message, still 2.1.92

Observed state

C:\Users\<user>\.claude-cli\
├── 2.1.86/
├── 2.1.90/
├── 2.1.92/
│   ├── claude.exe          (240 MB, dated 2026-04-06)
│   ├── Anthropic.Claude.CLI.win-x64.nuspec  (version: 2.1.92)
│   ├── [Content_Types].xml
│   ├── _rels/
│   └── package/
└── CurrentVersion -> C:\Users\<user>\.claude-cli\2.1.92\

No 2.1.100 folder is ever created. The update claims success but produces no artifacts.

Expected behavior

After claude update:

  1. A 2.1.100/ folder should be created with the new claude.exe
  2. The CurrentVersion symlink should be updated to point to 2.1.100/
  3. New shell sessions should resolve claude --version as 2.1.100

Additional context

  • The .nuspec shows this is the ESAI feed distribution (owners: Microsoft ESAI), not npm or direct download
  • where claude returns nothing (not on PATH as a standard exe — resolved via the CurrentVersion symlink in PATH)
  • npm list -g @anthropic-ai/claude-code shows empty — not installed via npm
  • npx @anthropic-ai/claude-code@latest runs ephemerally but does not update the .claude-cli installation
  • No logs found in ~/.claude/logs/ or ~/.claude/*.log
  • Previous updates (2.1.86 → 2.1.90 → 2.1.92) worked correctly based on folder timestamps

Hypothesis

The claude update command may be designed for the npm install path and doesn't know how to update the NuGet/ESAI distribution. It detects a newer version exists, prints success, but never downloads/extracts the binary or updates the symlink.

What Should Happen?

It should update

Error Messages/Logs

No Error

Steps to Reproduce

claude update 2x and see same version both times

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.92

Claude Code Version

2.1.92

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The claude update command may not be compatible with the NuGet/ESAI distribution, causing it to fail to update the CurrentVersion symlink and create a new version folder.

Guidance

  • Verify that the claude update command is designed to work with the NuGet/ESAI distribution by checking the documentation or release notes.
  • Check if there are any specific update instructions for the NuGet/ESAI distribution, such as using a different command or flag.
  • Try running claude update with the --force or --verbose flag to see if it provides more detailed output or error messages.
  • Consider reinstalling the Anthropic.Claude.CLI.win-x64 package from the NuGet feed to ensure that the latest version is installed correctly.

Example

No code snippet is provided as the issue seems to be related to the update mechanism rather than a specific code problem.

Notes

The issue may be specific to the NuGet/ESAI distribution, and the claude update command may work correctly with other installation methods, such as npm.

Recommendation

Apply workaround: Try reinstalling the Anthropic.Claude.CLI.win-x64 package from the NuGet feed to ensure that the latest version is installed correctly, as the claude update command may not be compatible with the NuGet/ESAI distribution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#GPU compatibility#latency issue#model loading

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] claude update reports success but never installs new version (Windows, ESAI NuGet distribution) [1 comments, 2 participants]