claude-code - 💡(How to fix) Fix [BUG] [BUG] Claude Desktop fails to open on Windows 10 — EBUSY on chrome-native-host.exe [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#48038Fetched 2026-04-15 06:35:05
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

The Claude Desktop app fails to open completely — no window appears at all. The issue started on April 9th and persists after updating to version 1.1617.0 on April 10th.


Error Message

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

Root Cause

The EBUSY error appears to be the root cause: something is locking chrome-native-host.exe preventing the app from completing its startup sequence. This persists across versions and reinstalls, suggesting the lock may survive uninstallation or originate outside the app's own processes.

The recurring Acceso denegado in cowork-service.log may also indicate insufficient permissions for the service.


Code Example

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

---

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

---

[sessions-bridge] Poll error: Failed with status 500: Internal server error
[request-id: req_011CZtXgxvqQu8eze3nHzBTk]

---

Uncaught (in promise) Error: Error invoking remote method '..._BuddyBleTransport_$_reportState':
Error: No handler registered for '..._BuddyBleTransport_$_reportState'

---

Warning: failed to open service for recovery config: Acceso denegado.

---

[main.log - 2026-04-09 14:02:59]
[Chrome Extension MCP] Failed to copy native host binary:
Error: EBUSY: resource busy or locked,
copyfile 'C:\Program Files\WindowsApps\Claude_1.1062.0.0_x64__pzs8sxrjxfjjc\app\resources\chrome-native-host.exe'
-> 'C:\Users\jigna\AppData\Roaming\Claude\ChromeNativeHost\chrome-native-host.exe'

[main.log - 2026-04-10 12:16:07] (reproduced with version 1.1617.0)
Same EBUSY error with new version path.

[cowork-service.log - recurring]
Warning: failed to open service for recovery config: Acceso denegado.
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?

Claude Desktop fails to open on Windows 10 — EBUSY on chrome-native-host.exe

Environment

  • OS: Windows 10 Pro 10.0.19045
  • Claude Desktop version: 1.1617.0 (installed via Microsoft Store)
  • Plan: Pro

Description

The Claude Desktop app fails to open completely — no window appears at all. The issue started on April 9th and persists after updating to version 1.1617.0 on April 10th.


Steps already attempted

  1. Killed all Claude and Claude Code processes via PowerShell (64 processes terminated)
  2. Attempted to end tasks via Task Manager — access denied on all Claude processes
  3. Uninstalled and reinstalled via Microsoft Store

None of the above resolved the issue.


Key errors from logs

main.log — April 9, 14:02:59

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

main.log — April 10, 12:16:07 (reproduced with new version 1.1617.0)

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

main.log — April 9, 18:41:20

[sessions-bridge] Poll error: Failed with status 500: Internal server error
[request-id: req_011CZtXgxvqQu8eze3nHzBTk]

claude.ai-web.log — April 10, 12:16:08

Uncaught (in promise) Error: Error invoking remote method '..._BuddyBleTransport_$_reportState':
Error: No handler registered for '..._BuddyBleTransport_$_reportState'

cowork-service.log — Recurring (April 9, 10, 11, 12, 14)

Warning: failed to open service for recovery config: Acceso denegado.

Analysis

The EBUSY error appears to be the root cause: something is locking chrome-native-host.exe preventing the app from completing its startup sequence. This persists across versions and reinstalls, suggesting the lock may survive uninstallation or originate outside the app's own processes.

The recurring Acceso denegado in cowork-service.log may also indicate insufficient permissions for the service.


Expected behavior

App opens normally.

Actual behavior

No window appears. App silently fails to start.

What Should Happen?

Claude Desktop app opens normally and displays the main window.

Error Messages/Logs

[main.log - 2026-04-09 14:02:59]
[Chrome Extension MCP] Failed to copy native host binary:
Error: EBUSY: resource busy or locked,
copyfile 'C:\Program Files\WindowsApps\Claude_1.1062.0.0_x64__pzs8sxrjxfjjc\app\resources\chrome-native-host.exe'
-> 'C:\Users\jigna\AppData\Roaming\Claude\ChromeNativeHost\chrome-native-host.exe'

[main.log - 2026-04-10 12:16:07] (reproduced with version 1.1617.0)
Same EBUSY error with new version path.

[cowork-service.log - recurring]
Warning: failed to open service for recovery config: Acceso denegado.

Steps to Reproduce

  1. Launch Claude Desktop app on Windows 10
  2. No window appears — app silently fails to start
  3. Check logs at %AppData%\Roaming\Claude\logs\main.log
  4. EBUSY error on chrome-native-host.exe is present on every launch attempt

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.1062.0

Claude Code Version

2.1.107 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The EBUSY error on chrome-native-host.exe is likely the root cause, and resolving the file lock issue may allow the Claude Desktop app to open normally.

Guidance

  1. Investigate file locks: Use tools like Process Explorer or Handle to identify which process is locking chrome-native-host.exe and terminate it if necessary.
  2. Check permissions: Verify that the user has sufficient permissions to access and modify the C:\Users\jigna\AppData\Roaming\Claude\ChromeNativeHost directory and its contents.
  3. Clear app data: Try deleting the C:\Users\jigna\AppData\Roaming\Claude directory and its contents to remove any potentially corrupted data.
  4. Reinstall with admin privileges: Reinstall the Claude Desktop app using an administrator account to ensure sufficient permissions.

Example

No code snippet is provided as this issue appears to be related to file system permissions and locking rather than code.

Notes

The Acceso denegado error in cowork-service.log may indicate a separate issue with service permissions, which should be investigated separately.

Recommendation

Apply workaround: Investigate and resolve the file lock issue on chrome-native-host.exe to allow the app to start normally. This approach is recommended as it directly addresses the identified root cause of the issue.

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…

FAQ

Expected behavior

App opens normally.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING