Windows 11 24H2 update and Workstation Pro cannot do nested virtualization

[cer113a]

HI

I just have updated windows 11 to 24H2 and after that when i try to launch esxi as a virtual machine in workstation pro 17.6.1 I am getting following error

Virtualized Intel VT-x/EPT is not supported on this platform.

Before upgrade it was working just fine but now with newest update i am no longer able to open ESXi as a virtual machine. I have tried all fixes available on internet but no luck

I am sure that it is Windows 24H2 update. I am not in any rush it is lab environment but just wondering did anyone else had issues

[Xx8leunam9xx]

I have exactly the same error and as you say, I already did everything without any success, I even formatted the computer without success. I think we will have to wait for an update to correct said error.

[Xx8leunam9xx]

Apart from me I also have a group of colleagues with the same problem, they tried everything for more than a week of trying everything without success.

[gbohn]

You may have already checked this out, but did updating to 24H2 enable Hyper-V on the host by any chance (through any of it's many 'security features' getting enabled)? 

That could possibly change you from from running Workstation in 

vmx Monitor Mode: CPL0

to

vmx Monitor Mode: ULM

which would not support "Virtualized Intel VT-x/EPT" if I understand correctly.

Your vmware.log for the guest would tell you which mode you are running in I would think.

[cer113a]

I disabled all these features but will see vmx file and try to change hyper v is disabled but still same thing

Get Outlook for Android<https: aka.ms aab9ysg>




________________________________
Canada's Largest and Most Reliable 5G Network

This communication is confidential. We only send and receive email on the basis of the terms set out at https://www.rogers.com/emailnotice<https: www.rogers.com web rogers.portal?_nfpb=true&_pageLabel=NEW_GCT&_nfls=true&setLanguage=en&template=emailnotice>



Le r?seau 5G le plus ?tendu et le plus fiable au pays

Ce message est confidentiel. Notre transmission et r?ception de courriels se fait strictement suivant les modalit?s ?nonc?es dans l'avis publi? ? www.rogers.com/aviscourriel <https: www.rogers.com aviscourriel>

[cer113a]

Yes vmx monitor mode changed to ULM

Get Outlook for Android<https: aka.ms aab9ysg>

[cer113a]

This is exactly what happened I disabled Hyper-V but still the same thing

[cer113a]

it is exactly what happened so what can be done about it or nothing can be done

[gbohn]

I am only running Windows 11 23H2 at the moment (with all of Hyper-V disabled), so I can't address 24H2.

I do remember that (at the time) to get hyper-v disabled I needed to disable all of the various 'Security features' that enable it (like 'core isolation') and after that use the command-line "bcdedit" command (shown in another post of this thread).

I don't know if that will still work with 24H2 or not.

[cer113a]

disabled but still it is running VBS is still running although i disabled it however VBS still showing as running

[kasper]

24H2 introduces virtual device security in the kernel.   Open task manager and look for the process 'secure system'.   I believe it visualizes device drivers and other core kernel components.   And it consumes a lot of memory in doing so.   If you open settings / privacy & security / Windows security / device security and disable a bunch of stuff that may work.    When you installed  Workstation did you get the message that HyperV was required?   That is one sign.    You may also have to rip out all the HyperV stuff on the host.

[cer113a]

Most likely I will have to revert back since no viable solution is available

Get Outlook for Android<https: aka.ms aab9ysg>

[kasper]

Consider Windows 2025 server eval.   You lose all the silly apps that come with 24H2.    You lose the kernel virtualization thingys.   You should be able to do nested VM guests.

[cer113a]

I am able to run virtual machines but just not esxi which was working in 23H2

Get Outlook for Android<https: aka.ms aab9ysg>

[cer113a]

I did disabled but it is still running no effect

[cer113a]

IT says Installer detected the host has Hyper-V or Device/Credential guard enabled

How do I turn this off

[Pollard]

For some reason the GUI doesn't work on windows 11 to disable hyper-v run this in administrator command line for the fix. 

bcdedit /set hypervisorlaunchtype off

[Xx8leunam9xx]

None of that works in Windows 11 24h2, everything on the network has already been tested, even reinstalling the system. It is definitely a VMware problem with Windows 11 24h2 that does not allow nested virtualization.

[cer113a]

this works in 23H2 but not on 24H2

[kasper]

VMWare Workstation 17.6.1 can do nested virtualization.    I am using Windows 2025 server eval as the host.    I have ESXi 7x running.    Under it I have 2 copies of server 2022 running.   The issue is not 17.6.1.   The issue is Win11 24h2.   You have uninstall anything to do with HyperV from the Win11 24h2 host.   Then install 17.6.1.   During the install of 17.6.1 if you get the popup to install HyperV then HyperV has not been fully removed from the host.   Or you can use a 2025 server host.   Or a LInux host.

[Xx8leunam9xx]

Everything is already uninstalled, which is why it is mentioned that everything you can find on the internet has already been tested. I even contacted Microsoft support for the problem and not even they, with remote support, can understand why it doesn't work if everything is already as it should, device guard, policies, etc., even BIOS updates by hardware manufacturers already providing support. I tried on two other computers and both give the same problem with Windows 11 24H2. I even tried using virtualbox and virtualbox does not have problems of this type if it accepts nested virtualization, the problem is most likely something related to vmware workstation

[kasper]

Funny how it works with server 2025.    It is a Windows 11 24h2 issue.    Talk to Microsoft.

[cer113a]

Yes VMware workstation pro 17.6.1 is working good in 23H2 but not in windows 11 24H2 

[Timothy Giese]

You would think that VT-x no longer being available on 24H2 would have been something that was broadcast.  

Does anyone know if Hyper-V has access to using VT-x on windows 11 24H2?

[Vinitha V Nair]

Hi,

Could you please provide the support bundle from WS on Windows 11 24H2 host?

[cer113a]

HI

The problem is that I cannot disable Virtualization based security. If there is a way to disable that in Windows 11 24H2 then nested virtualization will work but I cannot disable it as I was able in 23H2 this is just lab computer at home I use it to test new scripts and some other stuff before I implement it in production at work

Attachment(s)

vmsupport-2024-10-24-08-03.zip   5.59 MB 1 version

[cer113a]

for what it is worth problem is fixed now and VBS is not running now there are at least 50 registry keys you need to disable and I cannot get all of them i was just disabling one after another and eventually VBS is showing not running

You can close this thing now

[cer113a]

I have updated BIOS from HP and removed few more registry entries and it is working now so you can disregard. 

[Xx8leunam9xx]

It is the only thing that I had not thought about trying the registry keys since that consumes time to disable them in my case I think I will try it on the weekend in my free time

[Xx8leunam9xx]

I attach my WS because I still have the problem and I have tried everything without any success. I hope it will be helpful to solve the problem because it is urgent due to my study and work laboratories. Thank you for your support.

Attachment(s)

vmsupport-2024-10-24-13-46.zip   4.70 MB 1 version

[kasper]

It is unclear if 24h2 can do nested virtualization.   There are a number of steps you need to do in order for that to work.   No one has posted all the steps they have tried starting with a check in the BIOS to make sure cpu virtulation is available.   Along with that try these:

go to services and disable all 'hyperv'got to tasks and disable all hypervsettings / security / disable memory core isolation
powershell:   disable-windowsoptionalfeature -online -featurename microsoft-hyper-v-all
dism /online /disable-feature /featurename:microsoft-hyper-v-all
reg: system\currentcontrolset\control\deviceguard   enablevirtualizationbasedsecurity dword value 0
bcdedit /set hypervisorlaunchtype off

I am happy using 2025 as the host.   Nested virtualization works and I dont have the bloatware.

Someone please save me the time of trying 24h2 host myself.    Someone please post that they can do nested virtualization on 24h2.

[voytec13]

After few days I've managed to disable VBS in Windows 11 Pro 24H2.

To be sure that UEFI variables are not taking precedense ove OS/registry settings I've followed the steps described here:

https://learn.microsoft.com/en-us/windows/security/identity-protection/credential-guard/configure?tabs=reg

Then I found this:

https://www.jaspreet.net/2024/10/11/2731/how-to-properly-disable-virtualization-based-security-vbs-in-windows-11-24h2/

Which also mention disabling Tamper Protection.

After few restarts systeminfo (run it from cmd or powershell) eventually shows:
Virtualization-based security: Status: Not enabled :-)

