Fix SCHED_S_TASK_NOT_SCHEDULED (0X00041305) Error

What's Happening Here

You're staring at error 0X00041305, and it's annoying. I get it. This one usually pops up when you're trying to run a task manually or when Windows tries to fire it off automatically and finds the schedule configuration is busted. The error text says it all: one or more properties needed to run this task on a schedule haven't been set. In plain English? The task's trigger is missing, corrupted, or the task itself isn't properly created.

I've seen this most often after a Windows Update (especially 22H2 on Windows 10) or when someone copies a task from another machine without exporting the triggers. It also happens if you edit a task in Notepad and accidentally nuke the XML trigger node.

The 30-Second Fix: Reset the Trigger

This works about 60% of the time. Don't overthink it yet.

1. Open Task Scheduler. Hit Windows + R, type taskschd.msc, press Enter.
2. Find the task giving you the error. Look in the left pane under Task Scheduler Library.
3. Right-click the task and select Properties.
4. Go to the Triggers tab.
5. Do you see any triggers listed? If yes, select each one and click Edit. Just click OK without changing anything. That forces a re-save of the trigger data.
6. If there are no triggers, click New, set up a basic schedule (like daily at 8 AM), and click OK.
7. Click OK to save the properties.
8. Right-click the task and select Run. If it runs, done. If not, move to the next fix.

I once fixed this error on a client's Windows 11 machine just by opening and closing the triggers tab. No joke. The edit operation re-serializes the trigger XML, which sometimes fixes a subtle corruption.

The 5-Minute Fix: Re-Create the Task from Scratch

If the trigger reset didn't work, the task's definition is likely hosed. Don't bother tweaking individual settings—re-create it clean.

1. In Task Scheduler, select the broken task and press Delete. Confirm the deletion.
2. Click Create Basic Task in the right pane.
3. Give it the same name and description as the original.
4. Choose a trigger. For most tasks, Daily or One time works. Be specific with the start time and recurrence.
5. For the action, pick Start a program. Browse to the exact executable you were trying to run.
6. If the program needs arguments (like a script path), put them in Add arguments.
7. Click Finish.
8. Now right-click the new task, select Properties, and check the General tab. Make sure Run whether user is logged on or not is selected if you need it to run in the background. Also tick Run with highest privileges if it needs admin rights.
9. Test it by right-clicking and selecting Run.

This sounds heavy, but honestly it's faster than debugging a broken XML export. I've done this for dozens of users who tried to copy tasks between machines. Task Scheduler doesn't handle partial imports well.

The 15+ Minute Fix: Reset Task Scheduler Permissions and Check Corruption

If you're still stuck, the problem is deeper. Either the Task Scheduler service itself has bad permissions, or the task store is corrupted. Let's check both.

Step 1: Check Task Scheduler Service

1. Press Windows + R, type services.msc, press Enter.
2. Scroll to Task Scheduler. Make sure its status says Running and the startup type is Automatic.
3. If not, right-click, select Properties, set startup to Automatic, click Start, then OK.

Step 2: Reset the Task Store Permissions

The error can also come from the task file itself being in a folder with wrong permissions. Here's the fix:

1. Open File Explorer. Go to C:\Windows\System32\Tasks. This is where Windows stores task definitions as individual files.
2. Find the task file that matches your task name. It won't have an extension.
3. Right-click the file, select Properties, go to the Security tab.
4. Click Advanced. At the top, next to Owner, click Change.
5. Type SYSTEM in the box, click Check Names (it should underline it), then click OK.
6. Check the box Replace owner on subcontainers and objects.
7. Click Apply, then OK.
8. Now back in the Permissions window, make sure SYSTEM has Full control. Also add your user account with Read & execute.
9. Click OK all the way out.

Step 3: Re-Register the Task Scheduler DLLs

Corrupt DLLs can cause this error too. Open Command Prompt as administrator and run these commands one by one:

regsvr32 /s taskcomp.dll
regsvr32 /s taskschd.dll
regsvr32 /s mstask.dll

Then restart the Task Scheduler service from services.msc.

Step 4: System File Checker (SFC) and DISM

If nothing else works, corruption might be system-wide. Run these in an admin Command Prompt:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

The SFC scan takes about 15 minutes. DISM can take 30. Let them finish. Reboot, then re-create the task fresh.

When to Give Up and Use a Script

If you've done all of the above and the error still shows, the task is cursed. I'm serious—some tasks on Windows have a weird bug where the XML metadata in the registry stays corrupt even after deletion. The nuclear option: use PowerShell to delete the task forcefully.

Unregister-ScheduledTask -TaskName "YourTaskName" -Confirm:$false

Then register it again via PowerShell:

$Action = New-ScheduledTaskAction -Execute "C:\Path\To\App.exe"
$Trigger = New-ScheduledTaskTrigger -Daily -At 8am
Register-ScheduledTask -TaskName "YourTaskName" -Action $Action -Trigger $Trigger -User "SYSTEM" -RunLevel Highest

That bypasses the GUI entirely and is often the cleanest fix.

That's it. You should be clear of 0X00041305 now. If you're still seeing it after all this, you might be dealing with a third-party security tool locking the task store. Check your antivirus logs and temporarily disable any real-time protection to test.