-
Notifications
You must be signed in to change notification settings - Fork 253
StartService FAILED with error 4294967201 #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for these detailed information. This error code means the driver cannot gain access to CPU's virtualization extension. |
I solved this problem by change SDK platform from 9.0 to 10. A little bit weird but it works. That's why I closed this issue. Thanks for your help |
Glad that the problem is gone. But it is weird since this should have no relation with SDK platform. |
Yes, I think the same. Really weird, but worth it to try since I was so exhausted when got this problem for around 3 days alone. I disabled my antivirus before, no work at all |
OK. Another thing that is good to have a try is installing vbox and see if it can work with HW virtualization. Technically, the same thing that blocks this driver should also block vbox. However, vbox supports running with SW virtualization. So it will need to create a dummy VM and check its setting page. If you have problems in future, we can always chat here in github. |
I am encountering a similar problem today, as the Android Emulator Hypervisor Driver for AMD Processors is failing to install with the same error code. Any help to resolve the issue is appreciated I am using Ryzen 3 3200G |
Any screenshots to help me diagnose? |
Hello Shan, Thanks for offering the help. I was trying too many options and I believe a power shell script for (Hyper-V) resolved the issue. |
got this too . is it for having docker opened ? |
Got the same issue. New Ryzen 5 5600x. |
I have same issue "StartService FAILED with error 4294967201." Using Ryzen 3700X The description for Event ID 7000 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Android Emulator Hypervisor Driver for AMD Processors Service The resource loader failed to find MUI file |
help pls!! |
Be sure to check your BIOS. On my computer Windows said virtualization was enabled even when it wasn't. I've opened pull request #49 to point this out in the README. |
yes i am facing same issue after disabled hyper-v and memory integrity from windows security.can't install driver for amd |
Same issue but emulator is working fine and smooth. |
In windows 11, hyper-v is inactive looking at windows features, yet system info showed "a hypervisor has been detected". disabling the 'Virtual Machine Platform' fixes this but kills wsl2. |
I'm facing the same issue on windows 11. It's either wsl2 or android emulator! But I need both! |
AMD Ryzen 7 4800H faces the same issue. I disabled Hyper-V and enable the virtualization, closed anti-virus, but it still did not work. |
I solved the problem by downloading a game-play emulator that allows users to play mobile games on the computer. |
my virtualbox doesnt have any problems running vms yet I get this error from this amd driver :( |
Go to BIOS -> enable virtualization, it should work then |
I have it enabled, but still same problem |
This seems to be a limitation of either (or both) Android Emulator and Windows 10/11 virtualization. I ran into this same issue with other Hyper-V-based software while using WSL2. It's either lose WSL2 or don't use another virtualized solution like Android Emulator (or a lot of AMD-based Ryzen software). There was a registry hack that allowed for the Ryzen Master software to be installed while keeping Hyper-V and WSL, but I will have to investigate. |
AMD Ryzen 7 4700U
Hyper-V disabled already.
I got this error log when I tried to install it using cmd (run as admin already). Android studio showed the same error message
The text was updated successfully, but these errors were encountered: