Fix SCHED_S_TASK_READY (0X00041300) - Task Scheduler Status

When You See This Status

You open Task Scheduler, browse to a task you set up—maybe a backup script, a cleanup job, or a reminder popup—and the status column reads Ready (0x00041300). The task hasn't run yet, and you're wondering: is it broken? Did I misconfigure something? Why isn't it firing?

You'll typically see this right after creating a task or after the last run completed successfully. The most common trigger is checking the Task Scheduler library after setting a one-time or recurring task that hasn't reached its first trigger time yet.

What's Actually Happening Here

0x00041300 maps to SCHED_S_TASK_READY. The 'S' stands for success—it's a status code, not an error code. Windows Task Scheduler uses this to say: "The task is registered, all conditions are met, and it's waiting for its next trigger."

Think of it like an alarm clock that's been set but hasn't reached the alarm time yet. The clock isn't broken. It's just waiting.

The real question you should ask: does the task actually run when its trigger fires? If yes, ignore this status. If no, you've got a different problem—usually a permissions issue, missing trigger, or misconfigured settings.

How to Confirm the Task Works

1. Run it manually. Right-click the task in Task Scheduler and select Run. Check the Last Run Result column. If you get 0x0 (success) or 0x41301 (task is already running), the task itself is fine. The issue is timing.
2. Check the trigger list. Open the task properties, go to the Triggers tab. Make sure at least one trigger is enabled (green checkmark) and the start time is in the future. If you set a trigger for yesterday, the task won't run until you update the start time.
3. Verify the task is enabled. In the main Task Scheduler window, look at the task's status. If it says Disabled, right-click and choose Enable.
4. Check conditions. Go to the Conditions tab. If Start the task only if the computer is on AC power is checked and you're on battery, the task won't run. Same with Wake the computer to run this task—if unchecked, the task won't fire if the PC is asleep.
5. Look at the history. In Task Scheduler, under Task Scheduler Library, find your task and click the History tab. Filter by Task Started or Task Completed events. If you see nothing after manual run, check your permissions—the task might be running as a user that no longer exists.

When It Still Won't Run

If the status stays Ready but the task never fires at its scheduled time, here's the usual culprit:

The task is set to run only when the user is logged on, but you're not logged in at that time. In the task's General tab, check Run whether user is logged on or not. This requires the task to have a stored password. If you check it, you'll be prompted to enter the user's password. This is the single most common fix for tasks that look ready but never run.

Another overlooked cause: the task's Configure for setting is wrong. In the General tab, you'll see a dropdown labeled Configure for:. If you're on Windows 10 or 11, set it to Windows 10. Older settings (Windows 7, Windows 8) can cause the task to sit in Ready forever.

Task Scheduler > Select Task > Properties > General > Configure for: Windows 10

Last resort: delete the task and recreate it from scratch. Export the task first (right-click > Export) so you can compare the XML with the new one. Sometimes corrupted task definitions look fine in the UI but won't latch onto the scheduler properly.

What to Check If It Still Fails

• Run schtasks /query /v /fo LIST | findstr "TaskName" in an admin command prompt. Verify the task is listed and the status shows Ready.
• Check the Windows Application event log (Event Viewer > Windows Logs > Application) for any Task Scheduler warnings or errors around the scheduled time.
• If the task runs an executable (like a script or .exe), test that executable manually from an admin command prompt. If it fails there, the task won't fix it.
• Make sure the system clock is correct. Windows relies on accurate time to trigger tasks. If the clock drifts or shows the wrong time zone, tasks may appear Ready but never fire.

Bottom line: 0x00041300 is not an error. It's the normal waiting state. If your task actually runs when it should, stop worrying about this code. If it doesn't run, look at triggers, conditions, and the Run whether user is logged on setting first.