[BUG] Cowork on Windows 11: VM starts successfully but child process exits code 1 immediately

Resolved 💬 3 comments Opened Apr 16, 2026 by MrPinogris Closed Apr 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Cowork consistently fails with "exit code 1" on Windows 11. The VM launches, mounts succeed, the API is reachable, but the child process crashes immediately after PID start.

What Should Happen?

cowork should work

Error Messages/Logs

Relevant log output (from C:\ProgramData\Claude\Logs\coworkd\user-*.log):
[process:e497e1f0-61c7-409a-b6ba-ae27c595caaa] started PID 5248
[process:e497e1f0-61c7-409a-b6ba-ae27c595caaa] direct child exited: code=1 signal=<nil>

From cowork-service.log:
[RPC] API reachability: REACHABLE
[RPC] Process e497e1f0-61c7-409a-b6ba-ae27c595caaa exited: code=1 signal=<nil>

Steps to Reproduce

Fresh install of Claude Desktop from claude.ai/download
Open Cowork tab
Start any task
Process exits with code 1

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Desktop: v1.3036.0.0 (MSIX)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