[BUG] Cowork "Virtualization not available" on Windows 11 Pro — Hyper-V fully functional but HRESULT 0x80370102

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?

System info

• OS: Windows 11 Pro
• Claude Desktop version: 1.1.9310 (cb30ac)
• Subscription: Max (or Pro — pon el tuyo)

What's wrong
Cowork shows "La virtualización no está disponible" on every launch.
Restarting does not resolve it.

Verification — everything is correctly configured

• Microsoft-Hyper-V-All: Enabled
• HypervisorPlatform: Enabled
• Microsoft-Hyper-V-Hypervisor: Enabled
• CoworkVMService: Running (Automatic)
• vmcompute: Running
• bcdedit hypervisorlaunchtype: Auto
• Not domain-joined
• No other virtualization software installed
• New-VM works perfectly (Hyper-V is functional at system level)

Error from cowork_vm_node.log
HCS operation failed: failed to create compute system:
HcsWaitForOperationResult failed with HRESULT 0x80370102
"No se puede crear el sistema cowork-vm porque Hyper-V no está instalado en el host"

Conclusion
Hyper-V works correctly at the system level (can create VMs manually)
but CoworkVMService fails to use it. This appears to be a bug in how
Cowork detects or accesses Hyper-V, not a system configuration issue.

What Should Happen?

Cowork should start successfully. Hyper-V is fully functional on this system — New-VM creates VMs without errors — so Cowork should be able to use it without showing "Virtualization not available".

Error Messages/Logs

Steps to Reproduce

cowork_vm_node.log

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Versión 1.1.9310 (cb30ac)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_