claude-code - 💡(How to fix) Fix [BUG] Cowork - VM service not running, error 1058, cannot start CoworkVMService on Windows 10 Pro [1 comments, 2 participants]

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.

Error Messages/Logs

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. 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 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.

TL;DR

The issue is likely due to a configuration or dependency problem with the CoworkVMService, and a potential workaround involves investigating the service's dependencies and permissions.

Guidance

• Investigate the dependencies of the CoworkVMService, specifically the staterepository service, to ensure it is properly configured and running.
• Check the event logs for any errors related to the CoworkVMService or Hyper-V to gain more insight into the issue.
• Consider checking the permissions and access control lists (ACLs) for the CoworkVMService to ensure it has the necessary permissions to start and run.
• Verify that all Hyper-V components are properly enabled and configured, including the VirtualMachinePlatform and Microsoft-Hyper-V services.

Example

No code snippet is provided as the issue seems to be related to system configuration and service dependencies rather than code.

Notes

The issue seems to be specific to the Windows 10 Pro environment and the CoworkVMService. The fact that the staterepository dependency is running suggests that the issue might be related to the service's configuration or permissions.

Recommendation

Apply workaround: Investigate and adjust the dependencies and permissions of the CoworkVMService, as the issue seems to be related to its configuration rather than a version-specific bug.