Task Scheduler [Server 2019]: runs tasks every week instead of every 2nd week

Question

On Windows Server 2019, I have a weekly task which is set to "Recur every 2 weeks". It actually runs every week. The "next run time" shows correctly that it's scheduled to run again in 2 weeks but when it comes next week which it's supposed to skip it runs anyways.

Answer 1

In my case what I am looking for is that the MISSED tasks are executed. I already checked the option "run task as soon as possible after a scheduled start is missed" but it only works in ONE TIME and sometimes DAILY. In weekly or monthly it does not work. It also doesn't work well if you choose a day of the week.

This failure seems to have been like this forever. In 2018 they released a update that has improved somewhat but continues to fail in other cases.

The solution I use is to put it in ONE TIME and activate REPEAT TASK EVERY which can be selected or DIRECTLY WRITE whatever we want in the box. To select that the task runs on a specific day of the week, I put in START any date before of the desired day of the week and that it repeats every 7, 14, 21, 28 ... days indefinitely, always in multiples of 7 days to make it the same day of the week.

Answer 2

I have the same problem for at least 4 weeks ina row. I have 1 scripts which has to run every 4 weeks on monday. Every week with other parameters.
When the script is done, it sent a email. Every monday I get a email from the correct script, and also from the previous one.
Every script is set an a "weekly" schedule of 4 weeks, on monday, with different starting days (also on monday). It is configured for windows 2019 (if this makes any difference).
I am doing this on a full patches 2019 server.
In the task schedular window, I see the correct planned dates and times (next run time), but that is NOT what the task schedular is doing. After the scripts run, this is also reflected in the "last run time". It will show the dates it run (which is correct) but it runs on the wrong dates.
Very strange, that the "next run" is always correct, but it does not follow its own schedule..... why ?

I changed every schedule to run daily, every 28 days. I hope this will fix the problem. If it does, the weekly trigger interface is broken and should be fixed or removed.

Answer 3

We have the same issue here. Following this thread for solutions.

Answer 4

Hello, we are having the same issue in a W2K19 fully patched server.

Any updates of this?

Thanks.

Answer 5

Setting the schedule to daily and run every 14 or 28 days (whatever you need) fixed it for me.