Hey, appreciated for the reply.
Below a screenshot of Ryzen Master (Which unfortunately requires Hyper-V to be disabled).
So, I actually had this turn around took the MoBo manufacturer drivers for the chipset, and frankly the power plan was missing - Found mildly odd because on the first Windows install I had seen it there, so, something was amiss but didn't found it particularly important. That part is corrected now anyway.
Power supply is 750W, running Windows 10 Pro. Drives are all Samsung, 1TB 850 Evo, 1TB 860 Evo, and 2 1TB 970 Evo.
If there's anything else you may find relevant, please ask.
The issue still seems to occur despite the change of the drivers (did a clean install just to be sure since it offered the option), though like I said, this is not an issue that manifests if I were to connect to the VMs via RDP. The machines themselves seem quite responsive, and would connect via RDP in the expected time.
The issue is merely when using Hyper-V's Manager console and connecting directly to the machines without RDP.
Now, what I did find is that when the machines were having a greater delay being connected to, a WMI service would pop up and stick around for a bit, then disappear or just consume an insignificant amount of CPU and being shuffled all the way down to the list. In sheer curiosity because I figured it could do no harm, I restarted the Windows Management Instrumentation service and the delay promptly went away.
If nothing else, I have a viable workaround now since I don't need to open and close the windows that frequently, though at this point if anyone could tell me if this is anything known with Hyper-V/Windows experience in general or not would be appreciated.
Thanks, cmdr001. What looks weird to me is that core 1 is running 4150 MHz and all the rest are running 2200 MHz. Is W10 dispatching to all 12 cores? Where did you get your W10 to install? I hope it is not a clone of another system. Please open your Device Manager and expand Processors and post a screenshot. Here is my 2990WX:
It shows 64 threads. Yours should show 24. Thanks and enjoy, John.
Machine was idle right after boot up, so didn't seem particularly odd for me. I see the reported core speeds shifting as there's more and less load, and I see varying load across 24 threads. Checked the device manager, but as expected the 24 are there.
The Windows 10 was prepared from the Media Creator. It's a new system completely different from everything I had before so I wouldn't really dare to try and salvage the installation of my previous machine.
