Android Emulator fails with “/dev/kvm” missing due to errors installing Intel HAXM on Windows with Driver Signature Enforcement and Safe Boot (tested up to Windows 10 14367)

Intel HAXM for Android Emulator won’t work initially on some Windows (including Windows 10 1511 and 14367) versions.

Usually, HAXM installation will fail with the message that Intel HAXM driver cannot be configured. Even if you manage to install the driver, it may not work and Android Studio could incorrectly report /dev/kvm not present or VT-x not supported, although being enabled in UEFI.

The solution of manually installing HAXM using Intel provided installer won’t help in certain situations, and a workaround patch won’t help either.

One of the situations that can’t be resolved using aforementioned guides and tools is when Windows Driver Signature Enforcement prevents HAXM driver from working correctly.

If, following installation, the sc query intelhaxm command (requires elevated command prompt) returns that intelhaxm state is STOPPED, that confirms the problem. To resolve it, you’ll need to disable the WDSE feature (Windows 10 -> Advanced Boot Options, #7).

If you need it permanently disabled, you’ll need to first disable Safe Boot in UEFI and then disable the feature using

bcdedit.exe /set nointegritychecks on

After a reboot, your HAXM supported emulator should be fully functional with no further action required.

Leave a Reply