SCHED_E_TASK_NOT_READY (0X8004130A) Fix — Missing Task Properties

You try to run a scheduled task and get hit with SCHED_E_TASK_NOT_READY — the task just sits there, grayed out, refusing to launch. I've seen this drive people up the wall. Let's fix it.

The Quick Fix: Rebuild the Task

What's actually happening here is the task in Task Scheduler has corrupted or incomplete XML properties. Windows can't figure out what to run, when to run it, or under what account. The fastest path is to delete and recreate the task from scratch.

1. Open Task Scheduler as Administrator (right-click Start > Computer Management > Task Scheduler, or type taskschd.msc in Run).
2. Navigate to the folder holding the broken task — usually Task Scheduler Library.
3. Find the task showing the error. Right-click it and select Delete. Say yes to the confirmation.
4. Right-click the folder, choose Create Task, and configure it fresh. Pay attention to these specific fields:

• General tab: Give it a name. Check "Run whether user is logged on or not" unless you need interactive access.
• Triggers tab: Add at least one trigger. A task with zero triggers will throw this error.
• Actions tab: Add the program or script you want to run. Don't leave this empty.
• Conditions tab: Uncheck "Start the task only if the computer is on AC power" if you want it to run on battery too.
• Settings tab: Check "Allow task to be run on demand" (already on by default).

Click OK. Enter your Windows password if prompted. Try running the task manually — right-click it and select Run. Should work now.

Why This Works

The reason step 3 works is that Windows stores each scheduled task as an XML file in C:\Windows\System32\Tasks. When you delete via the GUI, it nukes that XML. Creating a fresh task builds a clean XML with all required fields: the task's Principal (user account), Triggers (at least one), Actions (what to execute), and Settings (run on demand flag). Missing any of these produces SCHED_E_TASK_NOT_READY. The GUI wizard forces you to fill them in. That's why recreating works — you can't create a half-baked task through the wizard, but the old one got into a half-baked state somehow.

What corrupts these files in the first place? Usually, a bad export-import cycle, a hard crash while the task was being edited, or third-party software (backup tools, game launchers) that modified the XML by hand and missed a field.

Less Common Variations

Sometimes recreating isn't the right fix. Here's when it's something else:

1. Source of the Task Is Missing

If the task points to a program that no longer exists, you get this error. Check the Actions tab — if the path is broken, update it to the correct executable location. Common trigger: uninstalling an app but leaving its scheduled task behind.

2. User Account Issues

A task set to run under a specific user account that's been deleted, disabled, or had its password changed will fail. Go to the General tab, click Change User or Group, and pick an active account. Re-enter the password. Test immediately.

3. Corrupted Task File on Disk

Task Scheduler won't let you edit a task that's too mangled. In that case, delete it via GUI, then manually check C:\Windows\System32\Tasks for any leftover files matching the task name. Delete them. Recreate.

4. Permission SNAFU

If the task was created by one user and you're running as another, you might not have rights to start it. Right-click the task, go to Properties > General, and click Change User or Group to match your current account.

Prevention

Three things keep this error away:

• Don't edit task XML by hand. The Task Scheduler GUI is ugly but safe. If you must export/import tasks (for backup or deployment), use schtasks /query /xml and schtasks /create /xml — those commands validate the XML. The GUI export/import feature works too, but only if you never modify the .xml file in a text editor afterwards.
• Keep user accounts stable. If you change your Windows password, update all your tasks immediately. Task Scheduler doesn't sync with your account password changes — it stores the old password hash and silently fails.
• Monitor task health. Run schtasks /query /v /fo LIST | find "Status" regularly in a script. Look for anything that says "Ready" but won't run. Catch it early.

That's it. The error is annoying but shallow — it's almost always a missing property in the task definition. Rebuild it clean and you're done.