I use VirtualBox localhost but I suggest using a remote desktop and see if your network latency is acceptable
i am saving up for more hardware and i may setup a different machine for remote desktop to virtual machines
hyper-v does not work on many laptops so this motivated me to use VirtualBox which does not care
Doh... after all that, it looks like this is happening on Intel machines, too:
Oh well.. at least I got to meet some cool peeps on here.
Hey all... wanted to add a quick reply here that this ended up being an undisclosed bug on MSFT's side that was eventually fixed in a KB. Starting with 18363.752 to be exact. Doesn't really matter as all new installs seem to have it and everything now works as expected. Very happy and relieved! Thank you to all here who took the time to reply to this thread and to offer their thoughts. It is very cool of you! Stay safe out there.