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(96, 89%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENL%3C/text%3E%3C/svg%3E)
We have an issue with the task scheduler(Windows server 2016). It runs multiple times even if it is set to 'Do not start a new instance'. Please advise.
Seeing the same behaviour on Windows Server 2022. I am able to start a task a dozen times even though "Do not start a new instance" is set.
ok this appears to be "by design". The setting only applies to the schedule. eg If a task is already running, and its schedule says to run again, it will not allow it if this setting is enabled.
However, if an admin like us comes along and says to run a task manually, Windows will allow it.
This is chatgpt response.
The “Do not start a new instance” setting in Windows Task Scheduler is about the scheduled task itself, not about what it does1. This means that if a task is already running and it is triggered again by its schedule, the Task Scheduler service will not run a new instance of the task and will not stop the instance that is already running1.
However, this does not prevent you from manually starting a new instance of the task. If you manually start a task that is already running, a new instance of the task will be started regardless of this setting1.
If you want to prevent multiple instances of the task from running at the same time, you might need to implement this functionality within the task itself. For example, your task could check if an instance of it is already running when it starts, and if so, it could terminate itself.