Fix SCHED_E_SERVICE_NOT_INSTALLED (0X8004130C) Error Fast
The Task Scheduler service isn't installed or running. This fix gets it back without reinstalling Windows. Two registry tweaks usually do it.
Cause 1: The Task Scheduler Service is Disabled or Set to Manual
This is the most common reason you see 0x8004130C. Something—a security tool, a system cleanup utility, or even a Windows Update glitch—turned the service off. Or set it to manual instead of automatic.
Here's how to check and fix it.
- Press Windows Key + R to open the Run box.
- Type
services.mscand hit Enter. You'll see the Services window open. - Scroll down to Task Scheduler. It's near the bottom, under the Ts.
- Look at the Startup Type column. If it says Disabled or Manual, that's your problem.
- Right-click Task Scheduler and choose Properties.
- In the Startup type dropdown, pick Automatic.
- Click Apply. You should see the buttons become active.
- Now click Start to kick the service on. If it starts without an error, you're good. Close the window and reboot to confirm the fix sticks.
If the service refuses to start, or if it's already set to Automatic but still not running, move to Cause 2.
Cause 2: Corrupted or Missing Registry Keys for Task Scheduler
I've seen this on systems where a tool like CCleaner or a manual registry edit removed the Task Scheduler's registry entry. Without it, Windows can't find the service, so it throws 0x8004130C even if the service file is intact.
Before you start: back up your registry. Open Regedit, click File > Export, and save a copy. If something goes wrong, you can double-click that file to restore.
- Open Registry Editor (Windows Key + R, type
regedit, press Enter). - Navigate to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule - If the Schedule key is missing, you'll need to create it. Right-click Services (not any subkey), choose New > Key, and name it
Schedule. - Inside the Schedule key, create these values:
- DisplayName (REG_SZ):
Task Scheduler - ImagePath (REG_EXPAND_SZ):
%SystemRoot%\System32\svchost.exe -k netsvcs - Start (REG_DWORD):
2(2 means Automatic) - Type (REG_DWORD):
0x10(decimal 16, Win32 service) - ErrorControl (REG_DWORD):
1 - ObjectName (REG_SZ):
LocalSystem
After adding these, close Regedit. Now open Services (services.msc) again, find Task Scheduler, right-click and start it. If it starts, run a task to verify. If it still won't start—you might have a missing DLL. That's Cause 3.
Cause 3: System File Corruption (sfc /scannow and DISM)
Sometimes the Task Scheduler executable file (schedsvc.dll) gets damaged or deleted. A security update or a failing hard drive can do this. The service might be set correctly but still throws 0x8004130C because Windows can't load the file.
Run these commands in an Administrator Command Prompt:
- Right-click the Start button and choose Command Prompt (Admin) or Windows Terminal (Admin).
- Type
DISM /Online /Cleanup-Image /RestoreHealthand press Enter. This checks the system image and fixes corruption. It can take 10-20 minutes. Let it finish. - Once that's done, type
sfc /scannowand press Enter. This checks every protected system file and replaces bad ones. Same deal—let it run completely. - After both finish, reboot your computer.
If DISM threw an error (like 0x800f081f), you might need a Windows installation media. Mount the ISO and run DISM pointing to it:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\sxs /LimitAccessReplace D: with the drive letter of your mounted ISO. After the reboot, check if the Task Scheduler service starts and the error disappears.
Quick-Reference Summary Table
| Cause | Symptom | Fix | Time |
|---|---|---|---|
| Service disabled | Service shows Disabled in Services.msc | Set Startup Type to Automatic, start service | 2 minutes |
| Missing registry key | Schedule key missing from registry | Create Schedule key with required values | 5 minutes |
| Corrupted system files | Service won't start even with correct registry | Run DISM then sfc /scannow | 20-30 minutes |
That's it. I've walked hundreds of people through this. Start with the service setting—it solves maybe 70% of these errors. The registry fix handles another 20%. System file repair covers the rest. You shouldn't need to reinstall Windows for this one.
Was this solution helpful?