Again me with the Task Scheduler.
Under Windows 7, tasks behave according to the rules stated in the link … tested and it works.
Under Windows 10 (Pro v1809 with all the updates) … well not exactly.
First of all both tasks (under Windows 7 and Windows 10) are the same.
The Task is created like this:
If I copy some files at 14:15, and move the mouse at 14:15, and type on my keyboard at 14:15 and then leaved my computer at 14:15, I would expect for the task to be executed at 15:15 and not at 14:30, or am I wrong?
The task always executes at 14:30 (if I leave my computer at max at 14:25) or it doesn't execute at all (for that day) if I'm working at my computer at 14:30. WTF? If I recreate the task at the computer with Windows 7, everything works just fine.
This was tested on 2 different computers with Windows 7 and 3 different computers with Windows 10. Numbers here doesn't matter, because the same thing happens at 02:00 with idle time of 15 minutes and wait time of 2 hours. They are here just to paint the picture what is happening.
I even thought this was connected somehow with the "working hours" in Windows 10 which is set between 06:00 and 00:00 so I moved the task at 14:30 … yeah, this didn't help.
And yes, I do understand that Windows 10 sees the idle time differently than Windows 7 but that would mean the task would be executed later not sooner and especially not at the time when the trigger was set.
Would be interested if someone could confirm this behavior and maybe provide some explanation why this is happening.
13.05.2019. – I can now definitely confirm this. Today two of my friends confirmed this issue. This has to be a bug in Windows 10 v1809 (maybe for earlier versions also but I don't have access to those). Also I can confirm that this works without the problem on Windows 7 machines. Great, just efing great. Will post this question on Microsoft forums.
15.05.2019. – Managed to test this on Windows 10 v1607 … same thing happens. How is it possible that no one has yet (in over two years) reported this issue to Microsoft? This can't be the way it's meant to behave, this is a clear bug in Windows 10.