Task Scheduler jobs in Windows server 2022 and server 2019 runs weekly instead of biweekly.

Question

I'm running task scheduler in a fully updated Windows Server 2022 environment and I have two jobs scheduled.
Each job is supposed to run every other week Sunday to Friday, however, this is not the case.
Today, as you will see in the image attached, both jobs ran, even though, based on the schedule, it should be only one job running on 2022-02-06 at 8:30 AM.

Is Microsoft ever going to fix this problem? I first noticed it in server 2019 and avoided installing it on my critical servers, hoping they would fix it the next go around as others have complained about this in 2019 as well. This link shows someone complaining about the same issue in Server 2019.

Answer 1

I'll start with a disclaimer: I'm just another forum user and have no access to task scheduler code or the inner workings of what changes the task scheduler team has made or will make in future updates. I understand why you and others would expect the task to run every other week, but it doesn't do that, and no one on this forum is going to be able to "fix" the code. Assuming that it's even considered "broken" in the first place.

In the link that you posted, the final reply from wyxwyx-9203 on Dec 09 2021 at 3:16 PM appears to be the best solution. That is: define multiple triggers to execute every 14 days and to run indefinitely.

Here I defined my "Every other Sunday" trigger. It ran at 11am and it's next run time is the 20th. That skips the 13th. In your case, you would need to define a trigger for every day that you want it to run. Set each trigger to run indefinitely every 14 days. Your task will have 6 triggers. Monitor the "next run time" to verify that it will run when you expect it to.

Answer 2

So Microsoft fixed this in Windows Server 2025. I completely dislike that they silently fixed it and didn't offer a solution to people that have the issues in Server 2019 and 2022.

I guess if you really need it fixed and not have to change your entire workflow, just give MSFT more money. It's disappointing that this was something they knew about and couldn't be bothered to fix it for their existing customers.

Answer 3

So Microsoft fixed this in Windows Server 2025. I completely dislike that they silently fixed it and didn't offer a solution to people that have the issues in Server 2019 and 2022.

I guess if you really need it fixed and not have to change your entire workflow, just give MSFT more money. It's disappointing that this was something they knew about and couldn't be bothered to fix it for their existing customers.