We run several Tasks on WS2008R2 that has the following configuration: Trigger: Run daily, repeat every 3 minutes for the duration of 1 day Actions: Start a cmd on local Disk other setting: standard options Under some circumstances the task may run longer than 3 minutes, so the run command after 3 minutes should not be fired. (Setting: Do not start a new instance) But in fact everytime the existing instance is stopped and a new instance is started If you change the setting to "Queue a new instance", the existing instance is also stopped and a new one gets started. This is quite disasterous for us as this behaviour destroys files (Within the running task existing files are manioulated) As I saw in another forum http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/29a37921-3e27-4c88-b387-3dd394302298 other users have a similar, maybe the same problem. Is there any workaround / bugfix available?