Android SDK's Intel HAXM disabled after installing Hyper V

Question

I\'m developing a suite of mobile apps - specifically Windows Store/Mobile 8 and Android.

Having installed VS2012 and then Monodroid, I was then able to start x86 An

Answer 1

I was in your same case that needed to support Hyper-V and Intel HAXM. Disabling and enabling the feature and then restarting was overkill so I found an alternative solution.

You can create 2 boot entries, one for Windows with the regular configuration of Hyper-V enabled and another one with Hyper-V disabled. I logged in with the second one (Hyper-V disabled) and I was able to install Intel HAXM.

To accomplish this you need:

1. Open a command prompt as Administrator
2. Enter the command: bcdedit /copy {current} /d "Windows 8 - No Hyper-V"
3. This will output an id with the format {GUID} that you need to copy it to use it in the next command.
4. Enter the command: bcdedit /set { copied GUID of step 3 } hypervisorlaunchtype off

More details in this post.

Answer 2

I had the same problem. After a long search I found the answer. In my case, I had installed Avast Antivirus, first uninstall avast, reboot your PC, install Haxm, reboot. you can install again antivirus.

Answer 3

The best thing you can do to get HAXM detect VT again, is turning the whole Hyper-V "Feature" off. Open "Control Panel -> "Programs" -> "Turn Windows features on or off" (under "Programs and Features") and locate "Hyper-V", uncheck, reboot.

Looks like Hyper-V and HAXM are mutually exclusive, which is kind of a nuisance, because you even need to reboot twice to enable or disable either feature.

Answer 4

You could try stopping the Hyper-V service when not needed and re-enabling it when you want to work on a WP8 project. It's a pain but the performance improvement offered by HAXM is immense.

Open services.msc, find the hvboot service (Hyper-V) and stop it. If this doesn't help you may need to disable the service and restart your pc.

Answer 5

I had a similar problem installing HAXM on Windows 8. I did the following with no effect:

• Disabled hypervisor using the instructions here (http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx)
• Double checked that processor supported VT-x and was enabled in BIOS (BIOS said "supported", but there was no option to turn it on
• Verified that all Hyper-V services in control panel were stopped (and never automatically started)
• Performed a complete shutdown and a cold boot up.

However, I tried installing VirtualBox after the above actions (VirtualBox installed fine) and created a new VM. Running the VM caused my machine to blue screen, but after the reboot HAXM installed fine. Perhaps running VirtualBox flips some sort of flag at the OS level to allow HAXM to install.

I was also running AVAST at that time, and according this (Running the new Intel emulator for Android), that may cause a problem. However, I didn't have to disable AVAST to get HAXM installed.