Host: Windows 10 Pro
Guest: Windows 11 Pro
VMware Workstation Pro 16.2.1
The problem I have, is that can't run Windows Subsystem for Android™ on the guest. On the Host, if it's W11, I can.
Maybe "Hyper-V", "Virtual Machine Platform" and "Windows Hypervisor Platform" can't be run inside a guest operating system?
To have nested virtualisation (i.e. running VMs inside a VM) with Workstation Pro, the VM Processor setting "Virtualize Intel VT-x/EPT or AMD-V/RVI" needs to be enabled/checked.
However, if Hyper-V is already enabled on the Windows 10 host, nested virtualisation will not work. So you would have to remove Hyper-V from the host aside from the VM processor setting mentioned above. When Hyper-V is enabled on the host, Workstation Pro/Player will use the Windows Hypervisor API (user-mode) instead of the native ring 0 Intel VT-x (which is way much faster than user mode).
Hyper-V is removed from the host, and can't run Hyper-V on the guest.
You can check whether Hyper-V is still detected by Workstation Pro in the vmware.log of any VM.
<timestamp>| vmx| I005: IOPL_Init: Hyper-V detected by CPUID
<timestamp>| vmx| I005: Monitor Mode: ULM
Turn off Hyper-V, follow this KB
https://kb.vmware.com/s/article/2146361
Make sure that Memory Integrity is also OFF on the host.
Windows Security -> Device Security -> Core Isolation details
Monitor Mode would be CPL0 (instead of ULM) if Hyper-V is no longer detected.
If your Windows 10 Pro host is a member of an AD domain, Device Guard/Memory Integrity can also be enforced through domain policy. If that is the case, you need to talk to your domain admin.
