The “Hypervisor not running” error on Windows 10 means your PC cannot start Hyper-V, Virtual Machine Platform, or Windows Sandbox because the hypervisor layer is disabled or blocked. The fix is to enable virtualization in your BIOS/UEFI, turn on the required Windows features, and ensure no conflicting third-party virtualization software is running.
What Causes the Hypervisor Not Running Error
Windows 10 uses a hypervisor (Hyper-V) to run virtual machines, Windows Sandbox, and some security features like Memory Integrity (Core Isolation). When you see the error “Hypervisor not running” — often when launching a VM or enabling a feature — it means the hypervisor cannot start. Common causes include:
- Virtualization (VT-x/AMD-V) is disabled in the BIOS/UEFI.
- Required Windows features (Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform) are off.
- Another hypervisor (like VMware Workstation or VirtualBox with its own hypervisor) is conflicting.
- Windows is running in a virtual machine without nested virtualization enabled.
- Outdated drivers or a pending Windows update.
Step 1: Enable Virtualization in BIOS/UEFI
Most modern PCs have virtualization disabled by default. To enable it:
- Restart your PC and press the key to enter BIOS/UEFI (usually Del, F2, F10, or Esc — check your manufacturer’s manual).
- Look for a setting named Intel Virtualization Technology (VT-x), AMD-V, or SVM Mode. It may be under Advanced, CPU Configuration, or Security.
- Set it to Enabled.
- Save and exit (usually F10).
If you don’t see the option, your CPU may not support virtualization. Check with the CPU manufacturer’s specifications. Also note that some laptops require a BIOS update to expose the setting.
Step 2: Turn On Required Windows Features
Windows 10 needs certain features enabled. Open the Control Panel > Programs > Turn Windows features on or off. Check the following:
- Hyper-V (includes Hyper-V Management Tools and Hyper-V Platform)
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Sandbox (if you use it)
Click OK and restart when prompted. If any feature fails to install, you may need to run dism /online /cleanup-image /restorehealth in an elevated Command Prompt.
Step 3: Check for Conflicting Software
Third-party virtualization tools can block Hyper-V. If you have VMware Workstation or VirtualBox installed, they may be using their own hypervisor. You can either:
- Uninstall them, or
- Disable their hypervisor modules (e.g., in VMware, set Hyper-V support off in the VM settings, or in VirtualBox, use VBoxManage setextradata global “VBoxInternal/Devices/ahci/0/Config/…” — but the simplest is to uninstall).
Also, third-party antivirus with hypervisor-based protection (like some versions of Kaspersky or AVG) can conflict. Temporarily disable them to test.
Step 4: Verify Hypervisor is Actually Running
Open an elevated Command Prompt and run:
systeminfo
Look for the line Hyper-V Requirements. If it says “A hypervisor has been detected. Features required for Hyper-V will not be displayed,” then the hypervisor is running. If it says “Hypervisor is not running,” continue with the steps below.
You can also run bcdedit /set hypervisorlaunchtype auto (as Administrator) to force the hypervisor to start at boot. Reboot after.
Step 5: Update Drivers and Windows
Outdated chipset or BIOS drivers can prevent virtualization from working. Visit your PC manufacturer’s support page and install the latest BIOS/UEFI and chipset drivers. Then run Windows Update and install all pending updates, including optional ones. A cumulative update often fixes hypervisor bugs.
Frequently Asked Questions
Why does the error appear when I try to run Windows Sandbox?
Windows Sandbox requires the hypervisor to be running. If you see the error, follow the same steps: enable virtualization in BIOS, enable the Virtual Machine Platform and Windows Sandbox features, and ensure no conflicting software. Also, your CPU must support virtualization and be enabled.
Can I run Hyper-V and VMware Workstation at the same time?
Yes, but only with specific configurations. VMware Workstation 15.5+ and later support running alongside Hyper-V using Windows Hypervisor Platform. However, this is not always stable. For most users, it’s simpler to use one hypervisor at a time.
Does enabling Hyper-V slow down my PC?
Hyper-V uses a small amount of memory and CPU when idle, but the performance impact is minimal. Some gaming features like anti-cheat may be affected if they rely on hardware virtualization. If you don’t use VMs, you can disable Hyper-V to avoid any potential conflicts.
How do I know if my CPU supports virtualization?
Run systeminfo in Command Prompt. Look for the Hyper-V requirements section. If it says “Virtualization Enabled In Firmware: Yes,” it’s enabled. If it says “No,” your BIOS may have it off, or your CPU doesn’t support it. You can also check the CPU model on the manufacturer’s website.
What if I don’t have a BIOS option for virtualization?
Some OEM systems hide the option. Try updating your BIOS to the latest version. If it still doesn’t appear, your CPU may not support it, or the manufacturer has disabled it. In that case, you cannot run Hyper-V or Windows Sandbox.
Is it safe to disable Hyper-V?
Yes, if you don’t use virtual machines or Windows Sandbox. However, some Windows security features like Memory Integrity (Core Isolation) rely on the hypervisor. If you disable Hyper-V, those features will be turned off, potentially reducing security. Only disable it if you understand the trade-off.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Spotify Jam Not Working on Mobile? Fixes That Work
- Windows 10 No Internet Secured WiFi Error Fix
- Multi-Cloud GPU Failover Design Guide
- Error Code Currant Destiny? Meaning & Fixes
- Install Windows After Replacing Hard Drive
- AirPlay with Roku Multi-Device Setup: A How-To