Cowork

Claude's workspace failed to start with HRESULT 0x80370102 (hypervisor not running)

Last checked

The error

Claude's workspace failed to start with HRESULT 0x80370102 (hypervisor not running).
Hardware virtualization (Intel VT-x or AMD-V) is disabled in this device's firmware.
Enable it in BIOS/UEFI settings and restart. On devices with a firmware password or
vendor management (Dell Command, HP BCU, Lenovo, vPro), this may need to be changed
via that tool.

[error] [VM:start] VM boot failed: HCS operation failed: failed to create compute system: HcsWaitForOperationResult failed with HRESULT 0x80370102: ... "Cannot create system 'cowork-vm-...' since Hyper-V is not installed on the host."
[error] [VM:start] Startup failed: Error: HYPERVISOR_VIRT_DISABLED

Shown in the Cowork tab of Claude Desktop on Windows. The log lines are from cowork_vm_node.log in %APPDATA%\Claude\logs. Older builds labelled it HYPERVISOR_SERVICE_ERROR.

Cowork runs its workspace in a local virtual machine. 0x80370102 is the Windows Host Compute Service saying the Windows hypervisor is not running, so the VM cannot be created. The message blames firmware, and BIOS virtualization (Intel VT-x or AMD SVM) is the most common cause. If firmware is already on, run bcdedit /set hypervisorlaunchtype auto in an admin prompt and use Restart, not Shut down.

Why it happens

0x80370102 is a Windows error, not a Claude one: Cowork asks the Host Compute Service to create its VM, and Windows refuses because the hypervisor did not start at boot. Claude Desktop then maps any 0x80370102 to the firmware message, even when firmware is not the reason.

  1. Hardware virtualization is off in BIOS/UEFI. Many desktops and some laptops ship with Intel VT-x or AMD SVM Mode disabled. Task Manager > Performance > CPU shows Virtualization: Disabled (issue #34323).
  2. The hypervisor is set not to launch at boot. VMware, VirtualBox and some tuning tools change hypervisorlaunchtype to Off, so Windows boots without the hypervisor even with every feature enabled.
  3. Another firmware setting blocks the hypervisor, such as NX Mode (No-Execute) disabled in BIOS (issue #60371).
  4. Hyper-V devices disabled in Device Manager (Error 22), confirmed by Microsoft on a Windows 11 Pro 25H2 machine (microsoft/WSL issue #41527).
  5. A false positive in Claude Desktop: the hypervisor is running and the message still appears (issues #81093, #77711, #97365).

The fix

  1. 1 Check firmware first: open Task Manager > Performance > CPU. If Virtualization reads Disabled, enter BIOS/UEFI, enable Intel Virtualization Technology (VT-x) or AMD SVM Mode, save and restart.
  2. 2 If a firmware password or vendor tool (Dell Command, HP BCU, Lenovo, vPro) locks the BIOS, change it there or ask IT.
  3. 3 In an admin Command Prompt run bcdedit /enum | findstr hypervisorlaunchtype. If it does not say Auto, run bcdedit /set hypervisorlaunchtype auto.
  4. 4 Enable Virtual Machine Platform in admin PowerShell: Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -All. Windows Hypervisor Platform (-FeatureName HypervisorPlatform) is optional. Both exist on Home.
  5. 5 Use Restart, not Shut down. Fast Startup can resume a session that never loaded the hypervisor.
  6. 6 Confirm the hypervisor is actually running: (Get-CimInstance Win32_ComputerSystem).HypervisorPresent should print True. Then reopen Claude Desktop and the Cowork tab.
bcdedit /set hypervisorlaunchtype auto

When the firmware message is wrong

If HypervisorPresent prints True, hypervisorlaunchtype is Auto and Virtual Machine Platform is enabled, your BIOS is not the problem, whatever the message says. Issue #81093 shows this on Windows 11 Home 25H2 with VT-x on; it was closed as stale on 1 October 2026 without a fix.

First rule out two real causes: hypervisor events in the System log, and Hyper-V devices disabled in Device Manager (View > Show hidden devices). Re-enable any disabled one and restart.

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Hyper-V-Hypervisor'} -MaxEvents 5 | Format-List TimeCreated, Id, Message

Event 42 means VT-x or SVM is off in BIOS. Event 44 with an NX message means No-Execute is off in BIOS. No events plus HypervisorPresent True points at Claude Desktop's check, not your machine.

Windows 11 Home and 0x80370102

Anthropic documents two Windows requirements for Cowork: hardware virtualization and Virtual Machine Platform. It names no edition, and an Anthropic engineer said in issue #27906 that Windows 11 Home is supported. Home has Virtual Machine Platform but not full Hyper-V, which Cowork does not require.

Home users do report more failures. If everything above checks out and the error remains, stop debugging: use Cowork on the web at claude.ai, which needs no local VM, or Claude Code in a terminal.

Still failing?

  • Run Anthropic's Cowork readiness check, but confirm a ready verdict with HypervisorPresent.
  • If you run Claude inside a VM or VDI desktop (Parallels, Citrix, Hyper-V guest), nested virtualization must be exposed to that guest or Cowork cannot start.
  • Open cowork_vm_node.log: yukonSilver not supported is a different detection bug, and Missing HCS services is a different fix.

Related errors

Full guide"Virtual Machine Platform Not Available" for Claude: How to Enable It on Windows

Hit a different error?

Paste any agent error and get the cause and fix in seconds.

Open the decoder

Frequently asked questions

Does 0x80370102 always mean virtualization is off in BIOS?

No. It means the Windows hypervisor is not running. BIOS is the usual reason, but a boot setting, disabled Hyper-V devices or a Claude Desktop false positive show the same message.

Can Windows 11 Home run Cowork?

Anthropic's documented requirements are available on Home and Anthropic has said Home is supported, though many Home users report failures. Try the steps here, then fall back to Cowork on the web.

Will reinstalling Claude Desktop fix it?

Rarely. 0x80370102 comes from Windows, so a reinstall does not change whether the hypervisor runs. Fix the firmware or boot setting first, then reopen the app.

Stop firefighting agent errors

Decoding errors one at a time is the manual version of what BetterClaw automates. Run your agents on a no-code AI agent platform with managed models, retries and config validation built in.

Deploy Your Agent — Start FreeBook a Demo

Free plan available · Pro $49/mo · BYOK · 7-day money-back guarantee