Recommended Free Tools
VMware Workstation can stop starting virtual machines on Windows 11 when Hyper-V, Virtualization-Based Security (VBS), Memory Integrity, or another Windows hypervisor component has claimed the processor’s virtualization features. Common symptoms include an incompatibility error, an unsupported VT-x/EPT error, or a VM that starts very slowly.
You can either run VMware through Windows Hypervisor Platform (WHP), keeping Windows features such as WSL 2, or disable the Windows hypervisor so VMware can use its native monitor. Check the active mode first, then follow the option that fits your needs.
First, check whether VMware is using native mode
Check the log before changing Windows settings to see whether VMware is using its native monitor or the Windows hypervisor.
- Start the affected virtual machine, if it starts.
- Open the VM’s folder in File Explorer.
- Open vmware.log in Notepad.
- Search for Monitor Mode.
| Log entry | Meaning |
|---|---|
| Monitor Mode: CPL0 | VMware’s native monitor is active. |
| Monitor Mode: UML | VMware is using the Windows Hypervisor Platform/Hyper-V interface. This can be slower and does not provide every native virtualization feature. |
If the log reports UML, Windows is still supplying the virtualization layer, even if you have already unchecked the main Hyper-V item in Windows Features.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Option 1: Keep Hyper-V and update VMware
The claim that Hyper-V and VMware can never run together is outdated. VMware added Host Hyper-V Mode in Workstation 15.5.5 and later. The documented minimum requirements include Windows 10 version 20H1 build 19041.264 or newer and an Intel Sandy Bridge-or-newer or AMD Bulldozer-or-newer processor.
Use this option if you need features such as WSL 2, Windows Sandbox, or Memory Integrity. Install a current Workstation release from the Broadcom Support Portal, restart Windows, and test the VM again.
This mode is suitable for ordinary VMs, but it is not equivalent to native VMware mode. A VM configured with Virtualize Intel VT-x/EPT or AMD-V/RVI may fail when VMware is operating through WHP. Performance may also be lower.
Option 2: Disable Hyper-V and VBS for native VMware mode
Use this sequence when you need native VMware performance, nested virtualization, or a VM that fails in UML mode. Disabling these components affects Windows features that depend on the Windows hypervisor, including WSL 2, Windows Sandbox, Windows Defender Application Guard, Memory Integrity, and Credential Guard/Device Guard functionality.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →1. Turn off Memory Integrity
- Open Windows Security.
- Go to Device security > Core isolation details.
- Set Memory integrity to Off.
- Restart Windows.
Memory Integrity is a VBS feature that uses the Windows hypervisor. If the switch is unavailable or turns itself back on, continue with the policy and boot checks below.
2. Clear the Windows virtualization features
- Open Start and search for Turn Windows features on or off.
- Clear Hyper-V, including all of its sub-items.
- Clear Virtual Machine Platform.
- Clear Windows Hypervisor Platform.
- Clear Windows Sandbox, if listed.
- Select OK and restart when Windows requests it.
Clearing only Hyper-V is not enough to establish that VBS, Memory Integrity, WHP, and the boot configuration are no longer launching a hypervisor.
3. Disable the Hyper-V services
- Open Start, search for Services, and press Enter.
- Find Hyper-V and HV Host Service, if present.
- Open each service, set Startup type to Disabled, select Stop if it is running, and select OK.
The available services vary by Windows edition and installed components.
4. Stop the hypervisor at boot
Open PowerShell or Command Prompt as administrator and run:
bcdedit /set hypervisorlaunchtype off
Restart Windows. This boot setting matters even when the optional Windows Features appear to be cleared.
5. Disable the VBS policy, where Group Policy is available
Windows 11 Pro, Enterprise, and other editions that include Local Group Policy Editor can retain VBS through policy.
- Press Win + R, type gpedit.msc, and press Enter.
- Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard.
- Open Turn on Virtualization Based Security.
- Set it to Disabled, select OK, and restart Windows.
Group Policy Editor may not be available on Windows 11 Home. Device Guard is no longer a standalone Windows feature; the policy location name remains relevant for finding VBS and Memory Integrity settings.
Verify that Windows stopped using its hypervisor
PowerShell check
Run PowerShell as administrator and execute:
Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard
Rank #3
Check VirtualizationBasedSecurityStatus:
| Value | Meaning |
|---|---|
| 0 | VBS is not enabled. |
| 1 | VBS is enabled but not running. |
| 2 | VBS is enabled and running. |
For native VMware mode, the target result is 0. If the command reports that VBS is still running, revisit Memory Integrity, Group Policy, Windows Features, and the boot command.
System Information check
- Press Win + R, type msinfo32.exe, and press Enter.
- Stay on System Summary.
- Review the virtualization-based security entries at the bottom of the page.
If System Information says that a hypervisor has been detected, Windows is still booting one. This can happen even when some optional features are unchecked.
After the checks pass, start the VM and inspect vmware.log again. Native operation should show Monitor Mode: CPL0.
If the error mentions nested virtualization
An error such as “This host appears to be running in a virtual machine with VHV disabled” can have another cause: VMware Workstation itself may be running inside another virtual machine.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →When the outer VM runs on ESXi, expose hardware virtualization to it:
- Open the vSphere Client.
- Right-click the outer VM and select Edit Settings.
- Open CPU.
- Enable Expose hardware assisted virtualization to the guest OS.
- Select OK, then restart the outer VM.
Without this setting, the guest Windows installation cannot pass VT-x/EPT or AMD-V/RVI through to VMware Workstation.
If Windows 11 was recently upgraded
A Windows 10-to-Windows 11 upgrade can leave Hyper-V services, VBS policy, or the boot hypervisor enabled. Broadcom documents this issue for Workstation Pro 17.5.2. Use the complete sequence above rather than only reinstalling VMware:
- Stop the Hyper-V services.
- Clear Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Sandbox.
- Run bcdedit /set hypervisorlaunchtype off from an elevated terminal.
- Disable the VBS policy.
- Turn off Memory Integrity.
- Restart and verify with msinfo32.exe or the Win32_DeviceGuard command.
Check your Workstation version for an older guest BSOD issue
Windows 10 and Windows 11 guests running in Host VBS Mode could encounter an Unsupported Processor blue screen with stop code 0x5D after installing 22H2 updates. Broadcom lists the issue as resolved in Workstation 16.2.5, Workstation 17.0, and later. Updating Workstation is preferable to trying to work around that particular guest crash.
Free tools Windows power users keep installed
One-click scans. No signup required.
When Secure Boot or UEFI lock prevents the change
If VBS was enabled with UEFI lock, changing Windows settings or registry values may not be sufficient. Disabling Secure Boot through the computer’s UEFI/BIOS interface may be required before the VBS configuration can be changed. This is a security-sensitive change: follow your organization’s policy and understand which Windows protections will be lost before proceeding.
Current Workstation release context
VMware Workstation Pro 26H1 became generally available on May 14, 2026. VMware moved to calendar-based versioning beginning with 25H2, and Workstation Pro for Windows is now a 64-bit application in 26H1. Workstation Pro remains free for commercial, educational, and personal use and is distributed through the Broadcom Support Portal.
Installing 26H1 will not, by itself, make native mode available if Windows is still running Hyper-V or VBS. Check the Windows configuration and VMware monitor mode.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.FAQ
Can VMware Workstation and Hyper-V run together on Windows 11?
Yes. Workstation 15.5.5 and newer can use Windows Hypervisor Platform through Host Hyper-V Mode. Compatibility mode supports ordinary VMs, but it can be slower and may not support nested hardware virtualization.
Best Value
- Used Book in Good Condition
Why does VMware still report Hyper-V after I unchecked Hyper-V?
Windows may still have Virtual Machine Platform, Windows Hypervisor Platform, Windows Sandbox, Memory Integrity, a VBS policy, Hyper-V services, or the boot setting hypervisorlaunchtype enabled. Verify with msinfo32.exe and the Win32_DeviceGuard PowerShell command.
What does “Monitor Mode: UML” mean in vmware.log?
UML means VMware is using the Windows Hypervisor Platform/Hyper-V interface. Native VMware mode reports Monitor Mode: CPL0.
Will disabling Hyper-V break WSL?
It can. WSL 2, Windows Sandbox, Windows Defender Application Guard, Memory Integrity, and Credential Guard/Device Guard functionality depend on the Windows hypervisor or related virtualization protections.
Why does nested virtualization fail even after disabling Hyper-V?
If Workstation is itself running inside an ESXi VM, the outer VM must expose hardware-assisted virtualization. In vSphere, edit the VM’s CPU settings and enable Expose hardware assisted virtualization to the guest OS.
The Bottom Line
For native VMware performance, turn off Memory Integrity, clear Hyper-V and the other Windows virtualization features, disable the relevant services and VBS policy, run bcdedit /set hypervisorlaunchtype off, and restart. Confirm that VBS is inactive and that vmware.log reports Monitor Mode: CPL0. If you need WSL 2, Sandbox, or Memory Integrity, leave Hyper-V enabled, use a current Workstation release, and accept WHP compatibility mode and its limitations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
