Error trying to install HAXM - Intel VT-x turned off

3
votes

I've Installed Android Studio, and I'am getting this error while I'm trying to install HAXM.

enter image description here

I tried to enable Virtualization in bios, but It didn't solve the problem. Then I disabled Hyper V in my Windows 8.1 (64 bits):

enter image description here

After restarting my computer, nothing changed, and I still can't install HAXM for the same reason. How can I solve this issue, assuming that I disabled Avast too, which basically covers all the solution I've found on stackoverflow.

4
androidandroid-studiovirtualizationhaxm
Hyper-V worked without virtualization in the bios? did you end up leaving the virtualization turned on or off after removing Hyper-V? (or check both cases)? aside from Hyper-V, any other virtualization software? (Virtualbox/etc.?) – user2813274
@user2813274 Actually Hyper-V is disabled, and virtualization enabled in bios. No I'm not using any other virtualization software. – TheByeByeMan
What laptop/desktop might this be, and what processor exactly? – matrixanomaly
@matrixanomaly : LENOVO G510 - 4th Generation Intel Core i7-4700MQ Processor (2.4 GHz 1600MHz 6MB) – TheByeByeMan
@Mfsob gave my answer, after checking out that specific model – matrixanomaly

4 Answers

3
votes

You mentioned that your processor was : Intel Core i7-4700MQ

I've done a quick search for it to determine that Intel HAXM works on your processor. It does.

You probably fulfill the software requirements for HAXM (Windows 8.1 is Supported, and an up to date Android SDK Manager.

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

(Taken from Installation Instructions)

Given the OS of your system and processor, here's a list of things that you could try in order.

  1. Check the Execute Disable Bit, VT-x, VT-d

I know this has been mentioned in other answers, but it be good to comb through all the settings again and make sure every virtualization option is properly turned on.

Within the BIOS setup utility, Execute Disable Bit may be identified by the terms "XD", "Execute Disable", "No Execute", or "Hardware DEP", depending on the BIOS used.

  1. Disable Hyper-V in Windows 8.1

This SO question mentions of a fix as other answers here have given, you need to disable Hyper-V due to known conflicts. You did show a screenshot of this being done, the fix does mention of a clean restart (not shutdown and turn on again due to the Fast Startup feature which is a hibernate of drivers).

  1. Alternative: Boot Entry that explicitly disables Hyper-V

    • 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

Instructions adapted from this blog post that mentions of how to create a separate boot entry. The blog post does touch on turning on Hyper-V after that too.

I personally had issues with HAXM because of the wrong BIOS settings. And perhaps some other virtualization software (I think VirtualBox, it was a while ago) was running. Good luck.

Edit: A user also mentioned here that completely uninstalling Avast helped. Not sure if that's the route you want to try.

2
votes

Run the command to make sure hyperV is off
bcdedit /set hypervisorlaunchtype off
and run this to make sure XD bit is on
bcdedit /set nx AlwaysOn
If you're using Avast, disable "Enable hardware-assisted virtualization" under: Settings > Troubleshooting. Restart the PC and try to run the HAXM installation again and if nothing is working, try reinstall using the installer from https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager

2
votes

Go to your bios settings and enable Virtualization (if ur device support virtualization)

1
votes

There are 2 parts to virtualization: virtualization of the cpu and IOMMU (memory remapping). In the Intel world, they are called VT-x and VT-d. These are usually two different settings in the BIOS. You may need to enable both for some of the features to work. Even though the actual text of error says that it needs VT-x, it may need VT-d (as well as VT-x). I have seen that happen.