Windows 10: Task Scheduler issue due to DST Changes

We have hit an bug in Task Scheduler . The version of windows is : Windows Server 2016Problem:The task finishes within 5 seconds of getting triggered. The task does not perform the desired actions.However if the same task is triggered manually, the task runs properly.Currently this issue is being faced in US region only.The trigger for the issue is Daylight saving changes for the US I guess also for Europe and may be other parts of the world . This issue had surfaced around October 2022 also . But , it got resolved on adding add <Duration> and <WaitTimeout> properties in IdleSett

:)

 

Task Scheduler failing after BST and DST changes

I thought I'd chip in with some of our findings having had a number of scheduled tasks fail on our network due to Task Scheduler not kicking in. We have found the following:

• Scheduled tasks on Windows Server 2012 and 2012 R2 are unaffected
  
• Windows Server 2016 and 2019 are affected but only tasks that are Weekly or Monthly (or with multiple triggers that contain either)
  
• Symptoms similar to those described. Tasks do not start; no messages, no log entries, they just proceed to the next scheduled event.
  

We have a call logged with Microsoft for advice on a permanent resolution to this however the following may work (albeit until the next DST event)

• Open each failing event and alter the change the 'from' start date
  
• Alter the time (even by one minute) let it run and revert
  
• Each of the above may just be just a case of resetting the task and re-presenting it to the system.
  
• A reboot of the servers (gleaned from the internet - not tried in our case). However this would happen as a result of monthly patching.
  
• Another suggestion for a permanent resolution is to tick the box to 'Synchronise across time zones' on setting the trigger time. This may have some validity as the system log entry for the DST shift states it is shifting time zones.
  
  The system time has changed to ‎2022‎-‎03‎-‎27T01:00:11.415086900Z from ‎2022‎-‎03‎-‎27T01:00:11.415086900Z.
  Change Reason: System time adjusted to the new time zone.
  
  (This is how it was displayed in the log file: yes, the old and new times showed as the same although the actual log was timed at 02:00:11)
  
  We can't afford the time to test the time zone solution so it may either have to wait until October or until Microsoft responds with a definitive answer. I will post the official response on here when it comes back.
  

 

Windows 10 Task Scheduler DST March 2023 issues

Since the Daylight Summer Time changed last weekend, some scheduled tasks have failed to run on Windows 10.

The issue appears to be tasks scheduled to start between 0:00 and 1:00 do not run.

I have several tasks starting at various times of the day and I have noted that two specific tasks that start during this time window no longer work.

Microsoft Task Scheduler DST/ return from DST task starting issues have been around for a number of years, so much so that we plan to fix the task schedules soon after the March / October time changes occur but this time it really looks broken.

I actions taken so far include the typical fixes:

• Reset the start date of the task to today
  
• Export the task and delete the task to then reimport the task
  
• Manually recreate the task within Task Scheduler GUI
  

Yesterday, I spent a few hours creating the Tasks using PowerShell scripts and last night the two expected to run did not.

Today, I plan to create around 40 scheduled tasks to run separately at 5 minute intervals between 23:30 and 03:00 to see which was start and which don't.

I will send in the results in tomorrow.

Kind Regards

 

Windows 10 Task Scheduler DST March 2023 issues

Greg,

This issue affects Windows 10 which is used by consumers and businesses.

I have created a similar question of the other forum as suggested.

The new issue appears that tasks will not start between specific time periods whereas before you could change the start date or export and import the task to fix the twice a year problem.

It appears that the issue of Scheduled tasks and DST changes has been made worse.

Kind Regards