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

Joel Levy 66 Reputation points
2021-06-16T20:40:52.617+00:00

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.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
0 comments No comments
{count} votes

23 answers

Sort by: Most helpful
  1. Joel Levy 66 Reputation points
    2021-07-02T06:13:32.36+00:00

    FYI, there is a work around that will accomplish the same skipping a week feature. Instead of using the Weekly with the Recur feature, use instead the One time with the Repeat feutre as below. This will accomplish the same result and works good. However, the Weekly Recur is still broken and I need to use it because of a special setup. Any help would be appreciated.

    111235-1.png

    4 people found this answer helpful.

  2. Joel Levy 66 Reputation points
    2021-06-17T22:05:10.163+00:00

    Please note that the problem is that the task runs to many times. It should only run every other week but it actually runs every week. This would not be related at all to the batch or exe that is set to run as there is no way that the intended executable would cause the task to run at additional times.

    -----------------------------------------------------------------------------------------

    PS C:\Users\sbv> Get-TimeZone

    Id : Eastern Standard Time
    DisplayName : (UTC-05:00) Eastern Time (US & Canada)
    StandardName : Eastern Standard Time
    DaylightName : Eastern Daylight Time
    BaseUtcOffset : -05:00:00
    SupportsDaylightSavingTime : True

    ---------------------------------------------------------------------------------------

    I don't have the task anymore, (it's already changed) but will test a simple task as attached.
    106771-1.png

    106745-2.png

    106772-3.png

    106746-4.png

    1 person found this answer helpful.

  3. Andy YOU 3,071 Reputation points
    2021-06-17T05:05:06.81+00:00

    HI JoelLevy-4460,

    1.Please run below powershell command on issue server then share the result?
    Get-TimeZone

    2.Could you share the detail setting about "triggers", "action" , " conditions "and "settings" items of your issue task scheduler?

    3.Did you select "allow task to be run on demand" and "run task as soon as possible after a scheduler task is missed"? like below picture
    106388-22.png

    4.Please try to create a simple bat file and set the same task scheduler setting as your issue one, then check if the same issue happen?(Is your current issue ralted to your original bat file?)

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Joel Levy 66 Reputation points
    2021-06-18T09:10:30.317+00:00

    Yes, the events for the for the wrong weeks look exactly the same as the events for the correct weeks.

    0 comments No comments

  5. Micah Ellison 1 Reputation point
    2021-06-18T17:19:59.38+00:00

    I have been having the exact same problem for around a month now. A few weeks ago, I deleted the task then re-created it, and that did not solve the problem. Here is a screenshot of the history of my task, which should only be running once every 2 weeks at 10:00am Fridays but is instead running every Friday.

    I believe this is rock-solid evidence that it is a bug in Windows and not a user error, but if there is anything else that I can provide, please let me know.

    107029-2021-06-18-windowstaskschedulerbug.png

    0 comments No comments