VMware Communities
tkdreamer2
Enthusiast
Enthusiast
Jump to solution

VMware Workstation does not support nested virtualization on this host. Module 'HV' power on failed

Hello

When trying to deploy a 64bits VM from VMware Workstation 16 hosted on a Windows 11 family edition, I have this error message:

"VMware Workstation does not support nested virtualization on this host.

Module 'HV' power on failed.

Virtualized Intel VT-x/EPT is disabled for this ESX virtual machine. You will only be able to run 32-bit nested virtual machines.

Failed to start the virtual machine."

 

VT is enabled and I tried everything written in the forums:

 

Verify Virtualization-based Security (VBS) is Enabled/Not Enabled:

      1. Open msinfo32/system information on Windows 10
      2. Under System Summary on the Right-hand page, scroll down to Virtualization-based Security and
          ensure the Value is set to Not enabled.
      3. If the value is set to enabled follow the steps given below according to disable Hyper-V.

1. Turn Off Hyper-V

  1. Go to "Turn Windows features on or off"
  2. Make sure Hyper-v is not ticked.
  3. If it is Ticked, untick it and click "Ok".

2. Open command prompt window as an administrator   

  1. Run “bcdedit /enum {current}”
  2. Note down the hypervisorlaunchtype in case this needs to be reverted
  3. Run “bcdedit /set hypervisorlaunchtype off” to disable hypervisor Close the command prompt after   executing the commands and restart the system.

And I have also done this: "make sure that Memory Integrity is OFF
Windows Security -> Device Security -> Core Isolation details"

 

 

1 Solution

Accepted Solutions
GeoStigma
Contributor
Contributor
Jump to solution

@tkdreamer2 

The below recommendation works perfectly thank you for sharing.

"Verify Virtualization-based Security (VBS) is Enabled/Not Enabled:

      1. Open msinfo32/system information on Windows 10
      2. Under System Summary on the Right-hand page, scroll down to Virtualization-based Security and
          ensure the Value is set to Not enabled.
      3. If the value is set to enabled follow the steps given below according to disable Hyper-V.

1. Turn Off Hyper-V

  1. Go to "Turn Windows features on or off"
  2. Make sure Hyper-v is not ticked.
  3. If it is Ticked, untick it and click "Ok".

2. Open command prompt window as an administrator   

  1. Run “bcdedit /enum {current}”
  2. Note down the hypervisorlaunchtype in case this needs to be reverted
  3. Run “bcdedit /set hypervisorlaunchtype off” to disable hypervisor Close the command prompt after   executing the commands and restart the system.

And I have also done this: "make sure that Memory Integrity is OFF
Windows Security -> Device Security -> Core Isolation details"

But I have the Windows blue screen when trying to start the vm... So I made it active again."

Regards,
GeoStigma

View solution in original post

18 Replies
GeoStigma
Contributor
Contributor
Jump to solution

@tkdreamer2 

The below recommendation works perfectly thank you for sharing.

"Verify Virtualization-based Security (VBS) is Enabled/Not Enabled:

      1. Open msinfo32/system information on Windows 10
      2. Under System Summary on the Right-hand page, scroll down to Virtualization-based Security and
          ensure the Value is set to Not enabled.
      3. If the value is set to enabled follow the steps given below according to disable Hyper-V.

1. Turn Off Hyper-V

  1. Go to "Turn Windows features on or off"
  2. Make sure Hyper-v is not ticked.
  3. If it is Ticked, untick it and click "Ok".

2. Open command prompt window as an administrator   

  1. Run “bcdedit /enum {current}”
  2. Note down the hypervisorlaunchtype in case this needs to be reverted
  3. Run “bcdedit /set hypervisorlaunchtype off” to disable hypervisor Close the command prompt after   executing the commands and restart the system.

And I have also done this: "make sure that Memory Integrity is OFF
Windows Security -> Device Security -> Core Isolation details"

But I have the Windows blue screen when trying to start the vm... So I made it active again."

Regards,
GeoStigma

OdMiTiMbO
Contributor
Contributor
Jump to solution

Hi thanks this worked for me as well. It just annoys me that the fix involves disabling security features, are there any fixes that don't involve reducing device security measures?

MGMGMG1
Contributor
Contributor
Jump to solution

HI there,

only solution working for me was:

Process to turn off virtualization-based Security:
Below steps can be followed to turn off virtualization-based Security for Windows 10 Home & Pro:
For Microsoft Windows 10 Pro & above:

Edit group policy (gpedit.msc)
Go to Local Computer Policy > Computer Configuration > Administrative Templates > System
Double Click on Device Guard on the right hand side to open.
Double Click on "Turn On Virtualization Security" to open a new window
It would be "Not Configured", Select "Disable" and click "Ok"
Close the Group Policy Editor.
Restart the system

 

Hope it useful for you as well.

MG

T7AMIL
Contributor
Contributor
Jump to solution

Out of the 10 solutions I've tried
Your only solution that worked
Thank you

tkdreamer2
Enthusiast
Enthusiast
Jump to solution

Problem solved with latest version of VMware Workstation (17)!

JBDell20
Contributor
Contributor
Jump to solution

what do you mean solved with vm workstation 17? Do you have to make any changes? I just upgraded to 17 and still get that message?

0 Kudos
meldirlobor
Contributor
Contributor
Jump to solution

It doesn't work for me either.

 

0 Kudos
JBDell20
Contributor
Contributor
Jump to solution

I was able to get it to work by doing the following below on workstation 17 pro.

1. Go to "Turn Windows features on or off" and unchecked Hyper V (this is under control panel) have to reboot
2. F2 Changed BIOS and made sure everything was checked under virtualization on my local laptop

0 Kudos
AminaHassan
Contributor
Contributor
Jump to solution

Thanks it worked for me

bouchra-we
Contributor
Contributor
Jump to solution

i had the same problem after trying to install the Windows Subsystem for Linux (WSL). 

if your problem persists after deactivating wsl and the vbs

I would advice to deactivate also Virtual Machine Platform (VMP) 

  1. You can disable VMP in the Windows Features menu. To open this, type Windows Features in Search.
  2. Select the Turn Windows features on and off option in the search results.
     
  3. Scroll down the list of features and deselect Virtual Machine Platform.
  4. Click Ok to close the window, then restart your computer.
aldosan6666
Contributor
Contributor
Jump to solution

Worked out perfectly! thank you!

amar3383
Contributor
Contributor
Jump to solution

Finally! it worked. Thanks

jsmolic83
Contributor
Contributor
Jump to solution

Thanks mate!

Tags (1)
Tonerone
Contributor
Contributor
Jump to solution

Nested virtualisation in VMware Workstation requires the guest to have "Virtualize Intel VT-x/EPT or AMD-V/RVI" checked (VM Settings > Processors). It will fail if Virtualisation Based Security is running on the host. msinfo32 will tell you if it is running. You can disable it using group policy UNLESS your host is managed by an MDM (Intune for example) AND your MDM admin has set an MDM setting to force Virtualisation Based Security to run - if this is the case, after you disable it using group policy and gpudate /force, you will see an error from gpudate /force telling you MDM is preventing the gpedit change.   

0 Kudos
omerbutt1478
Contributor
Contributor
Jump to solution

i tried everything but only this solution worked for me so, thanks for your help MGMGMG1

 

jsoto49
Contributor
Contributor
Jump to solution

This was the only thing that also worked for me on Windows 11 Pro.

Thanks!

0 Kudos
gbao1322
Contributor
Contributor
Jump to solution

Thanks a lot! You saved my day. 😍

0 Kudos