Sleep/Hibernation wake-up issue

Greetings,

Using HP desktop with Windows 10. Latest Fall Creator Update installed.

After the latest update my machine wouldn't wake up after sleep mode. The screen is blank although I can hear "rumbling" in the background as if the hard drive were indeed on but I see nothing. I have to shut down manually and restart. The Power Setting remained on Balanced since I first purchased the computer last year and it always woke up. I tried changing the power options to "put the computer to sleep: Never" and that works. But obviously this is not a solution, just a delay, and I don't want to stay with this "never" option. I have also read that one can turn off Hibernation but again, to my mind, this not a preferable option to the existing problem.

Your help is greatly appreciated.

PS. Oh, and what does "Post a Poll" mean on this web page?

There are many threads on this problem. Start by turning Off Fast Startup (this disables hibernation, by default). Turn On your preferred Sleep settings and test for a couple days. If this fixes it, you can turn off Hibernation in a command prompt (admin) to delete the hiberfil.sys taking up space by typing powercfg -h off then Enter. I know this means Shut Down vs Hibernation to save power but I've had this setting for a long time, as do many others, and no wake issues anymore.

mrgeek said:

There are many threads on this problem. Start by turning Off Fast Startup (this disables hibernation, by default). Turn On your preferred Sleep settings and test for a couple days. If this fixes it, you can turn off Hibernation in a command prompt (admin) to delete the hiberfil.sys taking up space by typing powercfg -h off then Enter. I know this means Shut Down vs Hibernation to save power but I've had this setting for a long time, as do many others, and no wake issues anymore.

Thank you for your quick reply.

I will attempt your suggestions. Forgive my naivete but I want to understand the logic here:
1. Has some kind of corruption occurred with my system? If so, simply turning off Hibernation seems to skirt whatever the real problem is, not fix it.
2. If, as you mention, turning off Fast Startup disables Hibernation and the problem does not recur, why then should I follow up and delete the file hiberfil.sys? Why not simply keep Hibernation disabled?

Finally, I had asked in my original post what "Post a Poll" meant.

Thx, once again.

Does anyone else have any comments/suggestions with respect to the questions in my post above?

Thx for helping me out.

The Windows 10 Fall Creator's Update has caused problems, which may look different depending on system, for many users.

I have a Modern Standby system and the problems with shutdown and hibernation have made the system almost unusable and I have rolled back to the previous build. Microsoft has told me my system is not compatible with the upgrade, which seems strange for a system only 7 months old....

Hoping for a fix from Microsoft shortly although they are not acknowledging any problems with the Build but are blaming it on OEM systems.

I think these problems go with changes made for Modern Standby or InstantGo systems, but I cannot verify. It is interesting that Fast Startup uses a hibernation file and the Hibernation process seems to be broken.

And no, corruption on your system is not the problem.

Thx for the quick and informative reply. And I appreciate you answering my first question. The second question concerns mrgeek's suggestions (2. If, as you mention, turning off Fast Startup disables Hibernation and the problem does not recur, why then should I follow up and delete the file hiberfil.sys? Why not simply keep Hibernation disabled?) and remains for your consideration.

Glad to hear that my system is ok and that there "might" be a fix soon.

mrgeek may have some reason of which I am not aware but I did not need to turn it off on my upgraded system.. The system would still not hibernate when I asked it to.

My system is OK if I do not upgrade to the new build. Not being to upgrade a 7 month old system seems a little ridiculous.

If Microsoft truly believes it is not their problem, there may not be a fix. I have to wonder how many testing groups broke down for the build to be released, probably several. There is a possibility Microsoft was aware of the problem but released the upgrade anyway... Windows 10 is a Beta OS, right

Many thx for taking the time to detail the issue and good luck with future upgrades to your new system Saltgrass. No end, it seems, to Microsoft realizing the existence of these kinds of problems and doing nothing to make a fix available. How many complaints does it take..... lol.

Thx, again.

Saltgrass said:

Windows 10 is a Beta OS, right

Correct. That OS is in an eternal beta state, with some pieces of software that come with it barely even reaching that level. As a matter of fact, if you look under the hood at the way they have grafted on stuff using a duct tape and bale wire approach to what already was a Rube Goldberg contraption of an OS, it's a small wonder anything's working at all. That's perfectly fine with Microsoft, since the people using it seem fine with it, too. On the other hand, if you need to get real work done on a PC, you should use a mature OS. In that case your only choice is Windows 7, if you also need to use industry-standard software.

Sylvan said:

PS. Oh, and what does "Post a Poll" mean on this web page?

All explained here:
Reading and Posting Messages