[BUG] Cowork - VM service not running, error 1058, cannot start CoworkVMService on Windows 10 Pro

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 fails to start with "Failed to start Claude's workspace — VM service not running. The service failed to start." CoworkVMService shows error 1058 (disabled / no associated devices). Tried: reinstalling workspace, rebooting, manually enabling Hyper-V and VirtualMachinePlatform via DISM, setting bcdedit hypervisorlaunchtype to auto, modifying registry start value to 3. Nothing works.

What Should Happen?

Cowork should start successfully and the CoworkVMService should run without errors.

Error Messages/Logs

sc query CoworkVMService → STATE: 1 STOPPED, WIN32_EXIT_CODE: 1077 (0x435)
net start CoworkVMService → System error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
sc qc CoworkVMService → DEPENDENCIES: staterepository (staterepository is RUNNING)
bcdedit /set hypervisorlaunchtype auto → completed successfully
Microsoft-Hyper-V → Estado: Habilitado
HypervisorPlatform → Estado: Habilitado

Steps to Reproduce

1. Install Claude Desktop on Windows 10 Pro (22H2, build 19045.6466)
2. Open Cowork tab
3. Observe error: "VM service not running. The service failed to start."
4. Error persists after reboot, reinstall, and manually enabling all Hyper-V components

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.3883.0.0

Claude Code Version

1.3883.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Windows 10 Pro 22H2 (build 19045.6466). Hyper-V fully enabled. staterepository dependency is running. CoworkVMService is WIN32_PACKAGED_PROCESS type — sc config access is denied (Error 5). Registry workaround (Start=3) applied but error 1058 persists.