Windows 10: Power-Troubleshooter not triggered on wake from sleep

Hi, I have been researching on how to launch a simple command prompt command and then pipe the results to a text file whenever my laptop is woken from sleep.

I am using Task Scheduler and triggering the action based on
Log: System
Source: Power-Troubleshooter
Event ID: 1

However, the action isn't being triggered and when I checked Event Viewer, I realised that Power-Troubleshooter with an Event ID of 1 doesn't seem to be triggered on every 'wake from sleep' event. Is this supposed to be the case ?

Any alternatives to trigger the action will be greatly appreciatred.

:)

 

ShutDown button in desktop (Win-10)

Sechedule Wake up doesn't work with sleep using the command line.

But Its work when sleep trigger by original power menu

 

Windows 10 Lock on Sleep

"Sign-in options" => "Require sign-in" => "When PC Wakes up from sleep"

Control Panel\All Control Panel Items\Power Options\System Settings => Ensure all relevant options say sleep.

Control Panel\All Control Panel Items\Power Options\Edit Plan Settings =>"Change advanced power settings" => "Power Buttons and Lid" => Ensure all relevant options say sleep.

I think the problem here is that Microsoft is answering how to ensure password is required when the computer is in sleep, however they fail to mention that there are actions that intuitively would trigger sleep, such as closing the lid of a laptop, that
don't necessarily trigger sleep without setting Windows to do so.

 

I did this type of thing on Windows 7 years ago. And like you, I found that the Power-Troubleshooter event wasn't always getting generated.

IIRC, I had to trigger on a Kernel-Power event too. I just checked my Event Viewer, and it looks like Event ID 107 of Kernel-Power in the System log is generated whenever the system resumes from sleep. Try triggering on that event as well.

I haven't tried writing a script like this on Windows 10 yet though. Please let me know if it works. I may need to do it myself real soon.

 

Currently, I am using Kernel-General with an event ID of 1 to trigger the action. It seems to be working 100% *Smile

 

You trigger on system time synchronization with the hardware clock? In my Event Viewer, I see other events of that type that have nothing to do with wakeup:
The system time has changed to ‎2017‎-‎01‎-‎17T14:23:02.021000000Z from ‎2017‎-‎01‎-‎17T14:23:02.021956600Z.

Change Reason: An application or system component changed the time.
I wouldn't want to trigger on that.