There are no settings in the VM that will help you with this. The workarounds are all Windows OS tweaks due to the interaction of Workstation, Hyper-V, and 12th gen Core CPUs. (and it's not clear really who's to blame, so don't automatically blame VMware. I believe Microsoft shoulders some of the blame here as well).
Try the following first:
Open a command prompt on Windows as administrator, and run the following command to disable power throttling on a VM (for some reason, Windows wants to run VM virtual CPUs on E-Cores, not P-Cores)
powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
If that doesn't work, you'll need to disable Windows' use of Hyper-V technology entirely in order to force the use of the VMware hypervisor and not Hyper-V:
- Make sure anything virtualization or Hyper-V related is uninstalled in Windows (check in Add/Remove Windows Features).
- Disable Memory Integrity/VBS settings by opening Windows Settings and navigate to
Windows Security -> Device Security -> Core Isolation then turn off the "Memory Integrity" slider - Disable any Hyper-V activity by opening a command prompt as administrator and issuing the following:
bcdedit /set hypervisorlaunchtype off
Note that this precludes the use of WSL2 as WSL2 needs Hyper-V components.
- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
