Re-installed Win 10 after botched update, now it wakes up at 3 am every day.
Cleaned Task Scheduler from what (IMO) was not needed. Still wakes up.
Checked Power settings, don't see anything wrong. Minimum processor power was 5%, changed to 0%. Still wakes up.
The last log - below. Bottom entry is when it woke up last time.
Hi almot109.
Next time it wakes up could you run this command at command prompt(admin) or powershell
powercfg -lastwake
If should give you info on what requested last wake.
See Wake Source in Windows 10 Windows 10 Tutorials
Last edited by Brink; 25 Mar 2018 at 11:31. Reason: added tutorial link for more info
Lastwake didn't help because after it had waken up at 7am, it went to Sleep again 3 hours later. So Lastwake only shows this last press of Power button - when I woke it up again.
Tutorial on Wake Source, results: Unknown Wake Source.
System is set to Hybernate when I press Power at the end of the day, - for faster booting.
Log - below.
Any chance you can catch it a 3:00 am?
Additionally I think one night I would boot it clean and then monitor behaviour to determine if this is windows or a third party.
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
It's not easy to catch it at 3am, there seems to be no fixed time. Yesterday woke at 7am.
About clean boot. To troubleshoot, - since I don't see programs that refused to install or didn't run properly etc - it looks like I'll have to enable Startup items one by one, every day, to see what is causing it to wake? Ouch.
PS. Today it didn't wake because I shut it down completely, by holding Power button for a few seconds - for some reason it refused to Hibernate. After this, all the icons on the desktop were re-arranged. Well, the machine is 7 years old...
Perhaps try Nir Sofer's TaskSchedulerView? This will list all scheduled tasks and their trigger times:
Make sure you download the version appropriate for your system - both x32 and x64 versions are available. Once unzipped, right-click on the executable and use Run as administrator.
Hope this helps...
Thanks, RickC. Nirsoft is nice. There was indeed a mysterious "Device" scheduled at 3am, and half a dozen other things.
Being self-taught, I don't recognize most of them, so just disabled whatever was scheduled to run in the night. I know many people just let machines run 24x7, but I'm old school.
Ideally, would prefer to modify Triggers for those tasks to "Specific time IF Logon = Yes", so it would only run when machine is On. Probably can do this by locating the app and changing properties. Later. Maybe. If disabled apps give me troubles.
Quote
