Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

The Android Emulator will not start with hardware acceleration (HAXM, Hyper-V, KVM)

ErrorSTATE : 1 STOPPED, WIN32_EXIT_CODE : 4294967201 (0xffffffa1)

Short answer

Intel HAXM is discontinued, and current emulators no longer use it. On Windows, switch on Windows Hypervisor Platform. On Linux, install KVM and check your user may use it. On any system run emulator -accel-check to see which hypervisor the emulator found. If the window dies, try -gpu software.

  • Applies to Android Emulator 36.x, Android Studio current stable, Windows 11, Ubuntu 24.04, macOS 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Ask the emulator which hypervisor it can use. Run it from the emulator folder inside your SDK.

    # macOS / Linux
    "$ANDROID_HOME/emulator/emulator" -accel-check
    # Windows (cmd)
    %LOCALAPPDATA%\Android\Sdk\emulator\emulator -accel-check
  2. 2Match what you see, then jump to its fix

    1. 1the HAXM installer fails, or sc query intelhaxm shows the service, and the emulator is version 36.2 or newerHAXM is used or installed, but it is discontinuedFix
    2. 2-accel-check reports no hypervisor, or sc query aehd shows STATE 1 STOPPED with WIN32_EXIT_CODE 4294967201 (0xffffffa1)Virtualization is off in BIOS, or Hyper-V blocks the driverFix
    3. 3-accel-check or the emulator says KVM is not installed or cannot be openedKVM is missing, or your Linux user cannot use itFix
    4. 4The emulator starts and then disappears, or shows corrupt images; the VM check passesGraphics acceleration crashes the emulator windowFix

What does the error look like?

  • STATE : 1 STOPPED, WIN32_EXIT_CODE : 4294967201 (0xffffffa1)
  • KVM acceleration can NOT be used

Cause 1 of 4

HAXM is used or installed, but it is discontinued

1Check

Intel stopped developing HAXM, and the Android Emulator does not use it from version 36.2 on. Check whether the service exists on Windows.

sc query intelhaxm

2Fix

Remove HAXM, then turn on Windows Hypervisor Platform. Open Turn Windows features on or off, tick Windows Hypervisor Platform, click OK and restart. To remove HAXM, clear it in SDK Manager, SDK Tools, or stop and delete the service from an administrator prompt.

sc stop intelhaxm
sc delete intelhaxm

3Verify

After the restart, -accel-check says WHPX is installed and usable.

emulator -accel-check

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 4

Virtualization is off in BIOS, or Hyper-V blocks the driver

1Check

Virtualization extensions are often disabled by default in the BIOS. If you use the Android Emulator hypervisor driver (AEHD), Hyper-V and some security features such as Core Isolation also keep it from running.

sc query aehd

2Fix

Enable virtualization (Intel VT-x or AMD SVM) in BIOS. Better, use Windows Hypervisor Platform, which coexists with Hyper-V; the AEHD driver will be sunset on 31 December 2026.

# Windows Hypervisor Platform route
# Turn Windows features on or off > Windows Hypervisor Platform > OK > restart

3Verify

Run the emulator check again.

emulator -accel-check

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 4

KVM is missing, or your Linux user cannot use it

1Check

Check that the CPU has virtualization support and that kvm-ok reports acceleration can be used.

egrep -c '(vmx|svm)' /proc/cpuinfo
sudo apt-get install cpu-checker
sudo kvm-ok

2Fix

Install the KVM packages, then give your user the permissions the KVM install guide describes (membership of the kvm group), and sign in again.

sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils

3Verify

kvm-ok prints KVM acceleration can be used, and -accel-check reports KVM.

sudo kvm-ok
"$ANDROID_HOME/emulator/emulator" -accel-check

Confirmed by developer.android.com

Did this fix it?

Cause 4 of 4

Graphics acceleration crashes the emulator window

1Check

The graphics setting is separate from VM acceleration. The emulator can choose it automatically, and a mode your driver does not support causes crashes or wrong images.

"$ANDROID_HOME/emulator/emulator" -list-avds

2Fix

Start the AVD with software rendering, or set Graphics acceleration to Software in Device Manager, Edit AVD, Emulated Performance. Update the graphics driver for a lasting fix.

"$ANDROID_HOME/emulator/emulator" -avd Pixel_8_API_35 -gpu software

3Verify

The emulator stays open and boots Android.

adb devices

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Run the emulator on the host machine; a VM-accelerated emulator cannot run inside another VM such as VirtualBox, VMware or Docker.
  • Do not run other virtualization software at the same time as the emulator if they conflict.
  • Keep the Android Emulator updated in SDK Manager, since hypervisor support changes between versions.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

adb tcpip 5555 fails because no device is found

adb: more than one device/emulator

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.