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(214.4, 91%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHA%3C/text%3E%3C/svg%3E)
Hello!
I have a scheduled task that has been running hourly till yesterday:
It ran at 6PM, 7PM, 8PM (8/6/2025)- then only at 11PM (9pm and 10pm missed) and eventually Task Scheduler displays its Next Run Time at 8/7/2025 6PM
I haven't changed anything in the task definition since its creation about 2 years ago (it is Windows Server 2022) - the task was exported from another DC with Windows Server 2012R2 where it's been working flawlessly for ~9 years!
How can it be possible???
Regards,
Michael
P.S. "and eventually Task Scheduler displays its Next Run Time at 8/7/2025 6PM" - and it hasn't even run at its scheduled time!!! (the server must be restarted if the task runs successfully).
TS didn't event try to launch the task Watcher-Memory at 6PM - only Windows-related task were started at 6PM!
P.P.S. As far as I get it the method I used for running the task hourly is not strictly correct, although it's widely used, for example: https://techrando.com/2019/06/22/how-to-execute-a-task-hourly-in-task-scheduler/
The problem is that there's no such option in Task Scheduler as "Run hourly" - there's only Daily (or One time) - Start [Specific time] + Repeat hourly... !
It means the task will be repeating only till the next server restart - after restart the task would first wait for the time specified in the Daily (or One time) - Start [] field and only AFTER that time the task would keep starting every hour!
Seems the only way to make TS run a task every time is to add 24 schedules :(
...but my problem is not caused by the absence of the "Run hourly" option.
I would think that if you set the trigger to run at midnight, recur every day, and repeat the task every hour for a duration of one day, that should work.
The task that kicks off at midnight is responsible for the next 24 hours.
You may also want to check the Stop Task option if the task runs longer than 50 minutes.
"I would think that if you set the trigger to run at midnight, recur every day, and repeat the task every hour for a duration of one day, that should work.
The task that kicks off at midnight is responsible for the next 24 hours."
-- hmm...but even in this case the task would need first to start at 0:00 and only then to be repeated hourly - if the server were rebooted say at 2:am the task could not be repeated any more because it should first wait to be run at 0:00 on the next day!
...don't know what to say: the issue seems to have gone and I haven't even tried to fix it yet. The only thing I've done is to have added 24 schedules instead of Run at ...+ Repeat hourly indefinitely - no comments...
Let's see if your Windows Server works differently from my Win11 VM. Create a second task using this command. It will run PS every hour and write the current time to a log file. Change c:\temp to some folder if you want. Don't use a folder with spaces in the name. Note that the start date is yesterday. Actually, on the first test that I did, I used 2015 for the year and it still worked.
I've rebooted and the Next Run Time is correct. See if the timestamps in the log show it running every hour.
schtasks /create /tn Test2 /ru system /sc DAILY /sd "08/10/2025" /st 12:00 /ri 60 /du 24:00 /tr "powershell.exe out-file c:\temp\TaskTester.txt -append -inputobject (get-date)"