In my case, several VMs of various versions Win8/Win10/Win11 have this issue except for 2 Win10 machines.
It appears the problem arises after the VM hardware compatibility is upgraded to v17.
