All guides
Guides

How to Enable Virtualization (VT-x / AMD-V) on Windows for Emulators

Step-by-step guide to enable Intel VT-x or AMD-V in BIOS/UEFI on Windows so your Android emulator runs fast and without errors.

NovaPlay Team7 min read
How to Enable Virtualization (VT-x / AMD-V) on Windows for Emulators

If you have ever launched an Android emulator and been greeted by a warning like "VT-x is not available" or "Hardware acceleration is disabled", you already know how quickly that kills the experience. Games stutter, apps take forever to load, and the whole thing feels more like a slideshow than a gaming session. The fix almost always comes down to one setting buried in your BIOS or UEFI firmware: CPU virtualization.

This guide walks you through exactly what virtualization is, why emulators depend on it, how to check whether it is already active, how to turn it on in your firmware, and how to resolve Windows features that can quietly block it even after you enable it. By the end you will have a clear picture of every step, regardless of whether you have an Intel or AMD machine.

What Is CPU Virtualization and Why Does It Matter?

Modern Intel processors expose a feature called VT-x (Virtualization Technology for IA-32 and Intel 64). AMD calls the same concept AMD-V (also marketed as SVM, Secure Virtual Machine). Both let a hypervisor — the software layer that runs virtual machines or emulated environments — talk to the CPU at near-native speed instead of having to translate every instruction in software.

Without hardware virtualization, an Android emulator has to interpret ARM or x86 Android instructions one at a time on the host CPU. That is brutally slow. With virtualization enabled, the emulator can hand large blocks of work directly to the hardware, which is why the difference between a disabled and enabled VT-x can mean the gap between 10 FPS and a smooth 60+ FPS inside the emulated environment.

Emulators like NovaPlay are built around this acceleration from the ground up. It is not an optional extra — it is the foundation that makes running full Android apps and games practical on a Windows PC.

Step 1 — Check Whether Virtualization Is Already On

Before diving into the BIOS, it is worth checking whether virtualization is already active. Many laptops and pre-built desktops ship with it enabled by default.

Using Task Manager:

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Click the Performance tab.
  3. Select CPU from the left panel.
  4. Look at the bottom-right of the CPU graph for a line that reads Virtualization: Enabled or Virtualization: Disabled.

If it says Enabled, you can skip to the section on Windows feature conflicts below — there may still be something on the Windows side blocking emulator acceleration. If it says Disabled, keep reading.

Using the System Information tool:

Press Win + R, type msinfo32, and hit Enter. In the System Summary panel, look for the line Hyper-V Requirements. If it lists "VM Monitor Mode Extensions: Yes" and "Virtualization Enabled In Firmware: Yes", you are good. If the firmware line says No, the BIOS needs attention.

Step 2 — Enter Your BIOS or UEFI Firmware

Restart your computer. The moment the screen goes dark after shutdown, you need to press the firmware entry key repeatedly until the BIOS or UEFI interface appears. The correct key depends on your motherboard manufacturer:

  • ASUS: Delete or F2
  • MSI: Delete
  • Gigabyte: Delete or F2
  • ASRock: F2 or Delete
  • HP: F10 or Esc
  • Dell: F2 (at the Dell logo)
  • Lenovo: F1, F2, or the small Novo button on the side
  • Acer: F2 or Delete

If you are not fast enough, Windows will boot normally. You can try again, or use a slower route through Windows: go to Settings > System > Recovery > Advanced startup > Restart now, then choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. This drops you straight into the firmware without needing precise timing.

Step 3 — Find the Virtualization Setting

Once inside the BIOS or UEFI, the layout varies widely. Most modern UEFI interfaces have a graphical interface with mouse support; older boards show a text-based menu. Either way, the virtualization toggle is usually one of these:

Intel Systems

Look under one of these menus (names vary by board):

  • Advanced > CPU Configuration > Intel Virtualization Technology
  • Advanced > CPU Features > Intel (VMX) Virtualization Technology
  • M.I.T. > Advanced CPU Core Settings > Intel Virtualization Technology (Gigabyte)

Set the option to Enabled.

Some boards also list a separate setting called VT-d (Virtualization Technology for Directed I/O). This is for passing hardware devices directly through to virtual machines. You do not strictly need VT-d for running an Android emulator, but enabling it does not hurt.

AMD Systems

