Android Emulator Hypervisor Driver Not Installed | Fix

Guide / By

android emulator hypervisor driver not installed means no VM acceleration; install AEHD or enable WHPX, restart, then verify.

That banner shows up when the emulator can’t use hardware-assisted virtualization on your PC. Without that layer, an x86 or x86_64 AVD boots slowly, drops frames, or fails to start. It’s common on Windows.

The fix is not a guessing game. This error comes from a short set of switches and components: firmware virtualization, a Windows hypervisor path, and the right Android SDK tools.

What This Error Means On A Real Machine

The Android Emulator runs a virtual device. To run it at a usable speed, the emulator needs access to your CPU’s virtualization extensions. On Windows, that acceleration can come from Windows Hypervisor Platform (WHPX) or from Google’s Android Emulator Hypervisor Driver (AEHD). Both paths are documented in the official emulator acceleration guide, along with the checks that confirm each one is active.

If neither path is active, the emulator falls back to a slow mode. You might still see a window appear, then watch it take minutes to reach the lock screen. In other cases, Android Studio blocks the AVD with a warning because the system image expects acceleration.

What You See Most Common Cause What To Do Next
Error shows up after an update SDK tool downloaded but driver not installed Install AEHD from SDK Manager, then restart
Emulator boots, then crawls Virtualization off in BIOS or blocked by another hypervisor Enable SVM or VT-x, then use WHPX or AEHD
Install fails and mentions Hyper-V Hyper-V stack still active Disable Hyper-V for AEHD, or keep it and use WHPX

Hypervisor Driver Missing In Android Emulator On Windows

Start by choosing the acceleration path that fits your setup. If you rely on WSL2, Docker Desktop, Windows Sandbox, or Windows VM features, WHPX is often the clean path. If you want Hyper-V fully off, AEHD is often the better fit.

Both paths still depend on firmware virtualization being enabled. If SVM or VT-x is off, WHPX can’t do its job and AEHD can’t start its service.

Choose The Path With A Simple Decision Tree

  • Pick WHPX — You want Windows virtualization features available for other tools, and you don’t mind keeping Hyper-V related features on.
  • Pick AEHD — You want the emulator accelerated while Hyper-V stays off, and you can restart after toggling Windows features.
  • Pick ARM Images — If you can’t enable virtualization on your machine, switch the AVD to an ARM system image and accept slower startup and lower speed.

Windows Checks That Decide The Outcome

These checks take minutes and stop you from reinstalling tools that are already fine. The goal is to confirm three layers: firmware virtualization, Windows features, and the Android SDK pieces that talk to the hypervisor.

Confirm Virtualization In Firmware

Restart your PC and enter BIOS or UEFI settings. Vendors label the option in different ways, so scan for SVM, AMD-V, Intel VT-x, or Virtualization Technology. Turn it on, save changes, then boot back into Windows.

If you want a quick Windows-side hint before rebooting, open Task Manager, go to the Performance tab, then select CPU. Look for the Virtualization field. If it says Disabled, the emulator will keep reporting missing acceleration until you enable it in firmware.

Enable Windows Hypervisor Platform For WHPX

  1. Open Windows Features — Open Start, type “Windows features”, then open Turn Windows features on or off.
  2. Tick WHPX — Select Windows Hypervisor Platform, then click OK.
  3. Restart Windows — A restart is required for the feature to load and become visible to the emulator.

After reboot, Android Studio can use WHPX without any extra driver installs. Google lists WHPX requirements, including Windows 10 or newer and a compatible emulator version.

Update The Android SDK Tools First

  1. Open SDK Manager — In Android Studio, choose Tools, then SDK Manager.
  2. Go To SDK Tools — Switch to the SDK Tools tab.
  3. Update Emulator Tools — Tick Android Emulator and Android SDK Platform-Tools, then apply updates.

If the emulator binaries are old, Android Studio can show stale messages. Updating first keeps you from chasing a ghost.

Android Emulator Hypervisor Driver Not Installed

If you choose AEHD, install it from the SDK Manager and confirm the Windows service is running. Android’s official acceleration guide also states that AEHD is planned to sunset on December 31, 2026, and it points Windows users toward WHPX as the long-term path.

AEHD works as a Windows driver with a matching Windows service. Newer releases use the service name aehd. Older releases used gvm. The official docs list both service names and the command you can use to check each one.

Install AEHD From Android Studio

  1. Open SDK Manager — In Android Studio, go to Tools, then SDK Manager.
  2. Choose SDK Tools — Click the SDK Tools tab.
  3. Select The Driver — Tick Android Emulator hypervisor driver, then apply changes.
  4. Run As Admin If Needed — If installation fails, rerun Android Studio as Administrator and try again.
  5. Restart Windows — The driver won’t load until after a restart.

Install AEHD Manually When Android Studio Only Downloads It

