6 months late, but just in case, because I don't find the topic mentioned anywhere...
Micro$oft sometimes adds rever$e logic to the process: bootup settings in 8- forward include something called 'fastboot', the effects of which I'm seeing along this thread.
One google quote is short and to the point:
". . . shutdown / bootup in Windows 8 and newer are by default not real shutdowns and bootups, but rather a hybrid "log off and hibernate" kind of thing. What most folks don't realize . . . is that the Hybrid/Fast Boot logic can cause problems. For one thing some parts of the system are not freshly restarted, and for another it's (possible) the file system (can) actually be left in a dirty state."
So, this refers to the process of using 'Shutdown' and then restarting, which it doesn't
. It keeps part of your previous kernel session on tap while it recycles other overhead, and it goes fairly quickly if '/fastboot' is on. It's apples and oranges to the 'Restart' choice, which is now actually the closest to a full down cycle, and therefore quite a bit slower as this thread points out.
Of course, in 7 and previous we were trained to use 'restart' to get back onboard sooner. Shutdown meant shutdown, and restart never went cold .... sort of the opposite.
My only guess at the MS logic is that most people typically do a 'shutdown' and go to bed. Then in the morning they 'boot up' and, since it seems to go really quickly, they can conclude the newer OS must be much fa$ter than the old. Cold-cycling reveals the true
footprint of that boot.
To be fair, we understand most of the time the OS keeps everything in order, on balance. But obviously, it can give your troubleshoot a quick boot. That preserved kernel session may have driver pointers that are honored according to its previous
hardware enumeration. And then there's Superfetch, by which the OS keeps parts of your most-used programs in RAM, even through a 'warm reboot' (even in win7 [even Prefetcher in XP]). I'm sure many know this. The issue is, where is the cold boot, really?
I'm no expert. These things google well, so vet this if it seems useful. I just want to raise a flag here where troubleshoot happens -especially re vid drivers, because I haven't found any mention and I see threads about doing a cold boot that wouldn't be. And BTW, for a really
complete blankout . . . you have to disable fastboot, shut down, pull the plug (and battery
), and then hold down the power button for 5-10 seconds to bleed it dry. Only then can you know you've done your best to not track something in on the bottom of your boot.