AMD boards typically place the setting under:

  • Advanced > CPU Configuration > SVM Mode
  • Advanced > AMD CBS > CPU Common Options > SVM Mode
  • OC Tweaker > Advanced CPU Configuration > SVM Mode (ASRock)

Set SVM Mode to Enabled.

Once you have made the change, press F10 (or whatever key your firmware displays for "Save & Exit") and confirm. The machine will reboot with virtualization active.

Step 4 — Disable Conflicting Windows Features

Here is where a lot of people get stuck even after correctly enabling VT-x or AMD-V. Windows ships with its own hypervisor called Hyper-V, and when Hyper-V is running, it sits between your CPU and every other application — including your emulator — claiming exclusive use of the virtualization layer. The result is that your emulator either refuses to start or runs slowly as if virtualization were disabled.

Check for and disable Hyper-V:

  1. Press Win + R, type optionalfeatures, and press Enter.
  2. In the Windows Features dialog, look for:
    • Hyper-V (and all sub-items)
    • Virtual Machine Platform
    • Windows Hypervisor Platform
  3. Uncheck all three, click OK, and restart.

Note: if you use WSL 2 (Windows Subsystem for Linux), it depends on Virtual Machine Platform. You may need to decide which you need more — WSL 2 or your emulator. WSL 1 does not require the hypervisor and can coexist with emulators.

Disable Memory Integrity (Core Isolation):

Windows 11 enables a security feature called Memory Integrity (also called HVCI, Hypervisor-Protected Code Integrity) by default on some machines. It runs a hypervisor to protect kernel memory, which can conflict with emulator acceleration.

To turn it off:

  1. Open Windows Security from the Start menu.
  2. Go to Device Security > Core isolation details.
  3. Toggle Memory Integrity off.
  4. Restart.

After the restart, check Task Manager's CPU performance panel again. Virtualization should now show Enabled.

Step 5 — Verify the Emulator Detects Acceleration

With everything in place, launch NovaPlay and open its diagnostic or settings panel. Look for a confirmation that hardware acceleration (WHPX on Windows, or the emulator's own virtualization backend) is active. If the emulator starts without any VT-x warnings and apps load quickly, you are done.

As a secondary check, you can open a Command Prompt as Administrator and run:

systeminfo

Scroll to the Hyper-V Requirements section at the bottom. Every line should now read Yes if you are on a system where Hyper-V is not installed, or the section may say "A hypervisor has been detected" if Hyper-V is still installed but your emulator has its own workaround.

Common Problems and Quick Fixes

  • The setting is greyed out in BIOS: Some OEM laptops (particularly budget models) lock the virtualization toggle. Check whether a BIOS update from the manufacturer unlocks it, or search your specific model alongside "enable VT-x" to see whether a workaround exists.
  • The option is not visible anywhere in BIOS: Try switching from EZ Mode to Advanced Mode inside your UEFI (usually an F7 or button in the corner).
  • Task Manager still shows Disabled after reboot: Double-check that Hyper-V and Windows Hypervisor Platform are fully uninstalled, not just unchecked temporarily.
  • Emulator shows acceleration errors despite Enabled in Task Manager: Memory Integrity (HVCI) is the most common remaining culprit — revisit the Core Isolation step above.

Does Your CPU Actually Support Virtualization?

Virtually every desktop and laptop CPU sold since 2010 supports VT-x or AMD-V. The only realistic exceptions are very old Atom-based netbooks, certain ultra-budget ARM-based Windows devices, and a handful of server Xeon SKUs with the feature deliberately disabled. If you are on a machine newer than roughly 2012, the capability is almost certainly there — it just might be switched off in firmware.

For more ways to squeeze performance out of your setup once virtualization is running, see the guide on how to boost FPS in Android games on PC. And if you are still choosing between emulators, the comparison of Android emulators for low-end PCs in 2026 covers where NovaPlay fits relative to the alternatives.

Conclusion

Enabling CPU virtualization is a one-time change that makes an enormous practical difference. A few minutes in your BIOS and a quick look at Windows feature settings is all it usually takes. Once the hardware layer is properly connected to your emulator, you get the kind of performance that makes playing mobile games on a large monitor with a keyboard and mouse genuinely enjoyable — not something you are constantly fighting.

Ready to put that virtualization to use? Download NovaPlay and start playing your favorite Android games on PC at full speed.

Advertisement

NovaPlay is an independent Android emulator and is not affiliated with, endorsed by, or associated with any third-party game or brand mentioned. Game names are used for descriptive purposes only.