Task Scheduler Issues – Tasks Disappearing and Snap-in Errors After Recent Update after reboot the tasks back but it randomly happen.

Question

Task Scheduler Issues – Tasks Disappearing and Snap-in Errors After Recent Update after reboot the tasks back but it randomly happen.

Greenkey 0

I'm experiencing problems with Task Scheduler where task disappear and the console behaves unexpectedly.

At random times, all tasks disappear from Task Scheduler.
When navigating to other folders (e.g., Microsoft folder), a popup appears with an “End Snap-in” error.
However, all scheduled tasks are still present in the directory C:\Windows\System32\Tasks. In Event Viewer (Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational), tasks appear to be launched but do not complete.
Behaviour varies: In some instances, all tasks (including Microsoft default tasks) stop running. In other cases, some Microsoft tasks and our custom tasks continue to run while others remain stuck or on hold.
After a system reboot, all tasks reappear in Task Scheduler and function normally until the issue occurs again.

The Windows updates (Azure Connected Machine Agent version 1.64.03414.2961) installed on June 11 and the issue started on June 15.

This is the first time we have encountered such an issue in over 8 years of these task operation.

Has anyone encountered this or knows if it is related to recent update? Any fixes or troubleshooting suggestions would be appreciated.

0 comments

1 answer

Your answer

Answer 1

Hi Greenkey,

Based on what you described, the disappearing tasks and snap-in errors are not caused by the tasks themselves but rather by how the Task Scheduler MMC console is rendering them after the recent update. The fact that tasks remain in C:\Windows\System32\Tasks and continue to launch (though inconsistently) confirms they are still present in the system.

A few troubleshooting steps you can try:

Clear the Task Scheduler cache by restarting the Task Scheduler service or rebooting (as you’ve noticed, reboot temporarily resolves it).
Check the Event Viewer > Microsoft > Windows > TaskScheduler > Operational log for error codes tied to the snap-in crash, this often points to corrupted XML in one or more tasks.
Run sfc /scannow and DISM /online /cleanup-image /restorehealth to ensure no system files were corrupted during the update.
If the issue persists, test by temporarily uninstalling or rolling back the Azure Connected Machine Agent update you mentioned, as that timing aligns closely with when the behavior started.

Best practice is to export your custom tasks to XML, then re-import them after confirming system health, which can eliminate hidden corruption.

I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

Jason.