I would not have any idea as to how to change the behavior, I check my taskbar
Hmm, it does not add up. It simply has nothing to do with harddrive which would be more prone to timing signal and breaking havoc there should not affect system time? I think the assumption has to be false somehow (no offense) :flower:
Fwiw, A bare essentials fix windows 10 primer:
For any FUBAR windows that will boot to windows one way or the other, just do an upgrade to the same version, it will actually let you do that and in that you basically have your old familiar repair install. I have not yet done this for the 1607 edition, but unless they changed it...
Then for registry errors like BAD_SYSTEM_CONFIG and other 'interesting' messages related to registry, still causing your windows to not boot, windows actually has you covered if system restore is enabled (I 'believe' it to be linked to that, never actually checked, only found that it is not always present). If you find the repair-boot from install media to fail on your restore points or otherwise, look at this path:
Notice the subfolder 'RegBack'? In there you will find a previous version of all registry databases found in the parent 'config' folder which should be
The only thing apart from this is your user NTUSER.DAT, but you are logging in before that kicks in and so it should not be a reason for windows not booting.
Make a backup of the ones in the config folder, then delete them from the original C:\Windows\System32\config' location .Now copy the ones found in 'C:\Windows\System32\config\RegBack' to 'C:\Windows\System32\config', reboot the system and see if it worked.
Now that was two 'last resort' solutions which would probably apply to your scenario where the last one can be performed only by command line found in advanced recovery options or by hooking up the HD in another computer/laptop.
On a general scale though, you would want to act as much as possible before it gets to this. Before large updates and if you notice slow behavior, run this from an administrative command line:
If it is unable to repair, run this:
DISM.exe /online /Cleanup-image /Scanhealth
If it says it is repairable, run this:
DISM.exe /online /Cleanup-image /Restorehealth
The DISM log file can be found at C:\windows\Logs\DISM\dism.log
Personally I have never found sfc /scannow to fix anything, but it is a recommended step. DISM on the other hand is a great addition to later OSes which you should take time to learn.