Pop Feed Daily

Home / updates

How to enable VMX?

Chloe Ramirez |

I want to install Intel HAXM 7.6.5. If I do this the setup aborts with this error:

The system requirements are not satisfied

In the background you can see the checktool.exe. This is the output:

checktool.exe --verbose
CPU vendor * GenuineIntel
Intel64 supported * Yes
VMX supported * Yes
VMX enabled - No
EPT supported * Yes
NX supported * Yes
NX enabled * Yes
Hyper-V disabled * Yes
OS version * Windows 10.0.18362
OS architecture * x86_64
Guest unoccupied * Yes. 0 guest(s)

I don't know what the requirements for HAXM are, but it seems that VMX is not enabled. How do I enable it?

Edit:

I checked the system requirements and they are met (Intel Core i7-8700 with Windows 1903). Now I enabled in the BIOS the following settings:

  • Intel(r) Virtualization Technology
  • VT-d
  • TxT

Through this I was able to install HAXM without problems. Don't know why but I would say I tried that before. Perhaps I missed TxT ... Thanks Ramhound.

3

2 Answers

I think it's not enough to just enable VT in the BIOS and disable Hyper-V in windows. You also need to disable Hyper-V in the BIOS. The setup misleadingly lets you think it failed because for some other reason, and that its ok with the fact that "Hyper-V-Disabled: No". What it really wants is "Hyper-V-Disabled: Yes" and not just in the OS, also in the BIOS.

Actually, after alot of twiddling, I just got it to work. Use the Windows Search box to find "Turn Windows Features On or Off"

Within it there are several features (Windows 11) relating to virtualization:

  • Guarded Host
  • Hyper-V (careful, upon de-/selection not all sub items get de-/selected even though graphic shows otherwise)
  • Virtual Machine Platform
  • Windows Hypervisor Platform
  • Windows Sandbox
  • Windows Subsystem for Linux

So what I did was fully disable the following:

  • Hyper-V
  • Windows Sandbox
  • Windows Hypervisor Platform
  • Virtual Machine Platform

I'm not sure which of those were actually necessary to disable (I'm sure this would interfere with any VMWare or VirtualBox installation, which I don't use), but it made it work. To be fair, I had previously also performed actions described here:

But that alone wasn't enough, so I don't know if it is also a requirement. Also note that The Issues section on HAXM's Github Page, describe why HAXM and Hyper-V are incompatible and why Hyper-V has to be fully disabled. There is also talk about WSL2 being involved with Hyper-V, hence HAXM not installing when WSL2 is enabled. I personally didn't need to disable it though.

More importantly, since Hyper-V is sometimes needed, the following page explains then how to deal with this when you need HAXM too:

3

I'm also having similar issue and went through the process of enabling virtualization in the bios setup but it still brings up the same error, albeit the only difference in our problem is that my processor is intel core i5

2

You Might Also Like