I am trying to get an emulator working on a new clean Windows 10 install. I'm stuck on a HAXM, AEHD, Hyper-V, AVD loop of death. I'm installing Android Studio on a decent and modern machine with core i5 4430, 4th generation.
Intel Virtualization is enabled on Bios. HAXM is deprecated since emulator v33, so I'm not installing it. Instead I installed AEHD as the docs says and Hyper-V is already disabled in all his names. It happens in a i7 4771 and i7 6700 with clean Windows installations, simply following steps to install Android Studio on Google guides.
The issue is that when trying to start the emulator, it displays this error: "intel haxm is required to run this avd haxm is not installed". And if I try to install a new AVD, when selecting system image, it says the same: "HAXM IS NOT INSTALLED" in red.
So I'm stuck and can't use AVD. I'm using the last version of Android Studio and SDK tools, emulator, etc.
Supposed steps to configure Hardware Acceleration on emulator:
https://developer.android.com/studio/run/emulator-acceleration
Before you can install and use Intel HAXM, your computer must meet the following requirements:
Intel processor with Virtualization Technology (VT-x), Intel EM64T (Intel 64) features, and Execute Disable (XD) Bit functionality enabled
32-bit version of the operating system on a 64-bit processor) On Windows 11, Windows 10 or Windows 8, you must turn off Hyper-V in the Windows Features Dialog.
On Windows 11, Windows 10 or Windows 8, you must turn off Hyper-V in the Windows Features Dialog.
Take attention to the last point: On Windows 11, Windows 10 or Windows 8, you must turn off Hyper-V in the Windows Features Dialog.
The error disappeared doing exactly what Google is telling you not to do. If you install AEHD and turn on Hyper-V, the error dissapears and the hardware acceleration is active again, with HAXM uninstalled and api 33 emulator.
Google says this:
https://developer.android.com/studio/run/emulator-acceleration
On Windows 11, Windows 10 or Windows 8, you must turn off Hyper-V in the Windows Features Dialog.
If you do exactly the reverse, If you turn on Hyper-V (Hyper-V, Hypervisor platform), suddenly the error disappeared and emulators work correctly with hardware acceleration
This problem was solved using this method in various computers with Windows 10 or 11 with clean installations. It works.
Maybe there is an error on Google documentation.