Task Scheduler Trigger Desynchronization After System Time Adjustment

Question

Task Scheduler Trigger Desynchronization After System Time Adjustment

George Wilson 80

Dear Colleagues,

We are troubleshooting an issue where scheduled database maintenance tasks fail to trigger after a daylight saving time transition or manual system clock adjustment, remaining stuck in a Queued state. What is the recommended procedure to re-synchronize the Task Scheduler triggers and restore normal execution?

Many thanks in advance for your insights.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hello George Wilson,

The queued state after daylight saving or manual clock changes is a known Task Scheduler behavior caused by trigger misalignment with the system time service. The recommended procedure is to force Task Scheduler to re‑synchronize its triggers by restarting the Task Scheduler service (Schedule) and ensuring the system clock is corrected against a reliable NTP source. In practice, run net stop schedule && net start schedule from an elevated command prompt, then confirm that w32time is synchronized (w32tm /resync). If tasks remain stuck, delete the C:\Windows\System32\Tasks\TaskCache registry entries under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree only for the affected tasks and re‑import them, which clears stale trigger metadata. Microsoft also advises applying the latest cumulative updates, since several hotfixes address DST handling in Task Scheduler. After these steps, scheduled database maintenance jobs should resume normal execution without requiring manual intervention.

If my answer is useful for you, please hit Accept the answer to support me.

Thank you,

HL.