Intel HAXM vs. Hyper-V/WHPX Choosing the Right Setup for Android Emulator on Windows

When setting up Android Studio on Windows, one of the first challenges developers face is getting the Android Emulator to run smoothly. Out of the box, the emulator can be painfully slow without hardware acceleration. That’s where Intel HAXM and Hyper-V/WHPX come in.

In this post, we’ll break down what these technologies are, how they interact with Android Studio, and when you should use one over the other.

Why Hardware Acceleration Matters for the Android Emulator

The Android Emulator simulates Android devices on your PC. Without acceleration, it relies only on software emulation, which is sluggish and almost unusable for serious development.

Hardware-assisted virtualization uses your CPU’s virtualization features (Intel VT-x, AMD-V) to boost performance. On Windows, this can be achieved using:

Intel HAXM (for Intel CPUs only)
Hyper-V + Windows Hypervisor Platform (WHPX)

Intel HAXM (Hardware Accelerated Execution Manager)

Intel HAXM is Intel’s virtualization engine designed specifically for the Android Emulator.

Key Points

Works only with Intel CPUs.
Requires Intel VT-x and Execute Disable Bit (XD/NX) to be enabled in BIOS.
Cannot run alongside Hyper-V (you must disable Hyper-V to use it).
Known for providing fast emulator performance.

How to Enable

Enable virtualization in BIOS.
Disable Hyper-V on Windows (dism.exe /Online /Disable-Feature:Microsoft-Hyper-V).
In Android Studio → SDK Manager → install Intel x86 Emulator Accelerator (HAXM Installer).
Run the installer manually from the Android SDK folder.

Hyper-V & Windows Hypervisor Platform (WHPX)

Hyper-V is Microsoft’s built-in hypervisor for running virtual machines.
Windows Hypervisor Platform (WHPX) is an API layer that allows applications (like the Android Emulator) to use Hyper-V for acceleration.

Key Points

Works with both Intel and AMD CPUs.
Allows you to keep Hyper-V enabled for other workloads (e.g., Docker, WSL2, or VM testing).
No need to disable Hyper-V as with HAXM.
Performance is usually good, though in some setups it can be slightly slower than HAXM.

How to Enable

In Windows Features, turn on:
- Hyper-V
- Windows Hypervisor Platform
Restart your PC.
In Android Studio, the emulator will automatically use WHPX for acceleration.

Choosing Between HAXM and Hyper-V/WHPX

Feature	Intel HAXM	Hyper-V/WHPX
CPU Support	Intel only	Intel & AMD
Hyper-V Dependency	Must be disabled	Must be enabled
Performance	Often slightly faster	Good, but can vary
Use Case	Best for dedicated Android dev environments	Best if you also use Docker, WSL2, or VMs

Android Studio + Emulator Workflow

Install Android Studio.
Configure an Android Virtual Device (AVD).
Choose the right acceleration option (HAXM or WHPX) based on your setup.
Run your emulator with hardware acceleration for smooth testing.

If you’re a Windows developer working with Android Studio, you’ll need to pick the right virtualization engine for your emulator:

Go with Intel HAXM if you have an Intel CPU and don’t rely on Hyper-V for anything else.
Stick with Hyper-V/WHPX if you use Docker, WSL2, or other VM workloads, or if you’re on an AMD CPU.

Either way, enabling hardware acceleration will make the Android Emulator far more usable and speed up your development workflow.