CoworkVMService fails to start on Windows — workspace permanently broken until manual intervention

Bug Description

On Windows 11, the Claude Desktop workspace fails to initialize with:

"VM service not running. The service failed to start."

CoworkVMService stops when Claude Desktop is closed and does NOT reliably restart when the app is reopened. This leaves the workspace permanently broken until Start-Service CoworkVMService is run manually from an elevated shell. Restarting the app or rebooting does not fix it.

Steps to Reproduce

1. Open Claude Desktop on Windows 11
2. Use workspace features normally
3. Close Claude Desktop
4. Reopen Claude Desktop
5. Workspace fails with "VM service not running"

Root Causes

1. No auto-recovery: CoworkVMService cannot set its own FailureActions (Access Denied), and the installer does not configure them. When the service crashes, it stays dead.
2. Race condition: Claude Desktop expects the VM to be ready instantly, but VM boot takes about 25s. App times out before service is ready.
3. App hang on close: claude.exe triggers MoAppHang when closing, Windows kills it, leaving the service in a bad state.

Log Evidence

Service log (successful manual start):

[VM] VM started successfully
[RPC] sdk-daemon is ready
[VM] API reachability: REACHABLE

Service startup warning:

Warning: failed to open service for recovery config: Access is denied.

Windows Event Log:

Event 7034: The Claude service terminated unexpectedly. It has done this 2 time(s).
MoAppHang: Claude_1.569.0.0 -- claude.exe stopped interacting with Windows and was closed.

Workaround

Run from an elevated PowerShell:

Start-Service CoworkVMService

Wait about 25 seconds, then open Claude Desktop.

Environment

• Windows 11 Home 10.0.26200
• AMD Ryzen 7 8700G, 32 GB RAM
• Claude Desktop v1.569.0.0 (MSIX)
• Hyper-V active, WSL2 active