sodcalculator

10 Tech How-To

Fix VirtualBox VT-x Not Available in Windows 10

Guide 10-48055 · Updated · Step by step

If VirtualBox reports “VT-x is not available” on Windows 10, the fix is usually to enable Intel Virtualization Technology (VT-x) or AMD-V in your computer’s BIOS/UEFI settings. This error appears when the CPU’s virtualization extensions are disabled, not because VirtualBox is broken. Follow the steps below to check and enable them, and you’ll be running virtual machines again in minutes.

What Does the VT-x Error Mean?

VT-x (Intel Virtualization Technology) and AMD-V (AMD Virtualization) are hardware features built into most modern CPUs that allow virtualization software like VirtualBox to run guest operating systems efficiently. When you see “VT-x is not available (VERR_VMX_NO_VMX)” or similar, it means the CPU supports virtualization but it’s turned off—usually in the firmware settings. This can also happen if another hypervisor (like Hyper-V) is running, or if your PC’s security settings are blocking it.

Why Is Virtualization Disabled by Default?

Many PC manufacturers ship systems with virtualization disabled in the BIOS to reduce attack surface or because most users never need it. On some laptops, especially business models, the option may be hidden or named differently (e.g., “Intel Virtualization Technology,” “VT-x,” “AMD SVM Mode,” or “Virtualization Extensions”). Windows 10 itself doesn’t control this setting—it’s a low-level firmware option that the OS can’t override.

How to Enable VT-x in BIOS/UEFI

  1. Restart your computer and press the key to enter BIOS/UEFI setup. Common keys are F2, Del, F10, or Esc—check your manufacturer’s splash screen.
  2. Navigate to the Advanced or Configuration tab (the exact name varies).
  3. Look for an option like Intel Virtualization Technology, VT-x, AMD SVM, or Virtualization Extensions.
  4. Set it to Enabled.
  5. Save and exit (usually F10). Your PC will reboot.

If you can’t find the option, search online for your specific motherboard or laptop model (e.g., “Dell XPS 13 enable VT-x”)—manufacturers often hide it under different menus. On some systems, you may need to disable “Secure Boot” or “Memory Integrity” first, but that’s rare.

Check If Virtualization Is Already On

Before diving into BIOS, you can check if virtualization is already enabled in Windows:

  • Open Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and select CPU. Look for “Virtualization: Enabled” at the bottom right.
  • Or open Command Prompt and run systeminfo. Look for “Hyper-V Requirements”—if it says “Yes” for virtualization, it’s on.

If Task Manager says “Enabled” but VirtualBox still complains, the issue is likely Hyper-V, not the BIOS.

Hyper-V Conflict: The Hidden Culprit

Windows 10 includes Hyper-V, a built-in hypervisor that can conflict with VirtualBox. If Hyper-V is enabled, VirtualBox can’t use VT-x because Hyper-V has already claimed it. Symptoms include the VT-x error even though BIOS is correct. To fix this, disable Hyper-V:

  1. Go to Control Panel > Programs > Turn Windows features on or off.
  2. Uncheck Hyper-V and also uncheck Windows Hypervisor Platform if present.
  3. Click OK and restart.

Alternatively, run Command Prompt as Administrator and enter: dism /online /disable-feature /featurename:Microsoft-Hyper-V-All then restart. Note that disabling Hyper-V may affect other features like WSL2 (Windows Subsystem for Linux) or Device Guard—you’ll need to re-enable it if you use those.

Other Possible Causes and Quick Fixes

If BIOS is correct and Hyper-V is off, try these:

  • Update VirtualBox to the latest version—older builds sometimes misdetect hardware.
  • Install the VirtualBox Extension Pack if you’re using USB devices, but it’s not required for the VT-x error.
  • Check for a BIOS update from your motherboard manufacturer—some older firmware had bugs with virtualization detection.
  • Disable Core Isolation / Memory Integrity in Windows Security > Device Security > Core Isolation. This feature can block virtualization in rare cases.
  • Run VirtualBox as Administrator—right-click the icon and select “Run as administrator” to rule out permission issues.

If you’re on a laptop, ensure it’s plugged in—some power-saving modes disable virtualization to save battery.

What If My CPU Doesn’t Support VT-x?

Very old CPUs (pre-2008) may lack VT-x entirely. In that case, you can’t enable it—it’s a hardware limitation. However, you can still run 32-bit guest OSes in VirtualBox, but 64-bit guests won’t work. Check your CPU model on Intel’s or AMD’s website to confirm support. If you’re stuck, consider using a different virtualization tool like VMware Workstation Player, which sometimes handles older CPUs better, or use a cloud VM service.

Frequently Asked Questions

How do I know if my CPU has VT-x?

Use the systeminfo command in Command Prompt—if “Virtualization Enabled In Firmware” says “Yes,” it’s on. You can also download Intel’s Processor Identification Utility or check your CPU specs online. Most Intel Core i3/i5/i7/i9 and AMD Ryzen CPUs from the last decade support it.

Why does VirtualBox say VT-x is not available even though it’s enabled in BIOS?

This usually points to Hyper-V being active. Check Windows Features and disable Hyper-V, then restart. Also ensure you’re not using a virtual machine within a virtual machine (nested virtualization) unless your host CPU explicitly supports it.

Can I enable VT-x without entering BIOS?

No, it’s a firmware setting that can only be changed in BIOS/UEFI. Windows cannot override it. Some enterprise PCs allow remote management tools to change it, but for most users, a reboot into BIOS is required.

Does enabling VT-x slow down my PC?

No—it has no noticeable impact on normal performance. It only activates when virtualization software uses it. In fact, some security features (like Windows Sandbox) require it, so leaving it on is generally safe.

Will disabling Hyper-V affect Docker or WSL2?

Yes. WSL2 and Docker Desktop (in Windows mode) rely on Hyper-V. If you disable it, those tools will stop working. You’ll need to choose between VirtualBox and those features, or use VirtualBox’s Hyper-V compatibility mode (available in newer versions) which allows both to coexist, though with a performance hit.

My BIOS doesn’t have a virtualization option—what now?

Some OEMs hide it or use a different name like “SVM Mode” (AMD) or “Vanderpool” (older Intel). If you truly can’t find it, check if there’s a BIOS update that adds the option. If not, your system may be locked down (common on some corporate laptops), and you’ll need to contact the manufacturer.

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

The whole Tech How-To bed →