How to Enable Virtualization on Your PC (BIOS, Windows & More)

Virtualization is one of those settings that sits quietly disabled on millions of computers — until someone tries to run a virtual machine, use WSL 2, or launch an Android emulator and hits a wall. Enabling it is usually straightforward, but the exact path depends on your hardware, firmware, and operating system setup.

Here's what virtualization actually is, how to turn it on, and what to watch for along the way.

What Is CPU Virtualization?

Hardware virtualization allows your processor to run multiple isolated operating systems simultaneously by creating virtual versions of hardware resources — CPU cores, RAM, storage, and network interfaces. The host machine manages these virtual environments (called virtual machines, or VMs) without them interfering with each other.

Modern processors include dedicated virtualization extensions built directly into the silicon:

• Intel calls theirs Intel VT-x (Virtualization Technology)
• AMD calls theirs AMD-V (AMD Virtualization)

Both do the same fundamental job. The extensions are almost universally present on processors made in the last decade — but they're frequently disabled by default at the firmware level.

Why Would You Need to Enable It?

Virtualization is required for a growing list of tasks:

• Running virtual machines via VMware, VirtualBox, or Hyper-V
• Using Windows Subsystem for Linux 2 (WSL 2) on Windows 10/11
• Running Android emulators like those used in Android Studio
• Enabling Windows Sandbox or Credential Guard
• Some containerization tools like Docker Desktop on Windows

If any of these are relevant to your workflow, and you're seeing errors like "VT-x is not available" or "This host supports Intel VT-x, but Intel VT-x is disabled," the fix starts in your BIOS or UEFI firmware.

Step 1: Check Whether Virtualization Is Already Enabled

Before diving into BIOS settings, verify the current status:

On Windows:

1. Open Task Manager (Ctrl + Shift + Esc)
2. Click the Performance tab
3. Select CPU
4. Look for Virtualization: Enabled or Disabled near the bottom

If it already shows Enabled, you may not need to change anything at the firmware level — the issue might be a Windows feature that needs activating separately.

Step 2: Enter Your BIOS or UEFI Firmware Settings ⚙️

This is where most of the variation happens. The method for entering firmware settings differs by manufacturer and system age.

Common key presses during startup:

You need to press the key immediately after powering on — before Windows starts loading. If you miss the window, restart and try again.

On Windows 10/11, you can also access UEFI settings without timing keystrokes:

1. Go to Settings → System → Recovery
2. Under Advanced startup, click Restart now
3. Choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart

Step 3: Find the Virtualization Setting in BIOS/UEFI

Once inside the firmware interface, the setting's location varies by manufacturer. There's no universal layout.

Where to look:

• Advanced tab → CPU Configuration → Intel Virtualization Technology
• Advanced tab → CPU Configuration → SVM Mode (AMD systems)
• Security tab (on some Lenovo and HP systems)
• OC or Overclocking tabs (on some ASUS and MSI boards)

Search for terms like "VT-x," "VT-d," "AMD-V," "SVM," or "Virtualization Technology." You may find multiple related options:

• VT-x / AMD-V — core CPU virtualization (this is the one you need for VMs)
• VT-d / AMD Vi — I/O virtualization for passing through hardware devices to VMs (optional for most users)

Set the relevant option to Enabled, then save and exit (usually F10).

Step 4: Enable Virtualization Features Inside Windows 🖥️

Enabling it in BIOS is often only half the job. Windows has its own virtualization features that must be turned on separately.

To enable Hyper-V (Windows 10/11 Pro, Enterprise, Education):

1. Open Control Panel → Programs → Turn Windows features on or off
2. Check Hyper-V (expand it and check all sub-items)
3. Click OK and restart

To enable WSL 2:

1. Open PowerShell as Administrator
2. Run: wsl --install
3. Restart when prompted

Docker Desktop and most emulators will either use Hyper-V or their own hypervisor layer — they typically detect what's available and configure themselves, but both require virtualization to be active at the hardware level first.

What Can Go Wrong

A few variables affect whether this process goes smoothly:

• Older processors may lack VT-x/AMD-V entirely — check your CPU's spec sheet if you're unsure
• Secure Boot and TPM settings in BIOS can interact with virtualization in unexpected ways, particularly on Windows 11
• Hyper-V conflicts with some third-party hypervisors (VMware and VirtualBox have historically had compatibility issues when Hyper-V is active, though this has improved in recent versions)
• Home editions of Windows don't include Hyper-V — WSL 2 and third-party tools like VirtualBox work without it, but the feature set is narrower

Whether the standard steps above cover your situation — or whether you'll run into any of these complications — depends heavily on your specific processor generation, Windows edition, and what you're ultimately trying to run.