NoelC1 wrote:
My own personal thoughts are that maybe somehow the change in the Windows scheduler so that interrupts don't occur at regular 1/1000 second intervals but are now variable has somehow affected a driver or protocol implementation.
Following up on that thought, try adding the following option to the .vmx file (with the VM powered off):
timeTracker.lazyApic = FALSE