Not in a Hypervisor Partition? Meaning & Fixes

“Not in a hypervisor partition” is an error message that appears when virtualization software (like Hyper-V, VirtualBox, or VMware) cannot start a virtual machine because the host system’s CPU is not running in the required privileged mode. This usually happens when virtualization is disabled in the BIOS/UEFI, a conflicting hypervisor is active, or the Windows Hypervisor Platform is misconfigured. Below, we explain what this error means, why it occurs, and how to fix it step by step.

What Does “Hypervisor Partition” Mean?

A hypervisor is a layer of software that sits between the hardware and virtual machines (VMs). It runs in a special CPU mode called “VMX root” (Intel) or “SVM” (AMD). The “hypervisor partition” is the isolated environment where the hypervisor itself executes. When a VM tries to start, the hypervisor checks that it has the necessary privileges. The error “Not in a hypervisor partition” means the VM’s code is not running in that privileged context—so the hypervisor refuses to launch it.

This message is most commonly seen in VirtualBox when trying to run a 64-bit guest, or in VMware Workstation when the host has Hyper-V enabled. It can also appear in Windows Sandbox or WSL2 if the Virtual Machine Platform feature is broken.

Why Does This Error Occur?

Several underlying causes can trigger this error:

• Virtualization disabled in BIOS/UEFI: The CPU’s virtualization extensions (Intel VT-x or AMD-V) are turned off in firmware.
• Hyper-V is enabled: Windows’ built-in hypervisor (Hyper-V) takes over the virtualization hardware, and third-party hypervisors like VirtualBox cannot use it unless they support the Windows Hypervisor Platform.
• Core Isolation / Memory Integrity: Windows Security’s “Memory Integrity” feature uses virtualization-based security (VBS), which can conflict with other hypervisors.
• Outdated hypervisor software: Old versions of VirtualBox or VMware may not recognize the current hypervisor state.
• Corrupted hypervisor files: Windows system files related to Hyper-V or the Virtual Machine Platform may be damaged.

How to Check If Virtualization Is Enabled

Before changing settings, verify whether your CPU supports and has enabled virtualization. In Windows, open Task Manager (Ctrl+Shift+Esc), go to the “Performance” tab, and select “CPU”. Look for “Virtualization: Enabled” or “Disabled”. If it says “Disabled”, you need to enable it in your BIOS/UEFI.

To enter BIOS/UEFI, restart your PC and press the key shown on the boot screen (often Del, F2, F10, or Esc). Navigate to the “Advanced” or “CPU Configuration” section, find “Intel Virtualization Technology” or “SVM Mode”, set it to “Enabled”, save and exit. The exact menu names vary by motherboard manufacturer.

Fixing the Error in Windows

If virtualization is already enabled, try these fixes in order:

1. Disable Hyper-V (if you don’t use it): Open Command Prompt as Administrator and run: dism /online /disable-feature /featurename:Microsoft-Hyper-V-All then restart. Alternatively, go to “Turn Windows features on or off” and uncheck “Hyper-V”.
2. Disable Memory Integrity: Go to Windows Security → Device Security → Core Isolation, turn off “Memory Integrity”, and restart.
3. Use Windows Hypervisor Platform (if you need Hyper-V): If you want to keep Hyper-V, enable “Windows Hypervisor Platform” in Windows Features. This allows VirtualBox and VMware to use Hyper-V’s API. After enabling, restart.
4. Update your virtualization software: Install the latest version of VirtualBox or VMware, as newer versions have better compatibility with Hyper-V.
5. Repair system files: Run sfc /scannow and dism /online /cleanup-image /restorehealth in an elevated Command Prompt, then restart.

When to Keep Hyper-V vs. Disable It

Deciding whether to disable Hyper-V depends on your primary use case:

• If you use VirtualBox or VMware: Disabling Hyper-V is usually the simplest fix, as these tools have their own hypervisor and don’t need Windows’.
• If you use Docker, WSL2, or Windows Sandbox: These require Hyper-V or the Virtual Machine Platform. In that case, enable “Windows Hypervisor Platform” and use a VirtualBox version that supports it (6.0+).
• If you run Hyper-V VMs: Keep Hyper-V enabled and avoid third-party hypervisors that don’t support the Windows Hypervisor Platform.

Note that you can have both Hyper-V and VirtualBox installed, but they must cooperate through the Windows Hypervisor Platform. If you don’t need Hyper-V, disabling it gives you the best performance with VirtualBox/VMware.

Common Misconceptions

One common myth is that the error means your CPU is too old. In reality, most CPUs from the last decade support virtualization. Another misconception is that you must reinstall Windows. The error is almost always fixable with the steps above. Also, some users think that enabling “Virtualization” in BIOS is enough—but if Hyper-V is active, it still conflicts. The error can also appear if you have a 32-bit host OS trying to run 64-bit guests; ensure your Windows is 64-bit.

Frequently Asked Questions

Why does VirtualBox say “Not in a hypervisor partition” even though VT-x is enabled?

This usually happens because Hyper-V is still enabled in Windows. Even if you don’t use Hyper-V, its services run in the background. Disable Hyper-V via Windows Features or the DISM command, then restart.

Can I run VirtualBox and Hyper-V at the same time?

Yes, but you need to enable “Windows Hypervisor Platform” in Windows Features and use VirtualBox 6.0 or later. This allows VirtualBox to use Hyper-V’s hypervisor instead of its own, avoiding the conflict.

Does the error affect WSL2?

WSL2 uses a lightweight VM, so if the hypervisor partition is unavailable, WSL2 may fail to start with a similar error. Ensure the “Virtual Machine Platform” and “Windows Subsystem for Linux” features are enabled, and that virtualization is on in BIOS.

How do I know if my CPU supports virtualization?

Check Task Manager → Performance → CPU → Virtualization. If it says “Enabled”, it’s on. If “Disabled”, your CPU supports it but it’s off in BIOS. If it says “Not supported”, your CPU lacks VT-x/AMD-V (rare for modern CPUs).

Will disabling Hyper-V affect my Docker Desktop?

Yes, Docker Desktop on Windows uses Hyper-V or WSL2. If you disable Hyper-V, Docker will not work unless you switch to WSL2 backend and keep the Virtual Machine Platform enabled. You can disable only the Hyper-V feature itself, but keep the Virtual Machine Platform.

Is it safe to disable Memory Integrity to fix this error?

Memory Integrity is a security feature that protects against malicious code injection. Disabling it reduces security slightly, but it’s generally safe if you have a good antivirus and practice safe browsing. Re-enable it after you’ve fixed the hypervisor issue if you don’t need it off.

Related

• Hitman 3 Crashing? Fixes for PC, PS, Xbox
• Clear Disk Space iMovie: Simple Steps That Work
• Whiteboard Ide: How a Canvas Helps Coding Agents