[BUG] VM Service not running. The Service failed to start. First download of the Desktop App. It has never worked

[beckerchiro]

Preflight Checklist

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

What's Wrong?

I have Claude Pro on Windows 10 HP desktop. Cowork fails with 'VM service not running, service failed to start.' I have enabled: Intel Virtualization Technology in BIOS, Virtual Machine Platform via PowerShell, Windows Hypervisor Platform, and manually started the Claude service. Reinstalling the workspace does not fix it.

What Should Happen?

Claude Pro should open and perform

Error Messages/Logs

VM service not running. The service failed to start.
Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace.

Steps to Reproduce

I never get past opening the App.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

Never worked

Claude Code Version

N/A

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Windows: Cowork fails to start - “VM service not running” (app hang / stuck) #48001
2. [BUG] Failed to start Claude's workspace VM service not running. The service failed to start. #31703
3. Cowork workspace broken since update - VM service not running #48381

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #48001.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.