I read a number of articles on Fast-Startup and the differences between Sleep, Hibernate and a full shutdown. So I think I understand the basic concepts. Currently I always shut down my pc at night and do a normal reboot in the morning. During the day I let it run and don't bother with either sleep or hibernate. I am wondering if I should change my approach and also if fast-startup should be part of this? In one thread I read today that being able to delay feature updates for extended periods relies on fast start-up as as only a full restart will install new updates. If you rather wait for bugs to be dealt with instead of rushing out and immediately updating, then that would be a good thing. I did notice a few threads here stating that fast startup is one of the first things being disabled but to me it was never quite clear why? I am using SSD and Macrium and IfW for imaging in case that is relevant.
Fast startup is one of the things I disable straight away on any of my machines. Why? because when I select shutdown from my machine, that is what I want it to do. With Fast startup enabled it's more like a pretend shutdown, it just closes its eyes and keeps things ticking over way in the background so to speak, so that when folk turn their machine on they say''wow, that was a fast boot!!''
I actually like the concept of Fast Startup, the desktop is loaded almost instantly after POST. But I wanted the 12 GB or so of disk space in the hibernate file so I disabled it in Control Panel and then ran cmd to shut off hibernation. Then I went and disabled various un-needed startup services like Atheros and HD Audio. So now, the desktop loads in around 10 seconds on here, which is a decent compromise.
The problem with "Fast Startup" is that from what I have found, it does not start any faster. At least not enough to make it worth leaving enabled. It also makes it take much longer to shut down since it is writing your current state to the disk. Over time it has the same problems as putting your PC to sleep. Things like sound that stops working. USB that functions incorrectly or not at all. Various other stability issues. For a while Norton was having issues with it enabled as well as a few other vendors. Microsoft was forcing it back on during their twice annual updates but fortunately they have stopped doing that. It's one of those things that seemed like a good idea that just doesn't work. Links to validate my claims: https://community.norton.com/en/forums/windows-881-or-10-and-fast-start-feature https://www.terabyteunlimited.com/ucf/viewtopic.php?f=2&t=427
There is an advantage to letting your computer sleep at night, rather than shutting it off: It gives Windows time to do maintenance tasks without bothering you. By default, it tries to do them in the middle of the night. So I recommend letting the computer sleep at night (lid up if laptop). And first thing in the morning, do a proper reboot. A proper reboot means clicking on restart, not shutting down and then letting fast boot bring up the system. As other posters mentioned, the computer might wake up with a headache due to fast boot.
I thought the main advantage to avoid any improved speedup via hibernate sleep etc was to make sure that a virus in a PCs memory (and not on the HD) is killed with the lack of power.
Same here as the result of the 1909 Feature Upgrade. I have fast startup enabled, have reset power settings, etc. etc. and still no quick boot at power up time. Prior to ver. 1909, fast startup did work if so enabled in power setting options.
Yes, I'd also read about issues caused by Fast Startup, it seems to be at the root of some problems like certain drivers failing to load and whatnot. Installed a new C drive nvm-e very recently and cleanly installed Windows v. 1909 and when I booted, it was like flipping a switch, that's how fast it was. But I would not want to blithely boot one day and then see the dreaded blue screen or "Windows needs to be repaired." I have enough on my plate as it is.
I leave Fast Startup enabled as it's not causing any issues. But I don't care about startup time, as I usually go at least a few weeks without rebooting.