claude-code - 💡(How to fix) Fix Claude Desktop on Windows 11 25H2 crashes when switching to Code section (Chat and Cowork work fine) [2 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#53779Fetched 2026-04-28 06:47:29
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1

Error Message

Recurring at every startup (versions 1.3561.0.0, 1.3883.0.0, 1.4758.0.0):

[error] [Chrome Extension MCP] Failed to copy native host binary: Error: EBUSY: resource busy or locked, copyfile 'C:\Program Files\WindowsApps\Claude_<version>_x64__pzs8sxrjxfjjc\app\resources\chrome-native-host.exe' -> 'C:\Users<user>\AppData\Roaming\Claude\ChromeNativeHost\chrome-native-host.exe'

Followed by: [error] Sentry caught: { type: 'Unknown', value: 'No message', stack: undefined }

GPU crash also logged once: GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 34, serviceName: 'GPU' }

The actual Code-section crash produces NO log entry — Desktop dies silently. After crash, Task Manager shows orphaned Claude Code (~410 MB) and cowork-svc.exe still running. main.log attached.

Code Example

Recurring at every startup (versions 1.3561.0.0, 1.3883.0.0, 1.4758.0.0):

[error] [Chrome Extension MCP] Failed to copy native host binary:
Error: EBUSY: resource busy or locked, copyfile
'C:\Program Files\WindowsApps\Claude_<version>_x64__pzs8sxrjxfjjc\app\resources\chrome-native-host.exe'
-> 'C:\Users\<user>\AppData\Roaming\Claude\ChromeNativeHost\chrome-native-host.exe'

Followed by:
[error] Sentry caught: { type: 'Unknown', value: 'No message', stack: undefined }

GPU crash also logged once:
GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 34, serviceName: 'GPU' }

The actual Code-section crash produces NO log entry — Desktop dies silently. After crash, Task Manager shows orphaned `Claude Code` (~410 MB) and `cowork-svc.exe` still running. main.log attached.
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?

Environment

  • OS: Windows 11 Pro, Version 25H2 (OS Build 26200.8246)
  • Claude Desktop version: 1.4758.0.0 (MSIX, Claude_pzs8sxrjxfjjc)
  • Claude Code CLI: 2.1.119
  • Node.js: v24.15.0

What's wrong

Claude Desktop launches normally. Chat works. Cowork works. When I switch to the Code section, the Desktop UI crashes within ~10 seconds. Every time. Reproducible 100%.

main.log

Already tried (none resolved the issue)

  • Full uninstall and reinstall of Claude Desktop
  • Killing all leftover Claude processes in Task Manager and relaunching
  • Multiple application restarts

Post-crash process state

After the Desktop UI crash, Task Manager shows the main Claude process gone, but the following remain running as orphans:

  • Claude Code (~410 MB) — the spawned Code child process
  • cowork-svc.exe (~15 MB)

The Code child process is not terminated when the Desktop UI dies.

Log findings (main.log attached)

Recurring error at every startup, present across versions 1.3561.0.0, 1.3883.0.0, and current 1.4758.0.0:

What Should Happen?

The Code section in Claude Desktop should open and stay running like the Chat and Cowork sections do. Instead, the Desktop UI crashes within ~10 seconds every time I switch to Code.

Error Messages/Logs

Recurring at every startup (versions 1.3561.0.0, 1.3883.0.0, 1.4758.0.0):

[error] [Chrome Extension MCP] Failed to copy native host binary:
Error: EBUSY: resource busy or locked, copyfile
'C:\Program Files\WindowsApps\Claude_<version>_x64__pzs8sxrjxfjjc\app\resources\chrome-native-host.exe'
-> 'C:\Users\<user>\AppData\Roaming\Claude\ChromeNativeHost\chrome-native-host.exe'

Followed by:
[error] Sentry caught: { type: 'Unknown', value: 'No message', stack: undefined }

GPU crash also logged once:
GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 34, serviceName: 'GPU' }

The actual Code-section crash produces NO log entry — Desktop dies silently. After crash, Task Manager shows orphaned `Claude Code` (~410 MB) and `cowork-svc.exe` still running. main.log attached.

Steps to Reproduce

  1. Launch Claude Desktop
  2. Use Chat — works fine
  3. Use Cowork — works fine
  4. Switch to the Code section
  5. Desktop UI crashes within ~10 seconds

Already tried: full uninstall+reinstall, killing leftover processes, multiple restarts. None resolved.

main.log

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.119 (CLI), running inside Claude Desktop 1.4758.0.0 (MSIX)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Claude Desktop integrated Code section (not standalone CLI). Tested separately in PowerShell — CLI works fine.

extent analysis

TL;DR

The most likely fix involves addressing the "EBUSY: resource busy or locked" error when copying the native host binary, which might be causing the Claude Desktop UI to crash when switching to the Code section.

Guidance

  • Investigate the file locking issue: Check if any other processes are holding a lock on the chrome-native-host.exe file, preventing it from being copied.
  • Verify file permissions: Ensure that the user account running Claude Desktop has the necessary permissions to read and write to the C:\Users\<user>\AppData\Roaming\Claude\ChromeNativeHost directory.
  • Review system resource usage: Monitor system resources (CPU, memory, disk usage) when switching to the Code section to identify potential bottlenecks.
  • Consider a temporary workaround: Try manually copying the chrome-native-host.exe file to the destination directory before launching Claude Desktop to see if it resolves the issue.

Example

No code snippet is provided as the issue seems related to file system and process interactions rather than code logic.

Notes

The actual cause of the crash might be more complex and related to the interaction between Claude Desktop, the Code section, and system resources. The provided log files and error messages suggest a starting point for investigation but may not reveal the full picture.

Recommendation

Apply a workaround by manually copying the chrome-native-host.exe file to the destination directory before launching Claude Desktop, as this directly addresses the reported "EBUSY" error and may prevent the crash.

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