[SC] StartService FAILED with error 4294967201 about android-emulator-hypervisor-driver-for-amd-processors HOT 8 OPEN

Hi there,

I had same issue before, and resolved after I checked the points in this wiki article and tried the steps discussed into #10.

from android-emulator-hypervisor-driver-for-amd-processors.

This reflects poorly on AMD. Next CPU won't be AMD.

from android-emulator-hypervisor-driver-for-amd-processors.

I encounter the problem of "start service failed with error 4294967201

from android-emulator-hypervisor-driver-for-amd-processors.

I am currently getting this same error on Windows 11

Android SDK is up to date.
Running Android Emulator Hypervisor Driver for AMD Processors installer
[SC] ControlService FAILED 1062:

The service has not been started.

[SC] DeleteService SUCCESS
[SC] StartService FAILED with error 4294967201.
Android Emulator Hypervisor Driver for AMD Processors installation failed. To install Android Emulator Hypervisor Driver for AMD Processors follow the instructions found at: https://github.com/google/android-emulator-hypervisor-driver-for-amd-processors
Done

from android-emulator-hypervisor-driver-for-amd-processors.

Is there a good reason why Hyper-V had to be disabled to get this working? I require Hyper-V for my work usage, and I can't be turning it on and off.

from android-emulator-hypervisor-driver-for-amd-processors.

I'm getting this issue too trying to setup an android emulator for flutter. Every AMD computer I've had has had several issues I do not recommend buying them. I suggest you get an Intel computer or Macbook if you want to avoid the unnecessary headache

from android-emulator-hypervisor-driver-for-amd-processors.

Is there a good reason why Hyper-V had to be disabled to get this working? I require Hyper-V for my work usage, and I can't be turning it on and off.

This is so absurd, but I forcefully disabled all the hyper-v features, including virtual machine, and then also disabled core isolation, rebooted, then finally was able to install the terrible AMD feature again from android studio, tested that an x86-64 AVD would start, then added all the hyper-v features back and rebooted, and I can still use this piece of junk AMD feature.

from android-emulator-hypervisor-driver-for-amd-processors.

I was able to re-enable core isolation as well, and ta-da, the AVD starts. What a piece of work.

from android-emulator-hypervisor-driver-for-amd-processors.