@banackmand @steve_goddard, FYI, I tried the previously recommended fix of adding to the .VMX file:
mks.enableX11Presentation = "TRUE"
mks.enableVulkanPresentation = "FALSE"
while retaning:
mks.enable3d = "TRUE"
This fixed my mkssandbox hang (wherein the mkssandbox process pins one host CPU core at 100% with no discernible trigger, freezing the Win10 client, including Task Manager and VMware Tools (preventing Player termination other than via system reset), indefinitely) for about two weeks until today, when the behavior resumed and recurred randomly and with increasing frequency.
The setup is W10 on Player 16.2.1 on Ubuntu 20.04, fully patched. Hwr is a four-core Xeon with 16GB RAM, three cores and ~11.5GB RAM allocated to the guest. Ancient nVidia adapter and two monitors. vmnet8, no folder sharing but the host serves SMB natively via Samba to the guest and machines on local physical subnets..
I'll diddle and fiddle with some of the subsequent suggestions re timeouts, etc., but you need to know the Vulkan approach fails.
