Windows 11 24H2/VM Workstation 17 Pro/Error: VMware Workstation does not support nested virtualization on this host.

[gerald santiago]

Hi,

    Please help.

I've done all possible solution to run VMware but still popping this error if I checked the "Virtualize Intel VT-x/EPT or AMD-V/RVI

Error: 

Virtualized AMD-V/RVI is not supported on this platform.

Continue without virtualized AMD-V/RVI?

then

VMware Workstation does not support nested virtualization on this host.

Module 'HV' power on failed.

Failed to start the virtual machine.

Attachment(s)

vmsupport-2024-12-12-11-56.zip   1009 KB 1 version

[backend@dat]

The problem is that latest versions of 24H2 always load the hypervisor. So what you see as Windows 11 is in fact a VM.

I could disable VBS and DriveGuard and everything I found on the net, but I could not manage to prevent loading HV at boot. In msinfo32 you always see the insane "a hypervisor has been detected". And then hasta la vista nested virtualization. 

[NTECHNIX]

Hi, Please help me...!!!

The same error occurs on HP Z2 G9 in Windows 24h2.

The same error occurs with both BIOS settings and Hypervisor disabled settings.
Please help me.

[NTECHNIX]

Hi,

I had the same errors, but I turned off VBS(Vritual Based Security)on Windows 11 and succeeded.

[backend@dat]

I bet it's some version prior to 26100.2605 ... I have VBS off too but nestedV is not working because of W11's "a hypervisor has been detected" in msinfo32.

Once again: diabling VBS and DriveGuard *does not* prevent loading W11's HV. Once you ran into this you can't go back. At least I found ablolutely no solution so far. Even in-place upgrade / repair does not get rid of this insane HV starting at boot. :-/

[Christoph Kaiser]

Hello,

i stumbled across the same issue in the last days when migrating powered off Virtual Machines from an Intel based PC to an AMD based machine with Workstation Pro 17.6.2 installed.

In my case it helped to open the *.vmx file of the machine in a text editor and delete the line "gui.exitOnCLIHLT = "FALSE" completely.

Then i opened the Virtual Machine in the new Workstation Installation and unchecked all marks in section "Virtualization Engine" prior to starting it up:

• "Virtualize Intel CT-x/EPT or AMD-V/RVI" -> unchecked
• "Virtualize CPU performance counter" -> unchecked

Then i started the the virtual machine and depending on the machine ( Win10/Win11) some installations took place during startup, once a reboot was performed, but in the end the virtual machines all booted to normal behaviour.

It worked with encrypted and unencrypted virutal machines in my case.

I hope this could be helpful to some of you as well.

[Christoph Kaiser]

Hello,

i stumbled across the same issue when migrating powered off virtual machines from a former Intel based PC to a now AMD based machine with Workstation Pro 17.6.2 installed.

For me it helped to open the *.vmx file of the virtual machine in a text editor and delete the line 'gui.exitOnCLIHLT = "FALSE" ' completely, prior to opening the virtual machine in Workstation Pro.

After opening the virtual machine in Workstation Pro, i unchecked all checkmarks in setting in section "Processors -> Virtualization engine":

• "Virtualize Intel VT-x/EPT or AMD-V/RVI" -> unchecked
• "Virtualize CPU performance counters" -> unchecked

Then i started the virtual machines and during initial startup some devices got installed/updated, rebooting happened and depending on the client of the virtual machine as well initial configuration of client installation was sometimes retriggered with e.g. question to install windows account and so on. I could cancel these requests as during initial installation of Windows and then the client booted up to login screen, as expected.

This process worked for me with encrypted and unencrypted virtual  machines.

I hope this will help some of you.

[QASIM BASIM]

 I have the same problem and I tried several methods but didn't work !

[Ivan Ivanowski]

Try to Turn Off the Credential Guard in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard the Reg_DWORD "Enabled" set to 0