VMware Workstation Windows 11 compatibility breaks in a handful of specific ways, and most of them can be fixed. If you're getting the 'VMware and Hyper-V are not compatible' error, VMs that refuse to start, or a Windows 11 guest installer that throws 'This PC can't run Windows 11', there's a concrete reason behind it. This guide covers all of them, in order of effort.
What Causes VMware Workstation Windows 11 Compatibility Problems?
Windows 11 often runs its own hypervisor in the background, even if you've never installed Hyper-V. Core isolation's Memory integrity, Virtual Machine Platform, which WSL2 needs, and Hyper-V itself can start Microsoft's hypervisor when Windows boots. Windows Sandbox also relies on hardware virtualisation, but it's a separate optional feature. That changes how VMware Workstation can work on the machine.
Older versions of Workstation needed the processor's virtualisation hardware (Intel VT-x or AMD-V) to themselves, so with Microsoft's hypervisor running they refused to start a VM, with errors such as "VMware Workstation and Hyper-V are not compatible". Workstation 15.5.5 introduced the ability to run on top of Microsoft's hypervisor through the Windows Hypervisor Platform. On a Windows 11 host, Broadcom supports Workstation 16.2 or later. VMs then start, though some workloads run slower that way, and a few features, nested virtualisation among them, behave differently or stop working.
The guest is the other half. A Windows 11 guest needs UEFI firmware, Secure Boot capability and a TPM 2.0, along with Microsoft's RAM, storage and processor requirements. Workstation Pro requires at least partial VM encryption before you can add a virtual TPM. The old Workstation Player can't add one at all, so if you still use Player, install the free Workstation Pro instead. If the installer stops with "This PC can't run Windows 11", check all of those requirements. An ISO for the wrong processor type (ARM on an Intel or AMD PC) gives boot errors that look unrelated.
And there's the plain stuff: virtualisation switched off in the PC's firmware, or a Workstation release that's simply too old for your Windows build. Microsoft's own documentation on VBS explains what Memory integrity protects, which matters before you turn it off.
VMware Workstation Windows 11 Compatibility: Quick Fixes
These two don't touch the Windows boot configuration. Updating Workstation is still a software install, though, so back up your VM folders first, as fix 1 says.
Update VMware Workstation Easy
- Check your version
Open Workstation and go to Help > About VMware Workstation. Version 15.5.5 introduced Windows Hypervisor Platform mode, but for a Windows 11 host use Workstation 16.2 or later. Better still, install the current supported release. - Get the current release
Workstation Pro is distributed by Broadcom and is free for personal, educational and commercial use. Download the current version from Broadcom's support portal and follow Broadcom's installation instructions. Keep a backup of any important VM folders before changing Workstation. Broadcom's Workstation Pro 26H1 documentation links the release notes for each update, which cover changes and known issues. - Restart and test
Restart the PC, open Workstation and start a VM.
Check Virtualisation Is On in the Firmware Easy
- Look in Task Manager
Press Ctrl + Shift + Esc, open the Performance tab and click CPU. Virtualization should say Enabled. - If it says Disabled
Restart into the PC's BIOS or UEFI setup (the key is shown at power-on, often F2 or Del) and turn on Intel Virtualization Technology (VT-x) or AMD SVM. The name depends on the maker. Save and exit. - Leave other firmware settings alone
Change only the virtualisation option. If BitLocker is on, have your recovery key to hand, because firmware changes can make Windows ask for it.
Intermediate VMware Workstation Windows 11 Compatibility Fixes
Up to date and still slow, or still refusing to start? Then decide if you want VMware running on Microsoft's hypervisor, or on its own. Both are valid, and the choice comes down to which Windows features you need.
Disable Memory Integrity (Core Isolation) Easy
- Know the trade-off
Memory integrity helps stop malicious drivers loading into Windows. Turning it off is reasonable on a machine used mainly for virtual machines, less so on the laptop you bank on. You can turn it back on any time. - Turn it off
Open Windows Security > Device security > Core isolation details and switch Memory integrity off. - Restart and test
A full restart is needed. Then start a VM and see if it's faster. On its own this may not stop Microsoft's hypervisor if other features still use it, which is what fix 4 checks.
Disable Hyper-V via Windows Features Medium
- Check what you'd lose
Turning these off stops WSL2, Windows Sandbox, Docker Desktop's WSL2 back end and any Hyper-V VMs working. If you rely on them, keep them and let Workstation run on Microsoft's hypervisor instead. - Open Windows Features
Press Win + R, typeoptionalfeaturesand press Enter. - Untick the hypervisor features
Untick Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform and Windows Sandbox if they're ticked. Click OK and restart when asked. - Test
Start a VM. If Microsoft's hypervisor is no longer running, Workstation uses the processor's virtualisation directly again.
Configure a Windows 11 Guest Correctly Medium
- "No compatible bootloader found"?
That message at a new VM's first start means the VM's firmware couldn't use the bootloader on the device it tried. Check VM Settings > Hardware > CD/DVD shows Connected at power on with your ISO selected, and that the ISO matches the VM (x64 for an Intel or AMD PC). If the VM boots past the message too quickly, press a key when it says Press any key to boot from CD or DVD. - Use the right ISO
Download the Windows 11 x64 ISO from Microsoft. On an Intel or AMD PC, don't use an ARM ISO. - Pick the guest type
In the New Virtual Machine wizard, choose Windows 10 and later x64. Before starting the VM, open VM Settings > Hardware, set at least 4 GB of memory, 64 GB of storage and two processor cores, then under Options > Advanced select UEFI and enable Secure Boot. - Encrypt the VM, then add the TPM
A virtual TPM needs VM encryption. Before starting the VM, open VM Settings > Options > Access Control, click Encrypt and set or generate an encryption password. Keep that password safe, because without it the VM can't be opened. Choose the option to encrypt only the files the TPM needs. Then open VM Settings > Hardware > Add and choose Trusted Platform Module. - For an existing VM
If it already boots in UEFI from a GPT disk, shut it down and back up the VM first. Open VM Settings > Options > Access Control to encrypt it. Don't encrypt it if an unencrypted VM shares its virtual disk, and don't change encryption while snapshots exist. Then choose Hardware > Add > Trusted Platform Module, and check Options > Advanced shows UEFI firmware with Secure Boot. If it's a legacy BIOS (MBR) Windows VM, don't just switch it to UEFI. Back it up or clone it, then follow Microsoft's MBR2GPT guidance, including its BitLocker steps, or create a new Windows 11 VM and move your files across.
Advanced VMware Workstation Windows 11 Compatibility Fixes
If those settings don't seem to stick, check what's actually running. Windows will tell you plainly whether its hypervisor is on, and the VM's own log records which mode Workstation used.
Find Out Whether Microsoft's Hypervisor Is Running Medium
- Ask System Information
Press Win + R, typemsinfo32and look at the System Summary. "A hypervisor has been detected" near the bottom means Microsoft's hypervisor is running. The Virtualization-based security line says whether VBS is running and which services use it. - Read the VM's log
Start the VM, then openvmware.login the VM's folder in Notepad and search for "Monitor Mode". UML means Workstation ran on top of Microsoft's hypervisor. CPL0 means it had the hardware to itself. - Cross-check with systeminfo
Runsysteminfoand scroll to the end. "A hypervisor has been detected. Features required for Hyper-V will not be displayed." means Microsoft's hypervisor is running. A list of Hyper-V requirements instead means it isn't. - Check the boot setting
In Terminal as administrator, runbcdedit /enum {current}and look for hypervisorlaunchtype. Off means Windows won't start the hypervisor at boot. Auto, or no line at all, means it will if a feature asks for it.
Disable Hyper-V at Boot with BCDEdit Hard
- Note what stops working
As with fix 4, WSL2, Windows Sandbox and Hyper-V VMs won't run while the hypervisor is off at boot. Memory integrity and other VBS features also can't run without it. - Turn it off
Open Terminal as administrator. If BitLocker is on, suspend its protection before continuing and resume it after testing, or make sure you have its recovery key to hand because changing BCD can trigger recovery. First runbcdedit /export C:\BCD-backup, which saves a copy of the boot settings. Then runbcdedit /set hypervisorlaunchtype off. You should see "The operation completed successfully." Restart. If Windows won't start afterwards, open Command Prompt from Windows Recovery and restore the copy withbcdedit /import C:\BCD-backup, adjusting the drive letter if recovery shows it differently. - Confirm
Check msinfo32 and the VM's log again, as in fix 6. The log should now say CPL0. - To undo
Runbcdedit /set hypervisorlaunchtype autoand restart. Keep a note of this command.
Disable VBS via Registry Hard
- Only if msinfo32 still shows VBS running
Some PCs turn VBS on through a policy or a firmware lock, and it stays on after the GUI changes. On a work PC, stop and ask IT, because this weakens protections they may require. - Back up first
Create a restore point, then inregeditexportHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuardbefore changing it. - Turn it off
In that key, set the DWORDEnableVirtualizationBasedSecurityto 0. Restart and check msinfo32 again. - If it comes back
A policy, Credential Guard or a UEFI lock can keep VBS on. Microsoft documents how to remove Credential Guard, including a UEFI lock, in its Credential Guard guidance. Follow that exactly rather than deleting keys, because a mistake here can leave the PC asking for its BitLocker key or unable to start.
Bypass Windows 11 Hardware Checks in the Guest Installer Hard
- For test VMs only
If you can't add a TPM to a test VM, you can make the installer inside that VM skip its TPM check. It doesn't change the host, but Microsoft doesn't support Windows 11 installed this way, and it may not get updates. - Open the installer's Command Prompt
When the VM's installer shows "This PC can't run Windows 11", press Shift + F10, typeregeditand press Enter. - Add the bypass values
Go toHKEY_LOCAL_MACHINE\SYSTEM\Setup, create a key calledLabConfig, and in it create a DWORD valueBypassTPMCheckset to 1. Close Registry Editor and Command Prompt, click Back and continue.
vmware.log and search Broadcom's knowledge base for that exact message. And if you need WSL2, Docker or Windows Sandbox on the same PC, accept the UML mode, which can be slower, rather than fighting Windows every update.For IT Pros: VMware Workstation and VBS on Managed PCs
On company PCs, Microsoft's hypervisor is often on by policy, which is why the steps above don't stick.
- Check the Device Guard policy.
In Group Policy, look at Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security. If it's Enabled, VBS can come back. Memory integrity only comes back if Virtualization Based Protection of Code Integrity is enabled there as well. Intune can set the same settings through a device configuration profile. - Remember Credential Guard.
On eligible Windows 11 Enterprise and Education devices, Microsoft turns Credential Guard on by default from version 22H2, and it runs on VBS. msinfo32 lists it under Virtualization-based security Services Running. - Decide per machine, not per user.
For developers who need Workstation at full speed, use a separate policy group with VBS off, or accept Windows Hypervisor Platform mode. Don't let users switch security features off locally against your baseline.
Preventing VMware Workstation Windows 11 Compatibility Issues
These problems tend to come back after updates, so a few habits save a lot of head-scratching.
Update Workstation before big Windows updates. Check Broadcom's release notes for your version before a Windows feature update on a machine you rely on for VMs, and install a newer Workstation first if one mentions Windows 11 fixes.
Recheck after feature updates. A feature update can turn Memory integrity or Virtual Machine Platform back on. Afterwards, look at Core isolation in Windows Security and at msinfo32's hypervisor line.
Build a Windows 11 template once. Make one Windows 11 VM with UEFI, Secure Boot and a TPM, keep its encryption password safe, then make full clones for new VMs. Workstation doesn't allow linked clones of a VM encrypted, even partially, for a virtual TPM.
Pick one way of working. Either keep Microsoft's hypervisor for WSL2 and Sandbox and accept that some VMs will run slower, or turn it off and give Workstation the hardware. Switching back and forth is what causes most of the confusion.
Note your firmware settings. Check Task Manager shows virtualisation enabled on a new PC before installing Workstation, and write down which firmware option you changed.
VMware Workstation Windows 11 Compatibility: Summary
VMware Workstation Windows 11 compatibility comes down to who owns the processor's virtualisation. On a current Workstation, VMs run alongside Microsoft's hypervisor, though some workloads run slower that way. Update Workstation first, check virtualisation is on in the firmware, then decide whether to turn off Memory integrity and the hypervisor features or live with the slower mode.
When changes don't seem to stick, msinfo32 and the VM's vmware.log show what's running, and bcdedit /enum {current} shows whether Windows is set not to start its hypervisor at boot. For a Windows 11 guest, choose Windows 10 and later x64, configure UEFI and Secure Boot, then encrypt the VM and add a virtual TPM.

