haxm | Intel® Hardware Accelerated Execution Manager | Infrastructure Automation library

I made it work...

Apparently, the Android Emulator updated to the latest version was the problem. Apparently many conflicts with vulkan.dll and other emulation process stopped working with this new version (at least for me in my computer).

I downloaded an old version of the android emulator based on this answer and then it started working again...

If you are developing on Mac M1chip, then that's probably the case it will not work.

If you don't use MAC then please try

1. Download directly from https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager

2. Go to this url and check the configuration https://github.com/intel/haxm/wiki/Windows-Installation-Environment-Check-and-Configurations

I have faced the same problem recently. It got solved when i updated the libraries. Try updating libraries and android studio.

Here is the link for the emulator revision 30.0.26 https://dl.google.com/android/repository/emulator-darwin-6885378.zip (taken from this answer)

Download it and then copy over the installed emulator.

It won't work if you have files quarantine enabled; I did so I needed to remove quarantine recursively from downloaded files

I am getting the same error as you. Nothing from the proposed solution worked. I've tried out all that you did. And so far, it seems that the only solution is to upgrade our Macs at least to Catalina... Or downgrade everything... which seems to be not the easiest way.

In macOS 10.15 Catalina, Apple has introduced a new framework to access USB devices in user mode, the IOUSBHost framework.

you can read more here:

• https://tejusadiga.wordpress.com/2020/06/06/time-to-farewell-kernel-extensions-kext-on-macos/
• https://developer.apple.com/documentation/iousbhost

hope this brings you some light too ;)

INTRODUCTION

First of all, I know that there are some posts out there. But there not up to date or incomplete. I want to point that my intention with this post is to make a nearly 100% working knowledge base for this issue. Serving as a step by step tutorial for fixing that problem properly.

Don't panic, we will fix that now :)

CHECK-1:

Check your BIOS Settings first. Virtualization Technology needs to be enabled in BIOS. Gigabyte, Asus Rog or MSI for example call that SVM Mode ("Secure Virtual Machine") other may call that as mentioned: "Virtualization"

F2/Del to access BIOS -> Advanced Settings -> CPU Configuration -> SVM Mode -> Enable, safe that with F10 (Asus BIOS Example)

As BIOS options are different among vendors, please refer to your system manufacturer's manual.

CHECK-2:

Type in your Windows searchbar (Lower left corner) "Windows Features". Make sure Hyper-V and Windows Hypervisor Platform are disabled. All Windows features enabling Hyper-V either explicitly or silently must be turned off. Restart your computer after. See the screenshots below for what you need to uncheck:

Note that in a future Studio 4.0 release, these instructions will be automatically run as part of the SDK Manager update and become obsolete.

CHECK-3:

To really ensure that Hyper-V is disabled run following command in Powershell. Open powershell: Right click on your Windows Logo (Lower left corner) -> click Windows Powershell (Administrator) -> proceed with following command:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

SETUP ANDROID STUDIO

We now want to install the missing Hypervisor Driver for AMD Processors: In Android Studio navigate File -> Settings -> expand Appearance & Behavior -> expand System Settings -> Android SDK -> SDK Tools -> install Android Emulator Hypervisor Driver for AMD Processors (installer) -> Apply -> OK

RUN THE INSTALLER

Now you downloaded the package of the driver you need to find it's location. In the image below you see the path of your Android SDK's.

Copy that path into your Explorer and navigate through like in image below to your silent_install.bat

Copy the complete path of your explorer and run Powershell as Administrator (how to open, explained above). In Powershell type:

cd [here your copied path]

Afterwards execute your installer by typing:

.\silent_install.bat

You will probably get an error, but that isn't important, because the installer worked. We will see it later. The service only couldn't start because one of our 3 CHECKS above are not done properly. Then it will look something like that:

We use this "worst case" to proof that the installer operated sucessfully even with the following errors.

[SC] DeleteService succeed. Fail of [SC] StartService error 4294967201

They may lead you to a github directory. To download a code there, but it isn't necessary at all. It worked already. Let's try it out.

PS: If everything went as it should it will look like that (Best case):

CREATING EMULATOR DEVICE

Let's create an android device and test it. I made it step by step as shown in the screenshots:

After you selected a device you are finally able to download the android version of the device:

Make your unique settings:

Run your device:

FINAL & CONCLUSION

Now you are able to work with the android studio emulator and an AMD Processor. Congratz! :) I know it was a long tutorial, but you made it trough. If you face any issues, comment below, I try to help you! That was it once again from my side. I keep this post updated.

so it seems even though intel HAXM shows as installed on SDK Tools, it wasnt really installed so i had to go to below location and manually reinstall (intelhaxm-android) file.

C:\Users\SUHAIL\AppData\Local\Android\Sdk\extras\intel\Hardware_Accelerated_Execution_Manager

if the file doesnt exist in that location, that means it wasnt downloaded and you will have to download the file online

So in the end I reinstalled Microsoft Visual C++ 2015, 2017 and 2019 redistributable (in x64 (I've mistakenly downloaded the x86 at first) and now it works

(https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0)

The reason it wouldn't start is because there was some write/read issue with the external storage, I've updated and gave the right needed and it works now