And VMware Workstation Pro 17.6.1 no longer complains about lack of support for VT-x/EPT.

Hope it helps someone.

Cheers everybody!

[cer113a]

Just disable virtualization based security

Get Outlook for Android<https: aka.ms aab9ysg>




________________________________
Canada's Largest and Most Reliable 5G Network

This communication is confidential. We only send and receive email on the basis of the terms set out at https://www.rogers.com/emailnotice<https: www.rogers.com web rogers.portal?_nfpb=true&_pageLabel=NEW_GCT&_nfls=true&setLanguage=en&template=emailnotice>



Le r?seau 5G le plus ?tendu et le plus fiable au pays

Ce message est confidentiel. Notre transmission et r?ception de courriels se fait strictement suivant les modalit?s ?nonc?es dans l'avis publi? ? www.rogers.com/aviscourriel <https: www.rogers.com aviscourriel>

[backend@dat]

It's not that easy... You can get into a situation where VBS is not running byt Hyper-V is ...

Still trying to figure out how to get rid of this insane "... a hypervisor has been detected" ... 

[Jack Smith]

disable the Linux subsystem, that prevents any other virtualization.

[Newton Viegas]

I've found a solution on another website. As I don't know if I can post links, just search for Device Guard and Credential Guard hardware readiness tool. You will find a link to a Microsoft website. Download the tool, read the instructions and run it. It took me 3 minutes and after DAYS VBS is finally disabled. Good Luck!

