Desktop app crash (STATUS_BREAKPOINT) when opening embedded Claude Browser preview (Cowork VM Sandbox)
Status Closed — duplicate
Maintainer reply None cached
Activity 1 comment · opened Aug 11, 2026 · closed Aug 25, 2026
Environment
- Claude desktop client build: 1.26832.0.0
- OS: Windows 11 Pro (10.0.26200)
- Hyper-V: enabled and functioning (vmcompute.dll loads successfully, confirmed via cowork-service.log)
Summary
The desktop app crashes deterministically (Claude.exe, ExceptionCode=0x80000003 / STATUS_BREAKPOINT, offset 0x6dd36f9 in the main image) within ~2 seconds of calling the embedded browser 2Claude Browser" MCP tool / preview_start, which runs inside the Cowork Full VM Sandbox) - even though the tool call itself reports success (navOk: true, "Browser pane opened").
Steps to reproduce
- On Windows 11 with Hyper-V enabled and working, open a task in Claude de.
- Call the embedded "Claude Browser" preview tool on any URL (
preview_start). - The tool call succeeds and returns
navOk: truewith a browser pane opened. - ~2 seconds later the app process crashes.
cowork-service.logshowsPersistent RPC: connection ended: failed to read length: EOFat the same timestamp as the crash dump.
What we ruled out
- Missing Hyper-V (
vmcompute.dllnot found): enabled Hyper-V, confirmedvmcompute.dll loaded successfullyin cowork-service.log and a workingvEthernet (Default Switch)adapter. Crash still occurs, same exception code and offset.
-tration: fully uninstalled and reinstalled the app. Crash still occurs, same exception code and offset.
- Both crashes (days apart, before/after the Hyper-V fix and the reinstall) landed at the exact same code location, and both times the immediately preceding action in the session log was a call to the embe
Crash details
- ExceptionCode: 0x80000003 (STATUS_BREAKPOINT - looks like a deliberate CHECK()/assert failure, not memory corruption)
- Faulting module: Claude.exe
- Offs Reproduced identically across two separate crash dumps.
Happy to share the .dmp files or additional logs if useful.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