Nice program - it's helped me a lot!

[KirkH420]

So I thought I'd offer you a suggestion, you may find this useful. I unplugged my laptop and then sifted though the Event Viewer until I found a related event. Windows triggers an event record whenever the AC adapter is plugged in or unplugged. This can be used to fire your task again rather than only doing it when somebody logs in.

Simply add another Trigger.
Begin the task: On an event
Basic
Log: System
Source: Kernel-Power
Event ID: 105
Click Okay

Change to Conditions Tab - In the "Power" section
Enable checkbox: Start the task only if the computer is on AC power.
Enable checkbox: Stop if the computer switches to battery power.

These might help too

Settings Tab -
Enable checkbox: If the task fails, restart every 1min
Attempt to restart up to: 3 times

I decided to play around with it because once and a while, I was finding that my battery would start charging past 60. Anyway, thanks again for the useful program!

[lampuiho]

Thank you for the contribution. Yes I was aware of this method but I have disabled all logs to prevent writes to the disk. I can add this to the readme if you'd like.

[dnmTX]

Yes I was aware of this method but I have disabled all logs to prevent writes to the disk.

@lampuiho your .exe doesn't log anything to the disk this way. The log is from Kernel-Power,which is standart and logs those events when you plug and unplug and the schedule task just monitoring,and if the event occurred,acts accordingly.
What @KirkH420 suggested here is the way to go and would advise you to implement it 👍

[lampuiho]

@lampuiho your .exe doesn't log anything to the disk this way. The log is from Kernel-Power,which is standart and logs those events.

As I mentioned, yes, I am aware of it see pic. I have disabled all loggings. For System, Application and Security, I disabled those individual events in registry. path is something like "Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\WMI\Autologger\EventLog-System{GUID}"

[dnmTX]

Oh,i see now what you meant and sure,it make sense in your case where you have all logging disabled(most of us keep those enabled) but on the other hand even if you implement what @KirkH420 here suggested,on your end it just won't get triggered and definitelly will not waste any resources if you worry about that. On our end will do what is suppose to.
Up to you though 👍

[lampuiho]

if you implement what @KirkH420 here suggested,on your end it just won't get triggered

There is nothing to implement. You just follow @KirkH420 instructions and add that task in Windows Task Scheduler if you would rather have the exe run when that event is fired.

[dnmTX]

I already have but i'm also trying to help here and make everyone's experience better when they using your .exe.
How would the next person know that he/she has to add additional event to the schedule task(your .xml file)?
Chances that they'll look at the issues here first and read them are slim to none.

if you would rather have the exe run when that event is fired

The suggestion here is just a small enhancement in addition to the original schedule task. What it does is it stops the task when you unplug your laptop(when the laptop is unplugged,why would you want that task to still run in the first place) and start the task back when you plug it back in.

[lampuiho]

I already have but i'm also trying to help here and make everyone's experience better when they using your .exe. How would the next person know that he/she has to add additional event to the schedule task(your .xml file)? Chances that they'll look at the issues here first and read them are slim to none.

Added it to readme. Also, there is no need for the stop event. The program doesn't keep running in the background like the stupid service provided by ASUS. Services get to start earlier than Task Scheduler tasks though. I may have to install Windows dev kit to write a service that stops itself after the task is finished.