SCHED_E_MISSINGNODE (0X80041319) – Task XML missing element fix
Windows Task Scheduler throws this when a task's XML is corrupt or missing required tags. Fix is to export and re-register the task or delete and recreate it.
Quick answer
Open Task Scheduler, export the broken task to XML, delete the task, then re-import the XML – or recreate the task from scratch.
Why this happens
You get SCHED_E_MISSINGNODE (0X80041319) when Task Scheduler tries to read a task that has a missing or corrupt XML element. This usually happens after a Windows update, a manual edit of the task XML gone wrong, or a system restore that didn't fully back up the task structure. I've seen this most often on Windows 10 after the 22H2 update – a client's nightly backup task just stopped working and threw this error when they tried to run it manually.
The XML file that defines a scheduled task has required tags like <Triggers>, <Actions>, <Principals>. If one of these is missing or malformed, you get error 0x80041319.
Step-by-step fix
Before you delete anything, stop the task from running again: open Task Scheduler, find the task that errors, right-click it, and select Disable.
Step 1: Export the broken task
Right-click the task and choose Export. Save the XML file to your desktop. This preserves any custom settings you might want later.
Step 2: Delete the task
Right-click the task again and choose Delete. Confirm the deletion.
Step 3: Re-import the task
Right-click the Task Scheduler Library in the left pane, select Import Task, and point to the XML you saved. If the import fails, you've got a corrupt XML file – skip to the alternative fix below.
Step 4: Test it
Right-click the newly imported task and choose Run. If it runs without error, you're done. If it still throws 0x80041319, the XML itself is bad.
Alternative fix: Recreate the task manually
When the export-import loop fails, you need to build the task from scratch. Open Task Scheduler, click Create Basic Task or Create Task. Re-enter the trigger, action, and settings exactly as before. If you exported the XML earlier, open it in Notepad to copy the exact command line and arguments.
I had a client last month whose entire print queue died because of this – the task that ran the nightly printer driver update became corrupt. We couldn't fix the export, so we rebuilt the task fresh. Took 5 minutes.
Alternative fix for power users: Schtasks command
If you prefer the command line, you can delete and recreate the task with schtasks:
schtasks /delete /tn "TaskName" /f
schtasks /create /xml "C:\path\to\exported.xml" /tn "TaskName"Replace TaskName with the exact name of your task. If the XML is clean, this works without the GUI. If it fails again, the XML is corrupt.
Alternative fix: Edit the XML manually
Open the exported XML in Notepad or VS Code. Look for missing required elements. The basic structure must include:
<RegistrationInfo>– date, author<Principals>– user account context<Settings>– at least a minimal settings block<Triggers>– at least one trigger (even a one-time trigger)<Actions>– at least one action
If you see a missing closing tag or an empty element like <Triggers/>, that's your problem. Add a proper trigger element. Save the XML, then import it again.
Prevention tip
Backup your task exports regularly. Use a script that exports all tasks to a folder daily:
schtasks /query /xml > alltasks.xmlStore that file somewhere safe. When an update breaks a task, you can re-import from a clean backup instead of guessing the original settings.
Also, never edit task XML files manually unless you know every required tag. One missing bracket and you're looking at error 0x80041319.
Was this solution helpful?