[Hamza Trby]

I believe the only way to disable VBS on Windows 24H2 is by using that Microsoft tool(Device Guard and Credential Guard hardware readiness tool). I've tried every other method, but none of them work for this version. I highly recommend anyone using Windows 24H2 to utilize this tool.

[Hartmut Honisch]

FWIW this worked for me on Windows 11 24H2 and VMware Workstation 17.6.2:

• Use Microsoft "Device Guard and Credential Guard hardware readiness tool" (https://www.microsoft.com/en-us/download/details.aspx?id=53337) to disable "Device Guard" and "Credential Guard" => Reboot => Confirm the changes when Windows asks for it at an early stage in the boot process
• Disable Hyper-V running "bcdedit /set hypervisorlaunchtype off" => Reboot

After that, VMWare Workstation is able to do nested virtualization again, which means it's using the VMware hypervisor, and not Hyper-V

[Maneesh Mishra]

Hi Hartmut,

I just disabled "Virtualize Intel VT-x/EPT". It worked for me.

VM>Processor>Virtual engine> Uncheck Virtualize Intel VT-x/EPT.

[Stas Skripka]

VMWARE Workstation Pro 15.5.5 work!!!

[Arrr]

I wrote a blog post about this issue with a work-around script but also with precautions because the work-around for this issue could modify Windows Hello settings and Bitlocker settings. 

https://metisit.com/nieuws/virtualization-issues-with-vmware-workstation-pro-on-windows-11-version-24h2/

[Aiman Buyahl]

Thank you so much that finally work, but I'n not really sure what is the security impact on the machine after disabling all these security.?

[Arrr]

Hi Aiman,

Good to hear that you fixed it. The security impact is that the security is lowered to the Windows version prior than 24H2.

Microsoft should solve this and I heard rumours that it will be solved in version 25H2.

My advise is to test this when your Windows version has been upgraded.

[prince Tiwari]

Try below work its working.

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\ WindowsHello\Enabled" -> 0 

[prince Tiwari]

Try it, it's work in win 11 

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\ WindowsHello\Enabled" -> 0 

[BR rr]

Hello everyone, I wrote the following article today, which addresses which registry keys must be created and configured, for this to work. 
--
Title: Using 'hardware assisted virtualization' outside Hyper-V

Author: _____

Date: 9/4/2025

Tags: VMware, VirtualBox, hardware assisted virtualization, Hyper-V, Windows 11

Error Message: Virtualized Intel VT-x/EPT not supported on this platform/ Workstation does not support nested virualisation on the host

The following Windows 11 features must be disabled for 'hardware assisted virtualization' capabilities like VT-x and AMD-V.to work in Windows 11 without Hyper-V. However additional registry keys needed to be created on Windows 11 24H2 to disable 'memory integrity'

Feature	Purpose	Blocks VT-x for VMware?
Hyper-V	Native virtualization	✅ Yes
VBS	Isolate sensitive OS components	✅ Yes
HVCI	Driver integrity	✅ Yes
Credential Guard	Protect credentials	✅ Yes
Virtual Machine Platform	Enable WSL2/Docker	✅ Yes
Windows Hypervisor Platform	API for virtualization	✅ Yes

--------

# Run as Administrator

# Create missing registry keys

New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard" -Force | Out-Null

New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios" -Force | Out-Null

New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" -Force | Out-Null

# Disable VBS and Memory Integrity

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard" -Name "EnableVirtualizationBasedSecurity" -Value 0 -Type DWord

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard" -Name "RequirePlatformSecurityFeatures" -Value 0 -Type DWord

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" -Name "Enabled" -Value 0 -Type DWord

# Disable VBS via Group Policy

New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard" -Force | Out-Null

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard" -Name "EnableVirtualizationBasedSecurity" -Value 0 -Type DWord

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard" -Name "RequirePlatformSecurityFeatures" -Value 0 -Type DWord

# Disable Credential Guard

New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa" -Force | Out-Null

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa" -Name "LsaCfgFlags" -Value 0 -Type DWord

# Disable Hyper-V and related features via DISM

dism /online /disable-feature /featurename:Microsoft-Hyper-V-All /norestart

dism /online /disable-feature /featurename:VirtualMachinePlatform /norestart

dism /online /disable-feature /featurename:WindowsHypervisorPlatform /norestart

# Disable Hypervisor launch

bcdedit /set hypervisorlaunchtype off

# Confirmation

Write-Host "✅ All virtualization-blocking features have been disabled. Please restart your system to apply changes."

-------------------------------------------

[Abdulqader Rasool]

That worked for me, I have Win11 25H2, Vmware Workstation 25H2.

Thanks very much.

-------------------------------------------

[Abdulqader Rasool]

Many thanks, finally it worked for me for Workstatiom 25H2 on my win11 pro 25h2.

-------------------------------------------