[BUG] Cowork VM fails at create_vm_config with HCS 0x80370102 (HYPERVISOR_VIRT_DISABLED) on Windows 10 Pro 22H2 despite Hyper-V fully 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's local VM (workspace) never starts on this machine. It fails at the create_vm_config step on every app launch with HCS error 0x80370102, and the app classifies it as HYPERVISOR_VIRT_DISABLED — even though virtualization, the hypervisor, and the Hyper-V feature are all enabled and running on the host.

The VM bundle itself downloads and installs fine (bundle version 882518393ed4ce89020bd48d99d5daf114999773).

Verified on the host

• (Get-CimInstance Win32_Processor).VirtualizationFirmwareEnabled = True
• (Get-CimInstance Win32_ComputerSystem).HypervisorPresent = True
• bcdedit hypervisorlaunchtype = Auto
• Microsoft-Hyper-V-All = Enabled, VirtualMachinePlatform = Enabled
• Services vmms, vmcompute, CoworkVMService = Running
• Rebooted after enabling Hyper-V → same error

Environment

• Windows 10 Pro 22H2 (build 19045), Microsoft Store (MSIX) install
• Claude Desktop 2.9939.2
• CPU: AMD Ryzen 9 7950X

What Should Happen?

With virtualization, the hypervisor and Hyper-V all enabled and running, the Cowork VM should be created and boot. If the host is genuinely unsupported (e.g. Windows 10), the app should say so clearly instead of reporting "virtualization disabled".

Error Messages/Logs

cowork_vm_node.log
[info] [VM:start] Bundle version: 882518393ed4ce89020bd48d99d5daf114999773
[info] [VM:start] memory=4GB
[info] [VM:start] Windows VM service configured
[info] [VM:steps] create_network completed (1ms)
[info] [VM:steps] create_vm_config started
[error] [VM:start] VM boot failed: HCS operation failed: failed to create compute system: HcsWaitForOperationResult failed with HRESULT 0x80370102: {"Error":-2143878910, ... "ErrorEvents":[{"Message":"Cannot create system 'cowork-vm-…' since Hyper-V is not installed on the host.","Provider":"17103e3f-3c6e-4677-bb17-3b267eb5be57","EventId":11008, ... "0x80370102"}]}
[error] [VM:start] HCS error detected, available=true, missing=[], sentinel=HYPERVISOR_VIRT_DISABLED
[info] Dispatching startup error: HYPERVISOR_VIRT_DISABLED
[error] [VM:start] Startup failed: Error: HYPERVISOR_VIRT_DISABLED
[warn] [VM:start] Skipping auto-reinstall (hypervisor error), leaving VM offline (will retry on next app launch)

(ErrorMessage/Message fields were localized Korean in the original log and got mojibake'd; translated above.)

Steps to Reproduce

1. Windows 10 Pro 22H2 (19045), AMD Ryzen 9 7950X, SVM enabled in firmware
2. Enable Hyper-V: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -All, reboot
3. Confirm HypervisorPresent=True, hypervisorlaunchtype=Auto, vmms/vmcompute/CoworkVMService running
4. Launch Claude Desktop 2.9939.2 (MSIX) and try to use a Cowork task that needs the local workspace
5. Check %LOCALAPPDATA%\Claude\Logs\cowork_vm_node.log → fails at create_vm_config with 0x80370102 / HYPERVISOR_VIRT_DISABLED

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Desktop 2.9939.2 (Cowork, Windows MSIX)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Related: #77711 (same HRESULT with all Hyper-V components healthy, closed as stale with "open a new issue if still relevant"), #34201 (same Windows 10 Pro 19045 + MSIX, same error, closed as not planned), #36962, #59035, #60371, #81093, #27801

Side note: Before reaching this error, the VM bundle update silently failed for weeks with Insufficient disk space: ... need 16.1 GB logged only as a non-fatal warning (Stale-bundle refresh failed (non-fatal)), while old bundle versions kept accumulating under vm_bundles\warm\. Surfacing low-disk failures to the user would help.