System info:
AMD Ryzen 5 2600X
PRIME X470-PRO Mobo
8gb ddr4 kingston hyperx
NVIDIA GeForce GTX 970 4GB
Windows 10 pro Version 10.0.17134 Build 17134
I would have preferred to add this as a comment to answers on this post, but I don't have 50 reputation.
I am stuck on step 2 of this answer.
I've tried disabling Hyper-V and Windows Hypervisor Platform, all virtualization options are enabled through BIOS, but HAXM refuses to install.
This comment indicates the exact opposite, and that does not work either.
This comment says AMD only works on Linux. But the linked documentation they point to does not mention this restriction. So it's possibly been patched.
EDIT:
just going to add random extra pieces of information that I find about my system to help answer questions that may come up.
Virtualization enable
My Windows features (and also with windows hypervisor platform enabled, still returns error after reboot)
I ran the following command before going into my windows features options, it appeared to do nothing however as Hyper-v was still showing as enabled in the GUI:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
Related
I know the question is not a new one , but I have tried all the solutions mentioned in other articles , which didn't work at all on my device. So I think there are something different .And here are the question and my computer configuration.
[SC] StartService: OpenService 失败 1060:
指定的服务未安装。
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
设备名称 LAPTOP-9D1HR6UR
处理器 AMD Ryzen 5 4600H with Radeon Graphics 3.00 GHz
机带 RAM 16.0 GB (15.4 GB 可用)
系统类型 64 位操作系统, 基于 x64 的处理器
I had that issue a while ago, just to check, do you have SVM enabled on your BIOS? I had that off for me, when I enabled it I was able to install the AMD Virtualisation Driver and it worked. You can quickly check by going into System Info, looking for Hyper-V and seeing if it is marked as "Yes".
I can't start android emulator and I don't why, because I tried all solutions found here and in other sites, but nothing.
I have a CPU AMD Ryzen 2600
MB ASrock B450 gaming k4
Android Studio 3.4.1
Bios MB 3.30 (last one)
SMV enabled
Windows 10 build 1903 18362.239
Hyper-v enabled
Windows Hyper-v Playform enabled
I tried also disable one feature but nothing changed, and the strange thing is that VirtualBox start without problem.
Can anyone help me?
I just update Visual Studio 2017 to version 15.8.0, the one that I've been waiting for a while now, due to its support for Hyper-V accelerated Android emulators using Windows Hypervisor Platform (WHPX).
I've been running Windows 10 version 1803 since May, and I have installed/enabled Windows Hypervisor Platform from "Turn Windows features on or off". Also, I have updated Android SDK and tools as it's described in https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration.
However, when I run any of the accelerated emulators, I get an error:
We've encountered an error with your Windows Hypervisor Platform (WHPX) configuration that is preventing us from running your emulator accelerated.
Please ensure WHPX is properly installed, then perform a factory reset on the emulator and try again.
No log and nothing else. Hence, I'm a bit confused and don't know what I should do next.
Appreciate any help.
P.S. Couple of clarifications:
I tried both, resetting existing emulators and creating new ones.
I run Hyper-V virtual machines and Docker containers on the same PC.
Maybe the Virtualisation is not enabled for your CPU from the BIOS menu. Boot to your BIOS and Enable Virtualisation. Also, install or reinstall these features on windows.
Running from VS2019 gives me the same WHPX error. But running manually works just fine with hardware acceleration (make sure you run powershell as administrator):
PS C:\Program Files (x86)\Android\android-sdk\emulator> .\emulator.exe -avd <avd_name> -feature WindowsHypervisorPlatform
I received this error even though I was already successfully running docker containers as well.
It turns out that I didn't have Windows Hypervisor Platform enabled in the "Turn Windows Features On and Off" menu. Once I turned it on, the error disappeared.
I had both Hyper-V options enabled but not Windows Hypervisor Platform. I guess that one is not required to run docker containers.
Work with visual studio 2019
I fixed this issue by disabling "Windows Hypervisor Platform" and only enable "Hyper-V" option.
It may be that your CPU does not support virtualization or some other software is preventing its use. If you have an Intel Processor Intel's VTx support page is an excellent resource to determine if your CPU permits virtualization and/or if some other software is preventing its use:
In summary:
Identify Your Intel CPU and View the Specs
Use the Intel Processor Identification Utility (https://www.intel.com/content/www/us/en/support/articles/000005495.html).
As the first link points out, even if the Intel tool in #2 shows VTx not supported, check TaskManager to see if Virtualization is enabled. If it is, then some other software is using Virtualization and preventing the tool (and other tools similar to it) from showing Virtualization as enabled.
Using both Intel's utility and TaskManager you can diagnose the problem per Intel's Table:
Virtualization Checked in Intel Utility + Virtualization Enabled in TaskManager -> enabled, usable
Virtualization Checked in Utility + Virtualization Disabled in TaskManager -> disabled in BIOS.
Virtualization Checked in Utility + Virtualization Enabled in TaskManager -> enabled but used by other software
Virtualization Checked in Utility + Virtualization Disabled in TaskManager -> Virtualization not supported .
I've seen many posts similar to my problem, and even though I tried to do the same steps, it still didn't work.
Intel Core i7 - 2670QM CPU # 2.20GHz Windows 10
I need to create an emulator for Android Studio in order to test my apps, but it doesnt work, it says that I need Intel HAXM.
Then I try to install and says (VT-x) is not enable (like in the picture below)
Error while installing HAXM
I've already tried:
(1) Check the BIOS (there is no option in my BIOS about VT-x virtualization, but I've check with the application "coreinfo" that says its actually working on my system.
(2) Disable Hyper-V on Windows (also, I couldn't find this option on "Windows Features" on Windows 10, but I've disabled everything that says Hyper-V in Windows "Services"
(3) I've checked about AVAST.
(4) I've updated my Windows
Thank you guys!!
I just don't get the fact that Windows doesnt show the Hyper-V option, and the BIOS doesnt give VT-x option also, but the Haxm_check says:
"VT support -- yes
NX support -- yes"
You don't mention what OS you're using. Have you tried downloading separate installer rather than install thru Android studio
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
also run the bcedit commands to make sure the CPU is enabled, not just capable
bcdedit /set hypervisorlaunchtype off
bcdedit /set nx AlwaysOn
your list shows hypervisor enabled. You should go into control panel>Programs>turn WINDOWS features on/off on the left side. Then whether it's on or off you should still see the HyperV checkbox. Make sure nothing is checked. If it's really off, you should be able to search for HyperV Manager and not find it.
I'm a new Android developer and learner, and I am actually facing some strange issue. (config : Intel Core i7 3630QM # 2.40GHz , 6go ram , windows 8.1)
Just like many, I encountered the HAXM issue when I tried the emulator on the AVD manager.
What I have done :
1. Download the package for intel accelerated HAXM virtualisation via my SDK manager
Figure out the sdk location on my pc, and click on install (manually on the app)
C:\Users\didier\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager)
2.1 I get this error,
My PC meets the requirements but...
This means that my HAXM virtulisation may not be enabled on my pc.
2.2 I checked that on my BIOS, enabled it , saved and exit.
3. I retry the install from the exe file in my sdk location.
- I get the same error message.
So I tried install from intel website : Software from intel Website link , ==> I get the same
error message
I download Speccy, a program that tells you what is on your PC, I found that on BIOS, the Virtualisation option that I enabled , was actually DISABLED.
So I rebooted, and check that, it was ENABLED.
So now, I don't know what to do, I have found some other solution to emulate, but it's quite slow, it uses ARM technology.
Here is a possible solution to your problem, what I've found from your information given is that:
Your processor supports HAXM, see this spec sheet.
The hardware requirements are:
Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality
At least 1 GB of available RAM
Referring to that list of possible solutions, you should try:
Double check if Execute Disable Bit, VT-x, VT-d are turned on in BIOS
Disable Hyper-V in Windows 8.1
There have been issues with Hyper-V tech conflicting with HAXM, refer to this SO question.
Create a separate boot entry that disables hyper-V completely, or just disable all of it by:
Press Start.
Type CMD.
Right-Click, select Run As Administrator (must do this even if on Admin account)
type this in bcdedit /set hypervisorlaunchtype off
Reboot. Hyper-V should be off now.
I had the same problem with a similar processor, core i3, in my VAIO laptop. VT was also enabled on the BIOS and the problem was fixed when I uninstalled the avast anti-virus(no disabling the protection) and so I could finish the HAMX installation. After that, I installed the Avast software again.
I hope this issue can help more people.
I had terrible trouble getting an Android Virtual Device to work on Android Studio. I thought I had done everything right but then I checked the Hewlett Packhard BIOS again and realised that the word Enable beside Virtualisation really meant Enable and not Enabled, which is VERY confusing. Switch to Disable (which seems to mean Enabled) and all should be good. Talk about double negatives!