I am having some trouble with Windows Task Scheduler. The problem occurs in Windows 2016 server, and I was able to reproduce it in Windows 10 Home edition. The problem does NOT seem to occur in Windows 2012 server.

We set a task to run every 15 minutes. For the sake of argument, let's say I have it starting at 1 PM. Under the "triggers" tab, we have the task expiring at 2:01 PM (so it should run 5 times - 1:00, 1:15, 1:30, 1:45, and 2:00). However, when 2:15 came around, the task still ran.

Is there something I'm missing with the "expire" setting in task scheduler? I know Windows depreciated some features of the scheduler, so maybe we ran into one of those, but I couldn't find a definitive answer online.



Edit: I've attached some screenshots of the error being reproduced (this one is just a once-per-minute task expiring after a few minutes, but still running).

Triggers - start at 11:20, expire at 11:23

Action - run test.bat, which just echoes date and time into a text file

Settings, if that's important

Results - still running at 11:25

  • Welcome to SuperUser. The 2016 Task Scheduler I'm looking at doesn't have a way to enter "1 hour and 1 minute" for the expiration. Rather, the expiration is a date and time value. Can you edit your question to include a screenshot and/or the verbose output from schtasks.exe? That might point us in the right direction. – Doug Deden Apr 11 at 20:36
  • Edited. Thanks. – Charles Yu Apr 12 at 15:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.