claude-code - 💡(How to fix) Fix [BUG] [BUG] claude --resume crashes with "FKH is not a function" on 2.1.120 (Windows, native installer) [7 comments, 4 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#53093Fetched 2026-04-25 06:12:32
View on GitHub
Comments
7
Participants
4
Timeline
13
Reactions
2
Author
Timeline (top)
commented ×7labeled ×5cross-referenced ×1

Error Message

ERROR FKH is not a function. (In 'FKH(K)', 'FKH' is undefined)

Error Messages/Logs

Fix Action

Fix / Workaround

Workarounds that DO work (suggesting the bug is in the resume init path, not session data):

  • claude --continue works
  • claude then /resume from inside the session works
  • Only claude --resume <name> and claude --resume (with picker) crash
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?

On Windows, running claude --resume <session-name> crashes immediately with:

ERROR FKH is not a function. (In 'FKH(K)', 'FKH' is undefined) B:/~BUN/root/src/entrypoints/cli.js:9273:5663

The crash fires before the session UI loads. It happens for every session that has prior messages — the session name and project don't matter.

Two related issues:

  1. The crashing version is 2.1.120, which is being delivered by the in-binary auto-updater. It is NOT available on either public channel:

    • npm latest tag = 2.1.118
    • GitHub Releases latest = 2.1.119 So the auto-updater is shipping a build that isn't published anywhere users can install from directly.
  2. The auto-updater ignores every documented disable mechanism. I have set ALL of the following and it still re-pulls 2.1.120 between launches:

    • Windows User env var DISABLE_AUTOUPDATER=1
    • Windows User env var DISABLE_UPDATES=1
    • "env": { "DISABLE_AUTOUPDATER": "1", "DISABLE_UPDATES": "1" } in ~/.claude/settings.json
    • "autoUpdates": false in ~/.claude/settings.json Reproducible: install 2.1.118 via npm i -g @anthropic-ai/[email protected], confirm claude --version says 2.1.118, run a session, exit, run claude --version again — it now says 2.1.120.

Workarounds that DO work (suggesting the bug is in the resume init path, not session data):

  • claude --continue works
  • claude then /resume from inside the session works
  • Only claude --resume <name> and claude --resume (with picker) crash

Related prior issues for the auto-updater bypass: #14985, #11263, #10764, #5753.

What Should Happen?

The session should resume normally, restoring the conversation history. claude --resume <name> should behave identically to launching claude and using /resume from inside (which works fine on the same version).

Error Messages/Logs

Steps to Reproduce

  1. Be on Windows with claude installed via npm
  2. claude --version → 2.1.120 (forced by auto-updater)
  3. cd into any project that has a prior named session
  4. claude --resume "<session-name>"
  5. Crash: "FKH is not a function"

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.120 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The issue can likely be worked around by using claude --continue or launching claude and then using /resume from inside the session, as these methods do not crash.

Guidance

  • The crash seems to be related to the --resume flag, specifically when used with a session name, suggesting the issue lies in the resume initialization path.
  • The auto-updater ignoring documented disable mechanisms and shipping an unpublished version (2.1.120) may be a contributing factor, but the immediate workaround involves avoiding the --resume flag.
  • To verify if the issue is indeed with the --resume flag, try using claude --continue or launching claude and then using /resume from inside, as these methods are reported to work.
  • Consider installing a previous version of Claude Code (e.g., 2.1.118 via npm i -g @anthropic-ai/[email protected]) to see if the issue persists, although the auto-updater may still force an update to 2.1.120.

Example

No specific code snippet is applicable here, as the issue seems to be related to the command-line flags and versioning rather than a code snippet that can be modified.

Notes

The auto-updater's behavior and the fact that version 2.1.120 is not available on public channels (npm or GitHub Releases) suggest there might be an issue with the update mechanism. However, the immediate focus is on finding a workaround for the crash when using --resume.

Recommendation

Apply workaround: Use claude --continue or launch claude and then use /resume from inside the session to avoid the crash, as these methods are reported to work without issues.

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…

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] [BUG] claude --resume crashes with "FKH is not a function" on 2.1.120 (Windows, native installer) [7 comments, 4 participants]