With the latest update to version 16.2.2 the issue has been fixed, now VM Workstation 16 is again fully compatible to Hyper-V. Or at least that's the case on my PC running Windows 11.
On Windows 10 VMWare Workstation works well with Hyper-V enabled. Windows 11 is another story, at least that's what I have experienced so far. In my case (Arch Linux as guest, Windows 11 as host) I can run the VM but suspending the guest OS is not possible since it crashes the guest. The only...
I use an Arch Linux VM for all my online activity. Linux is much less likely to be infected by some malware that is floating around on the internet. Whats more it allows me to learn about Linux in general without having to dual boot or using a second computer.
I can now confirm that Hyper-V is definitely the culprit. As soon as I start Windows without Hyper-V support suspending the guest OS works again as expected. For the time being I configured my PC to dualboot Windows with and without Hyper-V support.
For me VMWare Workstation Pro 16 worked fine under Windows 10 while Hyper-V was enabled, performance was decent. In fact it's also working under Windows 11 with the only exception that I cannot suspend the guest OS (trying to do so results in a crash of the guest OS).
I use the dust filters that came with my case (Corsair 750D) and clean them once a month using an electric dust remover. From time to time I also check the interior of the PC and give it a good cleaning too.
Today I realized that there seems to be a bug concerning the microphone. No matter if I try to use the Sound Blaster Control Panel or the Windows Settings (System\Sound) I cannot disable the microphone that is connected to my sound card. Even though the microphone symbol in the settings changes...
What are your timeout settings for locking Windows and screen off? Are there any third party screensavers installed? When it happens, does it log you out (session terminated) or is the computer simply locked?
Ah. And you can suspend the guest? On my system this crashes the guest. Maybe it has something to do with Hyper V being enabled on the host. Or the fact that the vm is a Linux system.