[BUG] Cowork "Virtualization is not available" on Windows 11 Pro 24H2 — all virtualization features enabled
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 shows: "Virtualization is not available — Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding."
Restarting does not resolve it. All virtualization features are fully enabled and verified working.
What Should Happen?
Cowork should detect that all virtualization features are enabled and successfully start the VM workspace without errors.
Error Messages/Logs
"A virtualização não está disponível. O workspace do Claude requer Virtual Machine Platform, mas o serviço de virtualização não está respondendo."
(English: "Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding.")
Steps to Reproduce
- Install Claude Desktop (latest version) on Windows 11 Pro
- Enable all virtualization features (Hyper-V, VirtualMachinePlatform, HypervisorPlatform)
- Restart computer
- Open Claude Desktop
- Navigate to Cowork tab
- Observe "Virtualization is not available" error immediately
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.1.9493 (b58a0b) - Claude Desktop for Windows
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
This is a Claude Desktop / Cowork issue, not Claude Code.
Tested on two machines:
- Windows 10 Pro 22H2
- Windows 11 Pro
Both have all Hyper-V features enabled and verified via PowerShell. The error persists on both machines after restart. This appears to be a platform detection bug in Claude Desktop, not a system configuration issue. Related issues: #27316, #27420, #29887, #32004, #32233.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