HAXM Is Gone: How to Switch to WHPX and AEHD for Android Emulators in 2026

If you have followed Android emulation for a few years, you will remember HAXM, the Intel Hardware Accelerated Execution Manager. For a long time it was the standard way to give Android emulators hardware acceleration on Intel PCs. It installed as a driver, it grabbed Intel VT-x, and it made emulators fast. That era is over. Intel discontinued HAXM, and modern Windows versions, emulator releases, and Android development tools have moved on to two replacements: WHPX on Windows, and AEHD, the Android Emulator Hypervisor Driver, for cases where WHPX is not the right fit. If your emulator still references HAXM, or you are following an old tutorial that tells you to install it, this guide explains what changed, how to migrate cleanly, and how to fix the errors that appear when HAXM is missing or half-installed.

What HAXM Was, and Why It Ended

HAXM was a kernel driver that let an emulator use Intel’s virtualization hardware directly, bypassing the need for a full hypervisor. On Windows PCs without Hyper-V, it was the simplest path to fast emulation, and Android Studio bundled it for years. Intel eventually stopped maintaining it, as Microsoft’s hypervisor platform matured and as the Android emulator itself gained native support for running on top of Hyper-V. Continuing to rely on an unmaintained kernel driver on a modern, security-hardened Windows build is a poor idea: it may fail to install, it may conflict with Hyper-V and Memory Integrity, and it will not receive fixes for new Windows versions or new processors. The correct response is not to hunt for an old HAXM installer on a third-party site. Those downloads are often outdated, sometimes tampered with, and they solve a problem that no longer needs solving. Migrate instead.

The Two Replacements, Explained Simply

WHPX, the Windows Hypervisor Platform, is Microsoft’s interface for running third-party hypervisors on top of Hyper-V. When an Android emulator uses WHPX, it runs as a guest of Hyper-V rather than fighting it. This is now the recommended path on Windows 10 and Windows 11 for most users, especially those who also use WSL2 or Docker, because all of those tools share the same hypervisor layer. If your emulator supports WHPX, choose WHPX first.

AEHD, the Android Emulator Hypervisor Driver, is Google’s own hypervisor driver for Windows. It is the successor path for situations where WHPX is unavailable or unsuitable, and it is distributed through the Android SDK rather than as a standalone Intel product. In practice, most consumer emulator users will use WHPX and never need to think about AEHD directly, because their emulator handles the choice internally. Android Studio users, and users of emulators built on the Android Emulator core, may encounter AEHD as a selectable driver or as an SDK component. The important point is that both replacements are maintained, both are distributed through official channels, and neither requires you to download a discontinued Intel driver from an unofficial mirror.

Before You Migrate: Remove HAXM Cleanly

A half-removed HAXM installation is worse than a fully present one, because it can leave a driver service that blocks WHPX from claiming the hardware. If HAXM is currently installed, remove it properly before switching. Open Settings, Apps, Installed Apps, and uninstall Intel Hardware Accelerated Execution Manager if it appears there. Then open an administrator terminal and check for leftover driver state. If the emulator’s own documentation provides a HAXM removal step, follow that as well, because different emulators bundled HAXM in slightly different ways. Restart after uninstalling. Do not simply delete HAXM files from disk, because a driver registered with Windows needs a proper uninstall to deregister its service cleanly.

Next, confirm that virtualization is still enabled in BIOS. Removing HAXM does not change BIOS settings, but this is a good moment to verify, because the next steps will fail confusingly if VT-x or AMD-V is off. In Task Manager, Performance, CPU, confirm “Virtualization: Enabled”. If it says Disabled, reboot into BIOS and enable it, using the brand guide in this category if your menu labels are unclear.

Switching to WHPX: The Step-by-Step Path

First, update your emulator to the latest version from its official site. WHPX support arrived in different versions for different products, so an old installer may not offer it at all. After updating, open “Turn Windows features on or off” and check both Virtual Machine Platform and Windows Hypervisor Platform. You do not necessarily need full Hyper-V checked for WHPX emulation, but if you use WSL2, Docker, or Hyper-V virtual machines, check Hyper-V as well. Restart when prompted.

Now open the emulator’s settings and look for its engine or virtualization option. Enable the Hyper-V, WHPX, or Windows Hypervisor Platform mode, using whatever label your emulator uses. Some emulators detect WHPX automatically once the Windows features are on and show a confirmation message. Others require you to restart the emulator, or to create a new instance, before the new engine takes effect. Test with a fresh instance if you have any doubt, because an instance created under HAXM sometimes retains engine settings that prevent WHPX from engaging.

