From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Sunday, December 30, 2018 8:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Highbernating windows 10
On Sun, Dec 30, 2018 at 10:03 PM, Kwork wrote:
why do you not recommend fast startup to be checked?
There are a couple of reasons, the last of which is the most important:
1. When one does a "shut down" on a system, what meaning does that generally carry? Most people think shut off/down, completely, and starting from scratch when it is powered up again. Fast startup directly violates that concept.
2. It seems to me that it is completely backward that Restart causes a complete shutdown, sets a timer, and fires up the system from scratch while Shut Down does not.
3. Fast Startup is a special form of Hibernation. Under normal Hibernation both the operating system state and all user states are written out to disk and reloaded when the system is powered up again. Fast Startup causes only the operating system state to be written out to disk in a special hibernation file and that is reloaded when the system is powered up again. As this state gets written out, over, and over and over again over a span of days, weeks, and months there will be corruptions that occur in the hibernation file. Almost invariably, at some point, a collection of little corruptions form a confluence where the entire system becomes unstable when it is restarted. I have witnessed this on two occasions myself, and the behaviors displayed were so bizarre that I simply could not figure out what the cause was, initially. Eventually, after a forced Restart rather that Shutdown/Power Up cycle, everything went back to normal.
I just cannot see how a few seconds to a minute or two of time saved at system start time is worth having to deal with the probability of this sort of problem. All the more so if a system has an SSD as the OS drive rather than an HDD. I would far rather have a complete, fresh, start where Windows 10 is loaded again from disk as it is when Restart is used than to have it come back from hibernation again and again. This is all the more so since I do not power down my system frequently, preferring to allow Windows 10 to have the "inactive hours" to do the updates I delay it from doing if they get configured during active hours and require a system restart.
When I shut down a system I intend, and absolutely want, it to shut down. I do not want it to hibernate the OS state. If I want hibernation I will intentionally choose it, and I want the user state(s) to be saved, too.
--
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
A great deal of intelligence can be invested in ignorance when the need for illusion is deep.
~ Saul Bellow, To Jerusalem and Back
