Share via

virtualization

angee bruner 0 Reputation points
2026-06-20T13:18:10.6433333+00:00

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.

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. HLBui 7,240 Reputation points Independent Advisor
    2026-06-20T14:28:47.2733333+00:00

    Hi Angee Bruner

    That HRESULT 0x80370102 error is basically Windows telling you the hypervisor isn’t running because hardware virtualization is disabled. The fix is to go into your BIOS/UEFI and enable Intel VT‑x or AMD‑V, depending on your processor. On some devices, especially enterprise laptops, you might also have a firmware password or vendor management tool (like Dell Command, HP BCU, Lenovo Vantage, or Intel vPro) that controls those settings so you’ll need to unlock or adjust it there.

    Once virtualization is enabled, restart the machine and the hypervisor should kick in normally. If you still see a blank workspace, double‑check that Hyper‑V is installed and active in Windows Features, and that no other virtualization software is conflicting. It’s a pretty common hiccup when setting up dev environments, so don’t worry once the BIOS setting is flipped, things usually run smoothly.

    Give that a try and let me know how it goes. And if this answer helps you move forward, please hit “accept answer”

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-20T13:18:26.1833333+00:00

    The error 0x80370102 (hypervisor not running) with the message about hardware virtualization being disabled means the CPU’s virtualization extensions (Intel VT-x or AMD‑V) are turned off in firmware. They must be enabled before Hyper‑V (and thus Claude’s workspace) can start.

    Follow these steps on the affected Windows device:

    1. Boot into UEFI/BIOS firmware settings
      Use one of these supported methods:
      • From Windows:
        1. Open Settings → System → Recovery (on Windows 10: Update & Security → Recovery).
        2. Under Recovery options, next to Advanced startup, select Restart now.
        3. In Windows Recovery Environment, select Troubleshoot → Advanced options → UEFI Firmware settings → Restart.
        4. The device restarts into the UEFI/BIOS utility.
      • Or at power‑on:
        1. Turn the PC on and immediately press the manufacturer’s firmware key repeatedly (commonly Esc, Delete, F1, F2, F10, F11, or F12; on tablets often Volume Up/Down).
    2. Enable CPU virtualization in firmware
      In the UEFI/BIOS menus, locate and enable the CPU virtualization option:
      • On Intel platforms: enable Intel Virtualization Technology (Intel VT / VT‑x).
      • On AMD platforms: enable AMD Virtualization (AMD‑V) technology.
      The exact menu name and location differ by OEM; if needed, use the OEM‑specific guidance for enabling virtualization (Acer, Asus, Dell, HP, Lenovo, etc.) or the device’s documentation. Important: Only change the virtualization‑related setting; changing unrelated firmware options can prevent Windows from booting.
    3. Save changes and reboot
      • Save and exit the UEFI/BIOS (often via Save & Exit or F10).
      • The PC restarts with hardware virtualization enabled.
    4. Ensure Windows virtualization features are enabled (if required)
      If this device was upgraded from Windows 10 to Windows 11, also confirm the Windows feature is on:
      1. Select Start, type Windows features, and open Turn Windows features on or off.
      2. In the Windows Features dialog, check Virtual Machine Platform (and Hyper‑V components if using Hyper‑V directly).
      3. Select OK and restart if prompted.

    After these steps, the hypervisor should start correctly and Claude’s workspace should no longer fail with 0x80370102.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.