Fix SCHED_E_SERVICE_NOT_RUNNING (0X80041315) – Task Scheduler stopped

Cause 1: Task Scheduler service is stopped or disabled

This is the most common reason you see 0x80041315. Something – usually a Windows update or a third-party cleanup tool – changed the service startup type to Disabled or just stopped it. I've seen it happen after running CCleaner's registry cleaner or after a feature update to Windows 10 22H2. The fix is straightforward: set the service back to Automatic and start it.

1. Press Windows key + R, type services.msc, and hit Enter. The Services window opens.
2. Scroll down and find Task Scheduler. It's under the Standard tab, usually in the lower half.
3. Right-click Task Scheduler and select Properties.
4. In the General tab, look at the Startup type dropdown. It should say Automatic. If it's Disabled or Manual, change it to Automatic.
5. Click Apply. After you click Apply, the Start button becomes clickable.
6. Click Start to start the service. You should see the service status change to Running in a few seconds.
7. Click OK to close the Properties window.

Now test your original task. Run whatever triggered the error (like a backup job or scheduled script). If it works, you're done. If not, close Services and open Task Scheduler itself (taskschd.msc) and verify your tasks are still there. Sometimes the service was down so long that tasks got corrupted – but that's rare.

If the service won't start – if you get a popup saying Error 1053: The service did not respond in a timely fashion – move to Cause 2.

Cause 2: Corrupted Task Scheduler configuration files

Windows stores Task Scheduler data in a hidden system folder. If that data gets corrupted – say from a sudden power loss, a failed Windows update, or a rogue script – the service fails to start. The symptom: you restart the service, it looks like it's starting, then it stops again immediately. Or you see error 1053.

The fix is to replace the corrupted files with backups that Windows keeps automatically. Here's how:

1. Open an elevated Command Prompt. Press Windows key + X, then select Terminal (Admin) or Command Prompt (Admin). Click Yes on the UAC prompt.
2. Stop the Task Scheduler service first: net stop schedule. Hit Enter. You should see The Task Scheduler service is stopping. followed by stopped.
3. Now rename the corrupted folder: ren C:\Windows\System32\Tasks Tasks.old. This renames the Tasks folder to Tasks.old.
4. Next, rename the registry data file: ren C:\Windows\System32\Tasks\Tasks.bak Tasks. Windows keeps a backup of the task configuration in that same folder. This command swaps the backup into the active folder.
5. Start the service again: net start schedule. You should see The Task Scheduler service is starting. then started.

If that backup folder doesn't exist (maybe Windows never created it), you can create a fresh Tasks folder by running mkdir C:\Windows\System32\Tasks and then restarting the service. After that, your scheduled tasks are gone – you'll need to recreate them. But at least the service runs.

Check your original error. If it's gone, you're set. If the service still refuses to start, you've got a bigger problem – likely a registry corruption or a system file issue.

Cause 3: System File Checker (SFC) and DISM repairs

If neither of the above fixes worked, the underlying Windows system files could be damaged. I've traced 0x80041315 to broken files in the %windir%\system32\Tasks path, and also to a missing schedsvc.dll after a botched update. SFC can repair those – but you need to run DISM first to fix the component store, or SFC will fail.

1. Open an elevated Command Prompt (same as above: Windows key + X > Terminal Admin).
2. Run DISM /Online /Cleanup-Image /RestoreHealth. This scans and repairs the Windows component store. It takes 5-15 minutes. Let it finish – don't close the window. You'll see a progress bar up to 100%, then a message like The restore operation completed successfully.
3. After DISM finishes, run SFC /SCANNOW. This checks all protected system files. It also takes 10-20 minutes. At the end, you'll see one of these messages: Windows Resource Protection did not find any integrity violations (that's good), or Windows Resource Protection found corrupt files and successfully repaired them (also good).
4. If SFC says it repaired files, restart your computer. After reboot, try starting Task Scheduler: net start schedule from an admin command prompt.

If DISM fails (you see error 0x800f081f or similar), you need an installation source – like a Windows 10/11 ISO or the Windows Server installation media. Skip that if you're not comfortable mounting ISOs. Instead, try running the Windows Update Troubleshooter from Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. It sometimes fixes the component store.

Quick-reference summary

One last thing: If none of these work, you're dealing with something weird – maybe a third-party antivirus that's blocking the service from starting (I've seen Bitdefender do this). Temporarily disable your AV and try again. If that fixes it, add an exception for C:\Windows\System32\taskschd.exe in your antivirus settings.