[Bug] Claude Code desktop application crashes with unresponsive processes after startup
Status Fixed / completed
Reported on v2.1.37
Maintainer reply ✓ Yes — amorriscode
Workaround ✓ Mentioned in thread ↓
Activity 15 comments · opened Feb 18, 2026 · closed Feb 25, 2026
💡 Likely answer: A maintainer (amorriscode, contributor)
responded on this thread — see the highlighted reply below.
Bug Description
1YCZHOG claude code on desktop opens and then shows this error code after a few seconds. once the error shows I can only kill the claude.exe(s) (8 of them) and then restart. been going on since evening of 17/02/2026
Environment Info
- Platform: win32
- Terminal: null
- Version: 2.1.37
- Feedback ID: 4806c090-f876-4565-bd16-465f5beb9399
Errors
[{"error":"AbortError: The operation was aborted.\n at unknown\n at abortChildProcess (node:child_process:947:42)\n at onAbortListener2 (node:child_process:35:24)\n at abort (unknown)\n at <anonymous> (B:/~BUN/root/claude.exe:3458:209)","timestamp":"2026-02-18T16:30:11.276Z"}]
tried all standard troubleshooting and reinstall, still the same issue.
15 Comments
I had the same 1YCZHOG crash and found the root cause + workaround.
Root cause: A Code session's metadata JSON still has
"isArchived": false(left in "active/running" state after an unexpected exit). When you click the session, the app tries to reconnect to the dead CLI process → React fatal error (#185) → crash screen.Fix:
%APPDATA%\Claude\claude-code-sessions\%LOCALAPPDATA%\Packages\Claude_{id}\LocalCache\Roaming\Claude\claude-code-sessions\{org_id}\{user_id}\local_*.jsonfile and look for the session that has"isArchived":false"isArchived":trueThe session will open normally with full conversation history after this change.
Additional technical details from investigation:
Crash sequence (from
main.logandclaude.ai-web.log):What was ruled out (to save your debugging time):
.gitnulreserved filename in worktree — present in other non-crashing sessionsTwo additional related issues found:
claude-code-sessions/{org}/{user}/local_*.jsonbecomes 0 bytes (e.g., after a crash), the session silently disappears. Log shows:Failed to load session from local_xxx.json: Unexpected end of JSON input. Also, files with UTF-8 BOM (0xEF 0xBB 0xBF) are rejected — the app requires BOM-free UTF-8.CLAUDE_CONFIG_DIRfor JSONL lookup: WhenCLAUDE_CONFIG_DIRis set to relocate.claude(e.g., toD:\.claude), the CLI writes JONLs to the new location, but the desktop app still looks inC:\Users\{user}\.claude\projects\. Workaround:mklink /D C:\Users\{user}\.claude\projects D:\.claude\projectsSuggested fix: When a session has
isArchived: falsebut the CLI process is not running, the app should gracefully fall back to read-only mode instead of crashing the React renderer.Just some feedback, I've tried the suggested workaround putting all sessions to true, unfortunately no success. Also tried removing the .git folder as mentioned in the linked issues and that did not work either. If there is any more info I can provide, do let me know. But as I'm not very technical, please be as precise as you can with the questions. Many thanks!
I'm experiencing the same 1YCZHOG crash on Windows. The app opens and crashes after a few seconds every time.
I've tried the following without success:
Nothing works — the 1YCZHOG error persists after every attempt. This has been going on since around February 17th.
Is this a server-side issue? status.claude.com showed high error rates around that date. If so, is there an ETA for a fix?
Key errors from logs:
From
claude.ai-web.log:From
main.log:The CSP violation blocking
a-api.anthropic.comseems significant — the app is blocking its own API connection. Is this a known issue with the MSIX/Microsoft Store build?Additional data: 6 reproducible crashes on v1.1.3541 (Windows VM, agent mode)
I'm hitting the same 1YCZHOG crash, but with a 100% reproducible trigger across 6 independent sessions. Every single crash follows the exact same sequence in the logs.
Environment
Exact crash sequence (identical all 6 times)
From
main.log:From
claude.ai-web.log(same timestamp assetFocusedSession: null):The crash happens 3-4 seconds after tool permission is granted, every time. The
getGitDiffcall on the worktree completes, then the React renderer crashes trying to display the result.What I tried (none fixed it)
claude-code-sessionsdirectory — eliminatedCannot save session: storage path not availablewarnings but crash persistsghCLI — eliminatesspawn gh ENOENTbut crash persistsKey observations
SyntaxHighlightedDiff: Token without row: [object Object]warnings appear inclaude.ai-web.logjust before every crash — the diff renderer may be producing invalid React children.checkGhAvailablecall silently fails (gh not on PATH) right before each crash, though installing gh didn't fix it.cowork_vm_node.logshowsVM not supported (win32/x64), skippingon every launch.Timestamps of all 6 crashes (same day)
| Session | Crash time | Tool | Worktree diff size |
|---------|-----------|------|-------------------|
| 1 (eloquent-tereshkova) | 10:15:53 | Edit | 44KB |
| 2 (stoic-brahmagupta) | 12:57:45 | Edit | 27KB |
| 3 (funny-lovelace) | 17:06:36 | Edit | 21KB |
| 4 (mystifying-booth) | 17:16:53 | Edit | 22KB |
| 5 (hungry-sanderson) | 17:55:27 | Bash | ~22KB |
All show identical log sequence. The
SyntaxHighlightedDiffwarnings + React #185 suggest the diff rendering component is producing invalid React children that trigger an infinite re-render loop.I've been getting this relentlessly for the last 2 days on Claude Code Desktop on Windows, using git repos with worktrees.
The only work around that's worked for me so far is changing my session filter on the sidebar to archived only and then using the session search function to open the session (which is not archived) and continue working that way.
As long as the sidebar isn't showing active sessions, my sessions are stable.
Edit: never mind, not stable but at least somewhat more useable
It;'s claude's forced update. Roll back to an earlier version and chnage config json to set autoupdates to false.
Today's 2/19/2026 uupdate regressed HARD.
Turns out that letting AI approve PRs is a steaming pile of poo.
Environment:
Issue:
Error code 1YCZHOG appears within seconds of launching Claude Code inside the Desktop App. This has been happening since February 19, 2026.
Troubleshooting steps taken – none resolved the issue:
claude-code-vmfolder to prevent VM startupvm_bundlesfolderautoUpdate: falseinclaude_desktop_config.jsonFindings from logs (
unknown-window.log):The root cause appears to be a recurring
Uncaught Error: Minified React error #418followed immediately by[BOOTSTRAP] Fatal error boundary triggered. This loop repeats on every startup regardless of app version or local configuration.Conclusion:
Since the error persists across two different app versions and survives a full cache wipe, this appears to be triggered server-side (resources loaded from claude.ai on startup), not a local configuration issue. A local fix does not seem possible until the server-side regression is resolved.
yes, server side, but prior version works. Using now back to January 10th. Anthropic doesn't publish old version, but you can download non-official (caveats apply) https://claude.en.uptodown.com/windows
The issue seems to be that while the system works somewhat in other projects, the projects that have open sessions crash every time. This problem has persisted for two days now without any resolution. Despite attempts to find a fix, there has been no solution yet, and the sessions remain unusable whenever they are open.
Summary:
Other projects: Works a little bit.
Projects with open sessions: Crashes every time.
Status: 2 days of downtime.
Solution: None found yet.
this helped to me:
Navigate to %APPDATA%\Claude\claude-code-sessions\
For Microsoft Store/UWP installs: %LOCALAPPDATA%\Packages\Claude_{id}\LocalCache\Roaming\Claude\claude-code-sessions\
Find the subfolder {org_id}\{user_id}\
Open each local_*.json file and look for the session that has "isArchived":false
Change it to "isArchived":true
x64
https://downloads.claude.ai/releases/win32/x64/1.1.2321/Claude-495628f91fbfa276fabd6da835ba226fdf5ec68e.exe
arm64
https://downloads.claude.ai/releases/win32/arm64/1.1.2321/Claude-495628f91fbfa276fabd6da835ba226fdf5ec68e.exe
Also in between 2-3, optionally you can delete cache data.
https://claude.ai/api/desktop/win32/x64/exe/latest/redirect?utm_source=claude_code&utm_medium=docs <-- this one works
The
1YCZHOGerror should be resolved if you update and restart the app. Looking into the related issues in the issue, thanks for reporting.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.