How to Enable Intel VT-x or AMD-V in BIOS on Windows 10/11 (2026 Guide)

Almost every modern Android emulator, virtual machine, and container runtime needs hardware virtualization. On Intel CPUs this is called VT-x (or Intel Virtualization Technology). On AMD CPUs it's AMD-V (or SVM Mode). Both ship disabled by default on most consumer PCs.

This guide walks through enabling it on Windows 10 and 11, with the exact BIOS path for each major OEM, and what to do when the toggle is missing, greyed out, or locked.

Last updated May 2026.

Before you start: do you actually need to enable VT?

Run this in Command Prompt:

systeminfo

Scroll to Hyper-V Requirements:

• VM Monitor Mode Extensions: Yes + Virtualization Enabled in Firmware: Yes → VT is already on. You're done.
• VM Monitor Mode Extensions: Yes + Virtualization Enabled in Firmware: No → Your CPU supports VT but it's off in BIOS. Follow this guide.
• VM Monitor Mode Extensions: No → Your CPU doesn't support hardware virtualization. Skip to the no-VT emulator guide.
• A hypervisor has been detected → Hyper-V is already running on top of VT. The settings table is hidden, but VT is enabled.

Step 1: Boot into UEFI / BIOS from Windows

The reliable way on Windows 10 and 11:

1. Open Settings → System → Recovery.
2. Under Advanced startup, click Restart now.
3. After reboot you'll see a blue menu. Pick Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.
4. Your PC will reboot directly into BIOS. No need to mash F2 or Delete at the splash screen.

This is what Microsoft documents on its official enablement page, and it's the only method that works consistently across OEMs since Fast Boot started skipping the BIOS prompt window on most laptops.

Step 2: Find the virtualization toggle

This is OEM-specific. Use the table below to jump to your manufacturer.

Step 3: Save and reboot

Press F10 (or use the Save & Exit menu on graphical BIOS UIs) and confirm. Your PC reboots into Windows. Re-run systeminfo and confirm Virtualization Enabled in Firmware: Yes.

OEM-specific walkthroughs

ASUS (motherboard or laptop)

1. Reboot into BIOS. ASUS EZ Mode opens by default — press F7 for Advanced Mode.
2. Go to Advanced → CPU Configuration.
3. For Intel: set Intel Virtualization Technology to Enabled. For AMD (ASUS Ryzen boards): set SVM Mode to Enabled.
4. (Optional, recommended for VM workloads) enable VT-d too.
5. F10 to save.

Dell (Latitude / Inspiron / XPS / OptiPlex)

1. Dell BIOS uses a sidebar tree. Expand Virtualization Support.
2. Enable Virtualization.
3. Also enable VT for Direct I/O if listed (needed for some Linux hypervisors).
4. Click Apply then Exit.

HP (Pavilion / Envy / EliteBook / ProBook)

1. Use arrow keys (HP BIOS is mostly keyboard-only).
2. Move to the Configuration tab.
3. Find Virtualization Technology (VTx) and set to Enabled. If listed, also enable Virtualization Technology for Directed I/O (VTd).
4. F10 to save.

Lenovo (ThinkPad / IdeaPad / Legion / Yoga)

1. Lenovo's BIOS opens to a Main screen. Move to Configuration (or Security on older ThinkPads).
2. Set Intel(R) Virtualization Technology to Enabled.
3. Set VT-d Feature to Enabled if present.
4. F10 to save. On ThinkPads, you may also need to power-cycle (not just reboot) for the change to take effect.

MSI (gaming desktops and laptops)

MSI's Click BIOS varies by board generation. On modern boards, the path is OC → CPU Features → Intel Virtualization Tech. On older boards it's Settings → Advanced → Integrated Peripherals → CPU Features. For Ryzen, it's SVM Mode in the OC tab.

Acer (Aspire / Predator / Nitro)

1. Acer BIOS often hides virtualization until you set a Supervisor Password (a long-running quirk on Aspire models).
2. If you don't see Intel Virtualization Technology on the Main or Advanced tab, go to Security → Set Supervisor Password, set one, save, re-enter BIOS — the toggle now appears.
3. Set it to Enabled.
4. F10 to save.

What if the option is missing or greyed out?

Run through this checklist in order:

1. Update your BIOS. Many older 6th/7th-gen Intel laptops shipped without the toggle, and vendors added it later via BIOS update. Check your OEM's support page for the latest BIOS version.
2. Set a Supervisor / Admin password. Acer, Toshiba, and some Sony VAIO laptops hide virtualization toggles until a Supervisor Password is set.
3. Check for vPro / TPM lock. Some enterprise SKUs ship with Intel vPro firmware policy that locks VT off. Only your IT admin can unlock this.
4. Verify your CPU supports VT at all. Look up your processor on Intel ARK (search the CPU model and check the Intel Virtualization Technology field). For AMD, all Ryzen and most FX-series support AMD-V; very old Athlon/Sempron may not.
5. Reset BIOS to factory defaults. A previous IT image may have hidden the option via a custom NVRAM variable. Load defaults from the Exit menu, save, re-enter, retry.

If none of these surface the option, the CPU likely cannot do VT, or the BIOS is permanently locked. Use a no-VT emulator instead.

After enabling: handle the Hyper-V conflict

Once VT is on, Windows can claim it via Hyper-V, WSL2, Windows Sandbox, or Memory Integrity. If you install an emulator that doesn't support running alongside Hyper-V, you'll see errors like "VT-x is not available, but is enabled in BIOS".

Two paths forward:

• Use a Hyper-V-aware emulator. BlueStacks 5.20+, MuMu Player 12, LDPlayer 9, and GameLoop all work with Hyper-V enabled. This is the cleaner choice for developers who also need WSL2 or Docker Desktop.
• Disable Hyper-V. Run OptionalFeatures.exe, uncheck Hyper-V Platform, Virtual Machine Platform, and Windows Hypervisor Platform, reboot. Also disable Memory Integrity from Windows Security → Device Security → Core Isolation if you want maximum FPS.

Decision tree: VT enablement

• VT is supported and the toggle is visible → enable it, you're done.
• Toggle is missing → update BIOS, then set a Supervisor Password, then re-check.
• Toggle is greyed out → corporate-locked or vPro-locked; contact IT or use a no-VT emulator.
• CPU doesn't support VT → use MuMu Nebula, NoxPlayer 7, or GameLoop in No-VT mode.
• VT enabled but emulator still fails → disable Hyper-V or switch to a Hyper-V-aware emulator build.

Related Codersera guides

• How to Run an Android Emulator Without Virtualization on Windows 10/11 (2026) — for when you can't enable VT.
• 10 Best Android Emulators for Low-End PC — 2 GB RAM, No VT, No Graphics Card — the listicle anchor for the no-VT cluster.
• Best Free Fire Emulators for PC Without VT (2026) — game-specific.
• Android Emulators: Complete Guide (2026) — pillar reference for the whole ecosystem.
• Best Android Emulator for Low-End PC 2026 — Ranked by RAM Tier.

FAQ

What's the difference between VT-x, VT-d, and AMD-V?

VT-x is Intel's hardware virtualization for CPU instructions. VT-d is Intel's hardware virtualization for I/O devices (PCIe passthrough). AMD-V is AMD's equivalent of VT-x, and on AMD boards it's labelled SVM Mode. Android emulators only need VT-x or AMD-V. VT-d is optional and useful mainly for advanced VM setups.

Why doesn't my BIOS have a virtualization option?

Three reasons: your CPU doesn't support it, your BIOS is outdated and the toggle was added in a later release, or your OEM hides it behind a Supervisor Password (common on Acer and old Toshiba laptops). Try a BIOS update first, then set a password.

Will enabling VT-x slow down my PC?

No. VT-x is dormant until a hypervisor uses it. There is no overhead from leaving it enabled.

Is it safe to enable VT-x?

Yes. It's a CPU capability, not a security toggle. Almost every business laptop ships with it enabled. The main side effect is that Hyper-V and Memory Integrity will be able to start, which can slow down some emulators that don't support running alongside them.

Why does Windows still say VT is disabled after I enabled it in BIOS?

Power-cycle the machine fully (shutdown, wait 10 seconds, power on). On Lenovo ThinkPads and Dell Latitudes, a soft reboot sometimes doesn't apply BIOS changes — only a cold boot does.

Can I enable VT on a Mac?

Macs (both Intel and Apple Silicon) ship with virtualization permanently enabled at the firmware level. There's no toggle — if you're on a Mac and an emulator says VT is missing, the cause is usually that the emulator doesn't support Apple Silicon yet.

What if my corporate laptop blocks BIOS access?

You can't enable VT yourself. Either ask IT to enable it (cite WSL2, Docker, or testing as the use case) or run a no-VT emulator like MuMu Nebula or NoxPlayer 7.

Does enabling VT-x conflict with secure boot or BitLocker?

No. VT-x, Secure Boot, and BitLocker are independent. Enable all three on a modern Windows install — it's the recommended security baseline.