3 ms·
It only does that if the machine has been on for 24+ hours or so. Shut it down instead of putting it to sleep and you won't have this problem.
by tokenizerrr 9y ago
It only does that if the machine has been on for 24+ hours or so. Shut it down instead of putting it to sleep and you won't have this problem.
- cesarb 9y agoWasn't it Microsoft itself who deemphasized "shut down" in favor of "sleep", by moving the shutdown command to a hard-to-find place? The intention was clear: the computer should be "always on", and a full shutdown should be done rarely, if at all.
- tokenizerrr 9y agoI'm not sure what you mean, both are in the exact same menu.
- sevensor 9y agoI posted a brief rant elsewhere in this thread about a notebook computer that was basically unusable because of Windows. It had been configured at the factory so that the power button didn't actually turn it off. Because it was used infrequently, and because the power button caused it to sleep instead of powering down, this computer always had a dead battery. This particular machine had no sleep indicator light, so to all appearances it was truly turned off. I'm angrier at Microsoft than usual today.
- WalterGR 9y agoIt sounds like the manufacturer caused the problems and not Microsoft.
- sevensor 9y agoTrue, this post did a poor job of making my case against Microsoft. My other post in this thread goes into more detail. With regard to power in particular, I'd argue that the "power button means sleep by default" is a terrible idea. By default, the power button should put the system into a state where it's not drawing an appreciable amount of current. Sure, Asus compounded the problem by not providing the computer with a sleep indicator LED, but Microsoft gets a lot of the blame for pushing the idea that we should suspend rather than power off our computers. I can only imagine that they wanted to mitigate their ludicrously terrible startup times.