Seems to be working fine for me, I have my settings like this:
I prefer that there is choice over the timings now, unlike the fixed 4 hours there used to be. I also enable the Hibernate option in the power menu,
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I upgraded my SP3 to Windows 10 (not enterprise). The unit no longer goes into hibernation after 4 hours of connected standby. With Win 8.1, the unit would hibernate after 4 hours of not being used. I disabled Wifi during sleep, which decreased the battery power usage during sleep, but it did not solve the hibernation issue. I liked the previous hibernation after 4 hours because the unit can sit in my bag for 8-9 hours at a time without being used.
Has anybody else experienced this and found a solution?
Thanks...
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Seems to be working fine for me, I have my settings like this:
I prefer that there is choice over the timings now, unlike the fixed 4 hours there used to be. I also enable the Hibernate option in the power menu,
Glad it's not me with this same issue. Clean install of windows 10 after performing the upgrade has broken the 4 hour hibernation even after I set a timer.
Will be waiting for a fix I guess.
I have the same issue
When will Microsoft provide a fix
Nothing you mentioned helped. Interestingly, while the unit is plugged in and charging, it will "doze to hibernate" around the 4 hour mark. But not on battery- which is when it would be more helpful for it to hibernate! My settings are identical for "on battery" and "plugged in". I am still not sure what the issue is, but SP3WIN10's response makes the most sense. Essentially saying stop wasting your time and either roll back or wait for an update that fixes this, if it ever comes....
thanks
yes
I can do it manually
Hope Microsoft is fully aware this issue and provide solution as I found this function quite useful.