Both Guest and Host become slow and lag when VMware tools is installed (MacOS Monterey)

[sitatec]

The installation works fine, but when I install the VMware tools everything start being slow (Guest and Host).
I've tried different versions of auto-unlocker, I've even tried unlocker, but it still slow until I uninstall the tools.

Is there any chance that the issue is related to the unlocker? Does someone have a solution for this?

• VMware® Workstation 16 Pro 16.2.3 build-19376536
• HOST: Windows 10 Pro, 64-bit (Build 19044.1586) 10.0.19044
• GUEST: MacOS Monterey latest
• Docker is installed on the HOST (but doesn't use Hyper-V which is disabled)

[MortalKim]

What CPU do you have? 12th gen should use big core instead little core. The VM will use little core by default.

[Nico04]

Same issue for me: Guest and Host becomes very slow when VMware tools are installed, and works perfectly fine when not.
Even the music on the host stutters !

In my case it's NOT hardware-related because it was working fine before with the same VM.
I've just re-installed Windows recently, installed lattest VMware.
To be sure, I've tested on a fresh MacOS VM installation, I've got the same issue.
I've got the same issue on MacOS 12.4 and 11.1
I've also tried several VM settings, and with or without this setting ulm.disableMitigations = "TRUE"

I've got Windows 11 with a Ryzen 3900X and a RX 6900 XT

[Nico04]

After hours of trials, I finaly found a fix.
What got me a hint is this message I had when I first installed VMware.
At the time I chose to install the Windows Hypervisor option, so I could use other Hyper-V features.

After some days using MacOS on VMware without the tools, which is quite a pain, I decided to desinstall VMware, start over and try the other option, which is to disable Windows virtualization-based Security.
And suprise : the MacOS VM work perfectly fine with the tools !

[Forge64]

Windows is pulling more and more virtualization functionality into the OS, and it's frequently causing conflicts with VMware Workstation and company. This is unfortunately not fixable by VMware or the unlocker, it's a Windows/User question.