Also, disabling "allow this device to wake computer" seems to do absolutely nothing, probably because that setting only applies to true S3 sleep, not the fake S0 sleep that's occurring.
Asus Laptop Wakes Immediately After Sleeping
I don't think the laptop was always like this (though it's barely been a week with it), but recently, when putting the laptop to sleep, it immediately wakes up, almost as if it never went to sleep at all (like hitting win+L, except the screen turns off for a little bit). I've done quite a bit of googling to try and find solutions, but no dice so far. Here's everything I've done/everything I know:
- Event viewer records both the sleep and wake events. The sleep event looks normal ("sleep button pressed" or something along those lines), but the wake event is strange (woken due to "reason: mouse input"). This makes no sense because:
- I have disabled all hardware devices from waking the computer; when running the powercfg command to list all devices that can wake the computer, it returns "NONE"
- There was 1 time where instead of reporting the wake reason as "mouse input", event viewer reported waking was caused by "reason 44", no idea what that is
- The powercfg lastwake command also isn't helpful, and just reports that no wake events have occurred
- I used powercfg to check for wake timers, while there was one related to windowsexperience whatever (which disappeared after removing all live tiles from the start menu), the disappearance of the timer does not seem to have fixed my problem
- I used a powershell script (can't remember which, exactly) to list all task scheduler tasks that could wake the computer, none of them were enabled
- I have tested the sleep behavior with Remote Desktop connections enabled and disabled (N/B the laptop shipped with a Windows 10 Pro key), no change either way
- I've tested the sleep behavior with magic packets and WOP enabled and disabled on my Wifi (ethernet not connected), no change
- I have tested the sleep behavior with MS PowerToys keyboard manager enabled and disabled, no change either way
- I have updated my bios to the latest version supplied by the laptop vendor, no change. Also checked Windows update, no updates available
- I have restarted my computer multiple times, no change in behavior
Any tips that I've not already tried would be greatly appreciated, thanks.
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.
12 answers
Sort by: Most helpful
-
Anonymous
2021-10-28T01:03:06+00:00 -
Anonymous
2021-10-27T04:05:26+00:00 Here's Admin events log, system info, and System events log as a bonus: https://1drv.ms/u/s!Apk3fKfsIFuxmX2mF6aYisJ2Dx5P?e=vsD6m0
-
Anonymous
2021-10-27T03:29:47+00:00 Can you provide the following information which may help determine any issue(s):
Windows Key + R > type msinfo32 in the "Open" box > OK > File > Save > then save as an .nfo file
Then make the resulting .nfo file available via a public folder on OneDrive or similar site.
Also, can you do the following:
Windows Key + R > type eventvwr in the "Open" box > OK > expand "Custom Views" and then right-click "Administrative Events" > select "Save all events in Custom View As" and save as an .evtx file
Then make the resulting .evtx file available via a public folder on OneDrive or similar site.
Here's a link on using OneDrive:
-
Anonymous
2021-10-27T02:07:27+00:00 Just tried the clean boot thing, with all non-Microsoft services disabled (and with Microsoft services disabled) the same issue occurs, though with slightly more variation in the event viewer reports: event viewer shows wake within a minute of sleep, with the same causes ("Mouse Input" & Reason: 44), as well as a new one (Reason: 50).
-
Anonymous
2021-10-26T18:59:38+00:00 Hi,
Can you try a "clean boot" and see if it makes a difference:
https://support.microsoft.com/en-us/kb/929135
If a clean boot does resolve the issue there is a section in the article "How to determine what is causing the problem by performing a clean boot".
Reset the computer to start normally afterward.
As a general precaution create a System Restore Point prior to initiating a clean boot.