This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 64%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 3%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I had the same problem, it was fixed when I ran the task with the LOCAL SERVICE account instead of my own user. If you are running it with another user other than this user, it is also useful to try.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 41%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
Same problem on a Windows 10 desktop. 21H2 fully patched.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 32%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Been trying to find a bug number to track or an anything from Microsoft saying it's been acknowledged, and I haven't found it. What I have seen is across multiple OS's both Servers and Clients and happens when using 'RunAs' weather the user is logged in or not. I can re-save the task and the 'next schedule run time' will be accurate, but after that time has passed the one after that will be only one week rather two or four etc.
I think that somewhat consolidates the information I have read in this thread so far, with the exception of the workaround. I so have a question on the workaround repat every 14 days if anyone has any information on if that workaround pushes the time out further and further for tasks that cross over day boundaries. (I.e. starts Friday night then is done Sat, will 14 days out be two weeks from now Sat morning then?)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 49%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
you know what? It's June 2024 and I have the same problem on windows 10 pro 22h2. For two months now, I've been staring like an idiot at the tasks I'm creating and trying to figure it out. Today it occurred to me that maybe everything is fine with my eyes, so I searched the Internet and came across this topic. SHAME ON YOU MS!!!
and the best part is that I have 8 tasks. they were all imported from one template created first and modified regarding the day and file run time. 6 works fine. two were malfunctioning from the start. Creating these tasks again or importing them from another one does not fix the situation. this is amazing. ill try upper solution on this two bad task (14 days). OMG... :/