I have brand new computer. Has done this ever since i bought it.
Sleep not working since 1903 update. Support said that it was an issues with update. Has it been repaired?
Has the glitch with 1903 been resolved? MS support analyzed my system and determined that it was an issue with 1903. I was told that this was a recurring glitch effecting many other users and was advised a rollback until the issue was resolved.
Windows for home | Windows 10 | Sleep and Power on, off
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.
43 answers
Sort by: Newest
-
Anonymous
2020-03-12T12:52:18+00:00 -
Anonymous
2020-03-12T12:44:59+00:00 I have come to learn that Microsoft doesn't care.
As I have previously reposted my issue of the computer not going to sleep or staying asleep was to disable all wake timers.
My computer will now hibernate once I close the lid after a set time.
Microsoft has so many other issues to deal with as I do not think this will ever get resolved.
-
Anonymous
2020-03-12T12:41:35+00:00 Did not experience this at all. Try rebooting computer from a back up.
-
Anonymous
2020-03-11T01:42:58+00:00 I am so ready to try anything, its so frustrating it goes to sleep on me every 2-3 minutes if mouse not moving or typing.
-
Anonymous
2020-03-10T20:33:30+00:00 Since the 1909 Windows Update (KB4517245) my ASUS Q550LF laptop goes to sleep "properly" then crashes when waking up, resulting in an Event 6008 followed by an Event 41, and the subsequent auto reboot. All work is lost. This happens every time I close my laptop and reopen it, every time I manually put the computer to sleep, and every time the computer automatically goes to sleep (which I obviously disabled after repeatedly losing progress).
I've created a feedback with the Windows Feedback Hub - go there and upvote it to get more attention: https://aka.ms/AA7mww7
My feedback includes evidence that the issue stems directly from the 1909 update. It appears a lot of people have this problem but not a lot of people are actually submitting the issue to Microsoft.