On some setups, Android Studio downloads the package but doesn’t install the driver. The official docs describe a manual path using the driver package and a batch installer. If you downloaded the driver from the AEHD repository, unzip it, open an admin Command Prompt, then run the installer script.

  1. Unzip The Driver Package — Extract the AEHD release files to a folder you can access.
  2. Open Admin Command Prompt — Search for Command Prompt, right-click, then run as Administrator.
  3. Run Silent Install — Execute the provided script from that folder.
silent_install.bat

Verify AEHD Is Running

After reboot, check the service status. A working setup reports STATE as RUNNING in the service output.

sc query aehd

If you see the service in a STOPPED state with an exit code that points to missing virtualization or a Hyper-V conflict, go back to firmware settings and Windows feature toggles. The official docs call out this pattern and the two root causes.

If your PC has an older driver package, run this command instead.

sc query gvm

When you want to remove the driver, the official docs list an uninstall path that stops and deletes the service.

sc stop aehd
sc delete aehd

Common Blocks That Keep Acceleration From Working

This is where most people get stuck. The driver may install cleanly, then refuse to run. The common causes are a Hyper-V stack still present, third-party VM tools holding virtualization extensions, or virtualization-based security features that conflict with your chosen path.

Hyper-V And Related Windows Features

AEHD needs Hyper-V off. WHPX needs Windows Hypervisor Platform on. Those goals clash, so set Windows up for the path you chose.

  • Disable Hyper-V Stack For AEHD — In Windows Features, untick Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Windows Sandbox, then restart.
  • Keep Hyper-V Stack For WHPX — Leave virtualization features as they are, confirm Windows Hypervisor Platform is ticked, then restart.

Some PCs still load the hypervisor after toggling features. If AEHD keeps complaining that Hyper-V is enabled, set the hypervisor launch type to off, restart, then recheck the AEHD service.

bcdedit /set hypervisorlaunchtype off

WSL2 And Docker Desktop

WSL2 and Docker Desktop are tied to Windows virtualization features. If you need them, use WHPX for the emulator. If you need AEHD, expect WSL2 and Docker Desktop to stop working until you re-enable the Hyper-V stack.

VirtualBox, VMware, And Similar Tools

Some VM tools can reserve virtualization extensions, or run with their own hypervisor layer. Close them before you test AEHD. If you need them active all day, WHPX tends to coexist better on Windows 11.

Virtualization-Based Security

Windows can run security features that rely on virtualization. If you see repeated conflicts, check core isolation and memory integrity settings in Windows Security, then restart after any change. Treat this as a switch: change one thing, restart, retest.

Prove The Fix With Quick Checks In Android Studio

Once you’ve set up WHPX or AEHD, verify it before you blame your project or your AVD. These checks give direct signals from the emulator tooling.

Run The Emulator Acceleration Check

  1. Open A Terminal — Use the terminal in Android Studio or a Windows terminal.
  2. Go To Emulator Folder — Change into your SDK’s emulator directory.
  3. Run The Check — Use the emulator binary to report acceleration status.
emulator -accel-check

The command-line docs for the emulator list this flag and what it checks. If acceleration is active, the output tells you which path is in use.

Cold Boot Once To Clear Snapshot Confusion

Snapshots can hide earlier failures. If you’re chasing a stubborn case, start the AVD with a cold boot, then watch the log lines that mention WHPX, AEHD, or HAXM status.

  • Cold Boot The AVD — In Device Manager, open the AVD menu and choose Cold Boot Now.
  • Wipe Data When Stuck — Only do this when you can lose the emulator’s local state.

Match The System Image To Your Machine

On Intel and AMD Windows PCs, x86_64 images are the common choice when acceleration works. If you’re on a machine with virtualization locked down, ARM images can still run without the same acceleration path, but they can feel slow. If you switch image types, rerun the accel check so you don’t misread normal ARM slowness as a broken driver.

Keep The Emulator Stable After You Unblock It

Most repeat failures come from one of three events: a Windows feature change, a firmware reset, or an Android Studio update that changes emulator bits. A few habits keep you from seeing the banner again.

  • Restart After Feature Changes — Windows caches hypervisor state across sessions, so restarts matter.
  • Keep Tools In Sync — Update Android Studio, Android Emulator, and platform-tools together.
  • Stick To One Path — Switching between WHPX and AEHD can reintroduce conflicts.
  • Check Free Disk Space — Low free space can break snapshots and make boot time look like a hypervisor issue.
  • Recheck After BIOS Updates — BIOS updates can reset SVM or VT-x back to Disabled.

If you still see the same banner after these steps, go back to official docs and compare your setup to their check commands and prerequisites. These pages include service checks, uninstall commands, and the AEHD sunset date.

Android Emulator Acceleration Docs
Emulator Command-Line Reference
AEHD Driver Repository
Microsoft Guide To Emulator Acceleration

After you fix it once, write down the path you chose and the one command that proves it. Next time you reinstall Android Studio, you can confirm acceleration in seconds.

android emulator hypervisor driver not installed can pop up again after you toggle Windows features or switch AVD images. If it returns, rerun the same checks before you reinstall anything.