This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 878
Known Issues
Huang, Jun edited this page Nov 19, 2018
·
5 revisions
- HAXM driver does not support emulating a 64-bit system image on Intel systems based on Core microarchitecture (Core, Core 2 Duo etc.). All systems based on Nehalem and beyond are supported (Core i3, Core i5 and Core i7 machines).
- If DriverVerifier is running on a Windows System on which HAXM is installed, BSOD can happen during HAXM uninstall. Check the following link for more information from Microsoft. http://msdn.microsoft.com/en-us/library/windows/hardware/ff545448(v=vs.85).aspx
- On Windows platform using
sc querycommand on command line, will show the driver to be in Running state even if VT is disabled in BIOS. The Android SDK gets this information from HAXM driver whether VT is enabled or not and displays it to user when the user starts to emulate a device. The information in the SDK is the most accurate information for the state of the HAXM driver. - On Windows 8, 8.1 and 10, it is recommended to disable Hyper-V from Windows Features in order for the HAXM driver to properly function.
- On Windows, Avast Antivirus may interfere with HAXM and cause Android Emulator or QEMU to run very slowly. A workaround is to uncheck "Use nested virtualization where available" in Avast Settings > Troubleshooting.
- On some Windows 10 systems where Intel SGX is enabled, especially laptops equipped with an 8th-generation Intel Core CPU and a Goodix fingerprint sensor, running HAXM-based virtual machines (e.g. Android Emulator) may result in a BSOD (#68). This issue is fixed as of HAXM 7.3.0.