How To Enable Virtualization In Windows 11 | The BIOS Toggle

Enabling hardware virtualization on a Windows 11 PC means flipping one setting inside your UEFI firmware, not installing a piece of software from within the operating system.

Virtualization lets your Windows 11 PC run virtual machines, power Windows Subsystem for Linux, and keep emulators like BlueStacks running smoothly. The catch is that the feature isn’t something you download — it’s a hardware switch built into your computer’s firmware, often set to Disabled by default.

This guide walks through how to enable virtualization in Windows 11 using the official recommended path, identifies the correct setting for your CPU, and explains what to do if the toggle looks on but nothing seems to work.

Why Virtualization Isn’t a Windows Toggle

Hardware virtualization is a CPU-level capability managed by the system firmware, not a Windows component you can enable from the desktop. That’s why searching for a simple checkbox inside Settings leads nowhere.

Many users confuse this with the Virtual Machine Platform found in the Turn Windows features on or off menu. Enabling that software feature does nothing if the physical CPU virtualization switch in the UEFI/BIOS is still disabled. The firmware toggle is what actually unlocks the hardware feature at the chip level.

Getting to UEFI: The Reliable Recovery Route

Microsoft’s official guidance for enabling virtualization recommends using the Windows Recovery Environment to access UEFI firmware settings. This method works on every modern Windows 11 device that supports UEFI and removes the guesswork of tapping the correct boot key during startup.

  1. Open Settings and navigate to System.
  2. Go to Recovery.
  3. Next to Advanced startup, select Restart now.
  4. After the PC reboots, choose Troubleshoot.
  5. Select Advanced options, then UEFI Firmware Settings.
  6. Click Restart.

The system boots directly into the firmware interface rather than back to the Windows login screen.

Which BIOS Setting Enables Virtualization?

Once you are inside the firmware setup utility, the setting is usually located under the Advanced or CPU Configuration menu. The exact label depends on your processor vendor.

CPU Vendor Setting Name Also Appears As
Intel Intel Virtualization Technology Intel VT-x, Intel VMX
AMD SVM Mode AMD-V, Secure Virtual Machine
Intel VT-d Directed I/O Virtualization
AMD IOMMU I/O Virtualization
Any Hardware Virtualization Virtualization Technology

Switch the corresponding setting to Enabled, save your changes (usually F10), and exit. The PC restarts with virtualization active at the hardware level.

How to Confirm Virtualization Is On

Windows makes verification simple. You do not need to install any third-party tools to check if the toggle stuck.

Right-click the taskbar and open Task Manager, then go to the Performance tab and select CPU.

In the lower-right corner of the CPU view, you should see Virtualization: Enabled. If it reads Disabled, the firmware change either did not save or was applied to the wrong setting.

What If VT-x Is Enabled But an App Says It’s Not?

This is the most frustrating scenario: you double-checked the BIOS and the setting shows Enabled, but an emulator, BlueStacks, or Windows itself claims virtualization is off. The cause is almost always a hypervisor conflict running inside Windows.

Two features typically cause the block:

  • Memory Integrity (Core Isolation): A security feature in Windows Security that can reserve virtualization capabilities. Turning it off and restarting often resolves the conflict.
  • Existing Hyper-V hypervisor: If you use Windows Subsystem for Linux, Docker, or have Hyper-V enabled, the hypervisor may hold the lock. Running the command bcdedit /set hypervisorlaunchtype off in an admin Command Prompt and restarting frees the hardware layer.

If Task Manager reads Not supported instead of Disabled, the CPU genuinely lacks the capability, and neither a firmware change nor a Windows update will add it.

The Windows-Level Features You Might Also Need

Some applications like WSL 2, Windows Sandbox, or newer Android emulators require the Windows virtualization components to be active on top of the firmware toggle.

  1. Open Start and search for Turn Windows features on or off.
  2. Check Virtual Machine Platform and optionally Windows Hypervisor Platform.
  3. Click OK and restart when prompted.

These features cannot function unless the hardware switch from the previous steps is already enabled.

Symptom Likely Cause Fix
Setting not visible in BIOS Hidden by OEM or legacy BIOS mode Check for “Overclocking” or “Advanced Chipset” menus; use Recovery route instead of boot key.
App says disabled, BIOS says on Hyper-V or Memory Integrity conflict Disable Memory Integrity or run bcdedit /set hypervisorlaunchtype off.
UEFI option missing in Recovery System installed in legacy BIOS mode Enter firmware during boot via F2, F10, or Del key.
Task Manager shows “Not supported” CPU lacks virtualization features Check CPU compatibility on Intel ARK or AMD product page; upgrade required.

Finishing the Job: The Quick Enable Reference

Once the steps are done, the whole process takes under a minute for future reference.

  1. Open Settings > System > Recovery > Restart now (under Advanced startup).
  2. Select Troubleshoot > Advanced options > UEFI Firmware Settings > Restart.
  3. Find Intel VT-x or AMD SVM Mode in the BIOS, enable it, save, and exit.
  4. Verify with Task Manager > Performance > CPU > Virtualization: Enabled.

That single toggle is the only barrier between the hardware and the apps that need it.

References & Sources