Android Emulator HAXM / Hypervisor Error (VT-x, WHPX, AEHD)
Quick answer
Intel HAXM is no longer supported by the emulator. Enable Windows Hypervisor Platform (WHPX) on Windows, make sure virtualization is on in BIOS, and uninstall HAXM. AEHD is being sunset on December 31, 2026.
Most likely fix: Turn on virtualization in BIOS
How to fix it
Try these in order — the most common fix is first.
1. Turn on virtualization in BIOS
- Reboot and open BIOS/UEFI setup
- Enable Intel Virtualization Technology (VT-x) or AMD SVM Mode
- Save and boot into Windows
Did this fix it?2. Enable Windows Hypervisor Platform (recommended)
- Start menu > search 'Turn Windows features on or off'
- Tick Windows Hypervisor Platform and click OK
- Restart the computer
- Run emulator -accel-check and look for 'WHPX ... is installed and usable'
Did this fix it?3. Uninstall old HAXM
- In an admin command prompt run sc query intelhaxm to see if it exists
- In SDK Manager > SDK Tools untick Intel x86 Emulator Accelerator (HAXM installer) and apply, or remove it in Windows Settings > Apps > Installed apps
- If needed run sc stop intelhaxm then sc delete intelhaxm
Did this fix it?4. If you use AEHD
- Install via SDK Manager > SDK Tools > Android Emulator hypervisor driver
- Check with sc query aehd; STATE 4 RUNNING is good
- Google says AEHD sunsets on December 31, 2026, so plan the switch to WHPX
Did this fix it?5. Linux: set up KVM
- Run sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils
- Run sudo kvm-ok to confirm acceleration can be used
- Make sure your user can access /dev/kvm
Did this fix it?
Symptoms
Errors such as 'HAXM is not installed', 'VT-x is disabled in BIOS', 'x86 emulation currently requires hardware acceleration' or an AVD banner about a missing hypervisor.
Why it happens
- Virtualization (Intel VT-x or AMD SVM) disabled in BIOS or UEFI
- Intel HAXM removed from emulator 36.2 onward
- Windows Hypervisor Platform feature not turned on
- Hyper-V, Core Isolation or other tools conflicting with AEHD
- Running the emulator inside another virtual machine (not supported)
This guide also covers
- haxm not installed android studio
- vt-x is disabled in bios android studio
- android emulator requires hardware acceleration
- whpx android emulator
Still not working?
If Android Studio keeps failing, you're not alone. See every Android Studio problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
- IntelliJ IDEA JDK Not Found or Invalid (JetBrains IntelliJ)
- Cursor High Load Error (ERROR_RESOURCE_EXHAUSTED) (Cursor)
Other Android Studio errors
- Android Studio Gradle Sync Failed
- Android Studio Emulator Not Starting
- Android Studio Emulator Slow or Laggy
- Android Studio Device Offline or Not Detected (ADB)
- Android Studio Slow and Using Too Much RAM
- Android Studio Gradle Build Slow
- Android Studio SDK Location Not Found
- Android Studio Build Failed: JDK, Gradle or AGP Version Mismatch