[BUG] Cowork "Virtualization is not available" on Windows 10 Pro despite Hyper-V fully enabled

[jesseladrian]

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?

Environment

• Claude Desktop: latest version (claude.ai/download)
• OS: Windows 10 Pro
• Subscription: Pro

Virtualization status (all verified as Administrator)

Check	Result
Microsoft-Hyper-V	✅ Enabled
VirtualMachinePlatform	✅ Enabled
HypervisorPlatform	✅ Enabled
CoworkVMService	✅ Running
bcdedit hypervisorlaunchtype	✅ Auto

What's wrong?
Cowork tab shows: "Virtualization is not available — Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding. Restart your computer to resolve this."

Restarting does not resolve it.

Steps taken (none resolved the issue)

1. Restarted computer multiple times
2. Deleted %APPDATA%\Claude\vm_bundles and relaunched Claude
3. Full clean reinstall: uninstalled Claude, deleted all Claude folders in APPDATA and LOCALAPPDATA, rebooted, reinstalled fresh
4. Ran bcdedit /set hypervisorlaunchtype auto as Administrator and rebooted

Expected behavior
Cowork should detect that all virtualization features are enabled and successfully start the VM workspace.

Actual behavior
Cowork permanently shows the virtualization error. The VM never attempts to initialize.

This appears to be the same issue as #27316, #27420, #29887, #32004, #32574.

What Should Happen?

Expected behavior
Cowork should detect that all virtualization features are enabled and successfully start the VM workspace.

Error Messages/Logs

El espacio de trabajo de Claude requiere Virtual Machine Platform, pero el servicio de virtualización no responde. Reinicia tu computadora para resolver esto.

Steps to Reproduce

Environment

• Claude Desktop: latest version (claude.ai/download)
• OS: Windows 10 Pro
• Subscription: Pro

Virtualization status (all verified as Administrator)

Check	Result
Microsoft-Hyper-V	✅ Enabled
VirtualMachinePlatform	✅ Enabled
HypervisorPlatform	✅ Enabled
CoworkVMService	✅ Running
bcdedit hypervisorlaunchtype	✅ Auto

What's wrong?
Cowork tab shows: "Virtualization is not available — Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding. Restart your computer to resolve this."

Restarting does not resolve it.

Steps taken (none resolved the issue)

1. Restarted computer multiple times
2. Deleted %APPDATA%\Claude\vm_bundles and relaunched Claude
3. Full clean reinstall: uninstalled Claude, deleted all Claude folders in APPDATA and LOCALAPPDATA, rebooted, reinstalled fresh
4. Ran bcdedit /set hypervisorlaunchtype auto as Administrator and rebooted

Expected behavior
Cowork should detect that all virtualization features are enabled and successfully start the VM workspace.

Actual behavior
Cowork permanently shows the virtualization error. The VM never attempts to initialize.

This appears to be the same issue as #27316, #27420, #29887, #32004, #32574.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Cowork shows "Virtualization is not available" on Windows 10 Pro despite Hyper-V fully enabled #36402
2. [BUG] Cowork "Virtualization is not available" on Windows 10 Pro — logs and vm_bundles folder never created #33339
3. [BUG] Cowork shows "Virtualization is not available" on Windows 11 Pro despite Hyper-V fully enabled and services running** #32574

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

[jesseladrian]

Not the same but similar

[ValueAddSolutions]

Same issue but for Windows 11 pro, version 22H2

[Plat0n82]

I have the same issue with Win 11 Pro 24H2