android emulator WHPX: Failed to emulate MMIO access , exit code 3

Question

I had Android Studio with AMD TR 2950x android emulator was working perfectly then suddenly it start to give me this error with this messages :

10:30 AM Emulator: qemu-system-x86_64.exe: WHPX: Failed to emulate MMIO access with EmulatorReturnStatus: 2 (InternalEmulationFailure )

10:30 AM Emulator: qemu-system-x86_64.exe: whpx_vcpu { emulator=000000000ec95f70, window_registered=false, interruptable=true, tpr=0, apic_base=fee00900, interruption_pending=false }

10:30 AM Emulator: qemu-system-x86_64.exe: WHV_MEMORY_ACCESS_CONTEXT { Instruction={ size=16, bytes='A1 F0 00 E0 FE 80 CC 01 A3 F0 00 E0 FE C7 05 50 ' }, AccessInfo={ AccessType=0, GpaUnmapped=1, GvaValid=0, AsUINT32=4 }, Gpa=fee000f0, Gva=0 }

10:30 AM Emulator: qemu-system-x86_64.exe: WHPX: Failed to exec a virtual processor

10:30 AM Emulator: Warning: QObject::~QObject: Timers cannot be stopped from another thread ((null):0, (null))

10:30 AM Emulator: Process finished with

Answer 1

Update Windows to insder preview build 10.0.18890

https://developercommunity.visualstudio.com/content/problem/528337/whpx-problem-android-emulator.html

Answer 2

For a solution without having to join the Windows Insider Program and update to the Windows Insider Preview you can install KB4545903 directly (which is the only KB downloaded and installed by joining the release preview) which should fix the emulator issue on AMD.

Assuming you're running 64bit system, download the CAB file here .

Then install it with an elevated command prompt:

DISM /Online /Add-Package /PackagePath:”Full path of .cab file”

After a restart, you should be good to go.

Props to this medium post for the answer.

Answer 3

I've got the same error. To avoid the upgrade to the insider preview build, I did the following steps:

1. Create a new virtual device
2. Select a device
3. select a system image and go to other images screenshot
4. Select an ARM based image (I've choosen the arm64-v8a API level 24)
5. Follow the next instructions and finish the setup

Now you can launch the emulator, but the emulator is VERY SLOW . It took about 8 minutes to go online and make it usable!

So this solution is just a quick fix, if you need to test the basics of your app. I hope, Microsoft will fix the bug and make it possible to use the HAXM/Co. again.

Hopefully this works for you as well! :)