Test performance for at least ten minutes in a real game or app, not just on a home screen. Home screens are easy to render and hide performance problems. A busy game scene, with animation and input, is the honest test. Compare the result with what you remember from HAXM, and accept a small difference: WHPX performance is generally comparable on modern hardware, but on older dual-core machines it can be slightly slower, because the hypervisor layer adds overhead that HAXM’s direct approach avoided. If the difference is large, check RAM allocation and Memory Integrity before concluding that WHPX itself is at fault, because both have a bigger effect than the engine choice alone.

Switching to AEHD: When and How

AEHD matters most to Android Studio users and to emulators built directly on Google’s Android Emulator. In Android Studio, open the SDK Manager, go to SDK Tools, and look for Android Emulator Hypervisor Driver. Install or update it from there, and only from there. Do not download AEHD from unofficial sites. After installing, restart Android Studio and create or start an emulator device. Android Studio will use AEHD where appropriate and will report driver problems in its event log if something is wrong.

For consumer emulators, you will rarely install AEHD manually. If your emulator’s documentation specifically instructs you to use AEHD, follow its exact steps, because the emulator may bundle or invoke the driver in its own way. If the documentation does not mention AEHD, do not install it speculatively. Adding a second hypervisor driver when WHPX already works only creates a new source of conflicts.

Troubleshooting Migration Errors

The most common migration error is an emulator that refuses to start and reports that virtualization is unavailable, even though BIOS shows it enabled. This usually means Hyper-V features are in a half-enabled state, or an old HAXM service is still registered. Re-check Windows features, restart, confirm HAXM is uninstalled, and try again. A second common error is extreme slowness under WHPX. Check Memory Integrity first, then RAM allocation, then whether another virtualization product is also running. A third common error is an emulator that starts but crashes when a game loads. Try switching the graphics renderer between DirectX and OpenGL, and test a fresh instance, because renderer and instance corruption are more likely culprits than the hypervisor driver itself.

If you see an error message that still names HAXM explicitly, search your emulator’s settings and configuration for a legacy engine option and switch it to automatic or WHPX mode. Some emulators keep a HAXM reference in their settings long after HAXM itself is gone, and that stale reference produces a confusing error even on a correctly migrated PC.

What About AMD Processors?

HAXM was an Intel product, so AMD users never used it in the first place. AMD users historically used the Windows Hypervisor Platform or the emulator’s own AMD support, and nothing about the end of HAXM changes their path. If you are on AMD hardware and an old tutorial tells you to install HAXM, ignore that tutorial. Enable AMD-V in BIOS, enable Virtual Machine Platform and Windows Hypervisor Platform, and use a current emulator build. The migration described here is, for AMD users, simply a confirmation that the WHPX path they already use remains the correct one.

Keep Your Sources Official

This migration is a good moment to reinforce a habit that protects you far beyond emulator performance. Kernel drivers and hypervisor components have deep access to your PC. Installing them from unofficial mirrors, forum attachments, or repackaged installers is genuinely risky, and the end of HAXM has created a market for exactly those dubious downloads, promising to restore a discontinued driver. Do not use them. WHPX ships with Windows, AEHD ships with the Android SDK, and current emulators ship with WHPX support built in. Everything you need comes from Microsoft, Google, or your emulator developer’s official site, and nothing else is required.

FAQ

Is HAXM still available to download?

Intel discontinued HAXM, and it is no longer maintained or recommended. Do not install old copies from unofficial sites; migrate to WHPX or AEHD through official channels instead.

What should Windows users use instead of HAXM?

WHPX, the Windows Hypervisor Platform, is the recommended replacement for most Windows users. Enable Virtual Machine Platform and Windows Hypervisor Platform, and use a current emulator build in its Hyper-V or WHPX mode.

What is AEHD and do I need it?

AEHD is Google’s Android Emulator Hypervisor Driver, distributed through the Android SDK. Android Studio users may install it from the SDK Manager. Most consumer emulator users use WHPX and do not need to install AEHD manually.

Why is my emulator slower after switching from HAXM to WHPX?

WHPX adds a hypervisor layer that HAXM’s direct approach avoided, so a small slowdown on older hardware is possible. Check Memory Integrity and RAM allocation first, as both often matter more than the engine choice.

I uninstalled HAXM but my emulator still mentions it. What do I do?

Check the emulator’s engine settings for a legacy or manual HAXM option and switch it to automatic or WHPX mode, then test with a fresh instance if the error persists.

This guide does not host, link to, or distribute copyrighted ROMs, ISOs or BIOS files. It describes legal emulator configuration only, and readers should obtain Android apps and games only from official sources such as the Google Play Store or the emulator developer’s official site.

Leave a Comment