E
Eric G (FCOA)
Guest
Windows 10 (build 1809) runs a Scheduled Task with multiple "on an event" triggers once for each defined trigger, regardless of whether the other event(s) have occurred. This does not occur in Win7 (we haven't checked other Win10 builds).
This undesirable behavior was seemingly confirmed by removing "on an event" triggers, and confirming that the run count did indeed match the number of defined triggers. It has also been independently verified by another source per our inquiry at Bug: Windows 10 Scheduled Task with Multiple Event Triggers. In the interim, our workaround has been to "...not start a new instance" if the task is already running, but this has some pitfalls to the "action" (a script) we're running.
Does anyone know of a hotfix or KB article that addresses this issue, or have any suggestions other than splitting the Task Scheduler into multiple records with one trigger defined per task?
More...
This undesirable behavior was seemingly confirmed by removing "on an event" triggers, and confirming that the run count did indeed match the number of defined triggers. It has also been independently verified by another source per our inquiry at Bug: Windows 10 Scheduled Task with Multiple Event Triggers. In the interim, our workaround has been to "...not start a new instance" if the task is already running, but this has some pitfalls to the "action" (a script) we're running.
Does anyone know of a hotfix or KB article that addresses this issue, or have any suggestions other than splitting the Task Scheduler into multiple records with one trigger defined per task?
More...