Has anyone noticed slow start-up times on a windows host? At startup I am eventually greeted cheerfully by a spinning circle on a black screen that does little but mock me for a couple of minutes. Eventually the system deigns to grace me with its presence however.
This is only while hyper-v is enabled and irrespective of whether SVM is enabled in BIOS or not. (So no hyper-v + SVM: ON -> “fast” boot, hyper-v enabled and SVM: ON -> gleefully mocking spinning circle of doom) .
100% reproducable even across different windows (re-)installs and graphics drivers, leading me to believe this could be ryzen related? Clean booting does nothing. Safe booting does fix it, but I assume it simply circumvents hyper-v?
I guess my question is: is this a known issue (I cannot find it) and if it is not, do you think changing my motherboard might improve things?
Say from b450 carbon ac to x470 taichi?
Help and mockery very much appreciated
I have now done the following:
unplugged every device except mouse and keyboard. This includes all storage devices except one, as well as my sound card and my second monitor.
- Ryzen 3700x
- b450 pro carbon ac
- 32GB Crucial Ballistix Sport LT V2 Dual Rank grau DDR4-3000 DIMM CL15 () (BLS2K16G4D30AESB)
- a hd 6870 GPU
now the GPU is simply to rule out my main GPU as a source of trouble, which is a GTX 670. With this setup, I should be able to rule out NVIDIA or AMD drivers.
SVM Mode “Enabled”
(probably not of interest but in the same sub-menu:
Global C-State Control “Auto”
Cool ‘n’ Queit “Auto”
P-State Adjustment “PState 01”
PSU Idle Control “Auto”
With this modified barebones setup I reinstalled Windows from scratch again, deleting all files on the last remaining SSD (Samsung),
updated through the Windows check update function and rebooted a couple of times to check start-up times, which seem fine. I then activated the Hyper-V functionality and the problem appears again.
(long black screen with a spinning circle before login screen but after post, obviously)
So for posterity and to save someone else the trouble:
The problem must either be windows, ryzen 3000 or b450 dependant.