Fix SCHED_E_TRIGGER_NOT_FOUND 0x80041309 – Windows

Quick answer for advanced users: Delete the corrupted task via schtasks /delete /tn "TaskName" /f, then recreate it manually or from a backup export.

I know this error is infuriating because it stops tasks from running, and Windows gives you almost no info on what's wrong. In my help desk days, I saw this a lot on Windows 10 (especially version 22H2) and early Windows 11 builds. The trigger for a task—like "run at startup" or "run every hour"—is actually stored in a separate XML file inside the task itself. If that file gets corrupted, or if a recent Windows update changes the scheduler's internal structure, the scheduler can't find the trigger. Windows Update sometimes does this after a major patch.

What causes it exactly?

Here's the real trigger (pun intended): SCHED_E_TRIGGER_NOT_FOUND happens when the task's XML definition is missing the trigger element. This can happen after:

A failed Windows Update that messes with the Task Scheduler's internal registry keys.
Manually editing a task's XML with notepad and breaking the structure.
A third-party app that removes or overwrites the task without cleaning up properly.
Running schtasks /change with wrong parameters that delete the trigger.

Fix it in 3 steps

Skip the registry edits for now—they rarely help. The real fix is to delete and recreate the task. Here's how:

Step 1: Find the corrupted task

Open Event Viewer (eventvwr.msc) and go to Windows Logs > System. Look for Event ID 101 with source TaskScheduler. That event will say something like: "The trigger for the task 'YourTaskName' could not be found." Note the exact task name—case matters.

Step 2: Delete the task via command line

Open Command Prompt as Administrator. Run:

schtasks /delete /tn "YourTaskName" /f

Replace YourTaskName with the exact name from Event Viewer. The /f flag forces the delete without asking. If the task is part of a library (like \Microsoft\Windows\Something), include the full path: "\Microsoft\Windows\DiskDiagnostic\Microsoft-Windows-DiskDiagnosticDataCollector".

Step 3: Recreate the task

If you have a backup export of the task (XML file), import it:

schtasks /create /xml "C:\path\to\backup.xml" /tn "YourTaskName"

No backup? Recreate the task manually through Task Scheduler. Right-click Task Scheduler Library, pick Create Task, and set the triggers, actions, and conditions exactly as before. For most users, this fixes it.

If that didn't work: alternative fixes

Sometimes the corruption goes deeper. Try these instead:

Run SFC and DISM: Open CMD as admin and run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth. This fixes system file corruption that might affect the scheduler's XML parser.
Reset the Task Scheduler database: This is a nuclear option. Stop the scheduler service: net stop schedule. Then delete all files in C:\Windows\System32\Tasks (yes, all of them). Then restart the service: net start schedule. Windows will rebuild the tasks from scratch, but you'll lose all custom tasks—so back up any custom ones first.
Check for broken registry keys: Open Regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache. Look for any task that's missing a Trigger subkey. If you find one, delete the whole key for that task. Be careful—messing with the registry can break things.

How to avoid this in the future

Once you fix it, take these steps to prevent a repeat:

Export your important tasks: Right-click each task in Task Scheduler and choose Export. Save the XML files somewhere safe—I keep mine on a USB stick.
Don't edit task XML by hand. The XML is fragile. Use the Task Scheduler GUI or schtasks commands.
Before a big Windows update, export all custom tasks. Windows often re-indexes the scheduler database during feature updates, and that can corrupt triggers.

This error used to drive me crazy until I realized it's almost always a simple corruption. Delete and recreate—90% of the time, it's the only fix you need. Good luck!