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:

https://github.com/intel/haxm/blob/master/docs/manual-windows.md#disabling-hyper-v-on-windows-10

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:

https://developer.android.com/studio/run/emulator-acceleration#vm-windows-whpx