Error during installing HAXM, VT-X not working

Question

I am an entry-level Android software developer. I recently heard about HAXM that support emulator in rendering graphics more smoothly. I downloaded appropriate file HAXM file for Windows 7 64 bit, unpacked and started installing. However, during the installation process I get this error:

"This computer meets requirements for HAXM, but VT-x is not turned on..."

I checked many forum about this problem, including checking the version of BIOS and enabling Virtual Technology on BIOS. I followed the steps posted in the following forum:

Intel HAXM installation error - This computer does not support Intel Virtualization Technology (VT-x)

However, I don't have any lines about Hyperlaunch and I could not find Hyper-V options in my Windows features. I don't have any idea how to solve this problem.

Answer 1

Uninstall any antivirus (Avast, in my case), reboot the system and try install the Intel HAXM again. It works for me.

Answer 2

I had the same issues on my notebook which runs Windows 8.1

Try this:

• Check if Hyper-V options in "Windows Features activate or deactivate" are deactivated
• Download and install the latest Oracle VirtualBox
• Reboot
• Install HAXM
• Reboot-->open BIOS--> Enable 'Execute Disable'

It looks like that the installation of VirtualBox sets a flag that "turns" VT-X on.

Answer 3

Did you get a message about enabling the Execute Disable bit?

You can enable the XD bit by running the following command (as administrator) and then reboot.

bcdedit /set nx AlwaysOn

Usually, this error: "This computer meets requirements for HAXM, but VT-x is not turned on" means that your system does have Intel VT, but you need to go into the BIOS to actually enable it.

I also ran into these instructions -might be helpful to you: http://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows

Did you ever get it to work?

Answer 4

If you are still having issues, try running these steps from VMware to disable credential guard. Worked for me, finally. Steps and link are posted below, not taking credit for them.

Original content from https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146361

To disable Device Guard or Credential Guard on Itanium based computers:

1. Disable the group policy setting that was used to enable Credential Guard.

   On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.

   Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.

   Select Disabled.

2. Go to Control Panel > Programs and Features > Turn Windows features on or off to turn off Hyper-V. [ remove a program on Windows 8 or earlier]

3. Select Do not restart.

4. Delete the related EFI variables by launching a command prompt on the host machine using an Administrator account and run these commands:

   enter code here

   mountvol X: /s

   copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y

   bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader

   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"

   bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}

   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS

   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:

   mountvol X: /d

Note: Ensure X is an unused drive, else change to another drive.

5. Restart the host.

6. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.

You should be able to install and start HAXM now

Answer 5

Some manufacturers lock out the bios menu so that you can't turn VT on if this is the case there is another way to turn it on using a program called CPUID. Check out this video if this is your problem: https://www.youtube.com/watch?v=YPjTFam30kc

Answer 6

I really hated this awful problem after upgrading Windows 10 Anniversary Update (version 1607). It's just about Driver Signing Changes in Windows 10. If you force install HAXM, you have to disable Driver Signature Enforcement too.

1. Restart W10 in Safe Mode.
2. Enter Troubleshoot.
3. Advanced options>Startup Settings.
4. Choose "Disable driver signature enforcement"
5. When Windows 10 loaded, install HAXM latest version.