The remote computer in that message is your own PC. The Task Scheduler window can't reach its background service on this same machine, so every option stays gray and scheduled jobs, defrag included, stop running.
Getting that service running is the fix. What usually stops it is a switched-off helper service called Time Broker, a wrong clock, or a registry setting that gets in its way.
Try starting the service by hand, and the reply you get points to the right one.
In this guide
Try to start the service and read the reply
Press Windows + R, type services.msc and press Enter. Scroll down to Task Scheduler: an empty Status column means it isn't running.
On Windows 10 and 11 its startup type is grayed out, so any change to how it starts goes through the registry, as fix 3 shows.
Right-click Task Scheduler and choose Start, or run net start schedule in Terminal (Admin). Note the exact reply, then find it in this list:

- The Task Scheduler service on Local Computer started and then stopped: go to fix 1.
- Error 126: The specified module could not be found: go to fix 5.
- Error 5: Access is denied: go to fix 6.
- The service shows Running, yet Task Scheduler still can't connect: work through fixes 2 to 4.
1. Turn Time Broker back on (started and then stopped)
Microsoft's troubleshooting article for this message links the started-and-stopped reply to Time Broker, a service that handles background work for Store apps. When Time Broker is stopped or disabled, Task Scheduler won't stay running.
In Services, find Time Broker and start it if its Status is empty. If its options are grayed out, use Registry Editor instead: press Windows + R, type regedit and press Enter.
Before you change anything there, select the key you're about to edit and use File > Export to save a copy. File > Import puts it back if something goes wrong.
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc, double-click Start and set it to 3, the normal value on a healthy Windows 11 PC. Restart and open Task Scheduler again.
2. Let Windows set the clock
A clock that's off can stop the service too. One owner on Windows 10 found Set time automatically had been switched off, and turning it back on brought Task Scheduler back.
The same wrong clock had Google flagging their searches as unusual traffic, which makes that a handy sign your clock is off.
Open Settings > Time & language > Date & time, switch Set time automatically on, and make sure the time zone is yours. If the clock was wrong, restart before you test Task Scheduler again.
I'd rule out the clock before any registry edit, since it takes seconds.
3. Change the Task Scheduler Start value to 3
One Windows 10 owner's Task Scheduler was set to Automatic but never really ran at startup. Starting it by hand only made it look like it was running, and the defrag tool still couldn't see it.
Their Start value was already 2, which means Automatic, the default you'll also find on a healthy Windows 11 PC. They changed it to 3 (Manual), restarted, and the service came up at boot with everything working again.
In Registry Editor, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule, export the key, then double-click Start, type 3 and select OK. Restart, then check that Services shows Task Scheduler as Running.
If the value you found was 4, that means Disabled. Change it to 2 first, restart, and only try 3 if 2 doesn't stick.
A service that's set to Automatic and still doesn't start after a restart can have other causes, but for Task Scheduler, this value is the one owners report changing.
4. Remove a leftover RPC Internet key
Task Scheduler talks to its service through RPC, the plumbing Windows programs use to call each other. A registry key named Internet under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc limits which network ports RPC may use.
That key isn't there on a normal PC. People add it by hand for firewall setups, and if any entry in it is out of range or can't be read, RPC treats the whole setup as invalid.
One server admin deleted the key (it was empty) and Task Scheduler started again. Another owner replied that deleting it solved theirs too.
Check with IT before deleting it on a company PC, since a firewall rule may depend on that key.
Open the Rpc key in Registry Editor. If Internet is listed under it, export it, then right-click it, choose Delete and restart.
No Internet key means this isn't your cause. One owner who went looking found only ClientProtocols, Extensions and SecurityService there, the same three subkeys a healthy Windows 11 PC has.
5. Put back a missing schedsvc.dll (Error 126)
Error 126 means a file the service needs is missing, or its registry entry points to the wrong place.
Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Parameters and check that ServiceDll reads %systemroot%\system32\schedsvc.dll.
Next, look for schedsvc.dll in C:\Windows\System32. It's a protected Windows file, so if it's gone, run these two commands in Terminal (Admin), one at a time, then restart:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
The line you want from System File Checker says the corrupt files it found were successfully repaired. After the restart, try starting the service again.
6. Error 5 on a work PC: the System log permission
Here, Access is denied means the SYSTEM account the service runs under can't write to the System event log. An administrator may have changed that permission for another reason, so on a managed office or campus PC, give IT the exact error.
To check it yourself, run wevtutil get-log "SYSTEM" in Terminal (Admin). The channelAccess line should begin O:BAG:SYD:(A;;0xf0007;;;SY).
If that SY entry is missing or different, the CustomSD value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System needs fixing, and that's a job for whoever manages the PC.
When the service still won't run
Event Viewer records the service's errors in the System log, with Service Control Manager as the source. Write down the Task Scheduler entries there and the reply you got when you tried to start it.
A repair install, which reinstalls Windows over itself, didn't help the owner from fix 3, so don't jump to it first. With fixes 1 to 6 done, bring those notes to a repair shop, or reach Microsoft support from the Get Help app.
The Short Version
Open Services and try to start Task Scheduler. If it starts and then stops, turn Time Broker back on. Error 126 needs DISM and SFC, and Error 5 on a company PC goes to your IT team.
If the service shows Running but the message stays, set the clock to automatic, change the Schedule Start value to 3, and delete any RPC Internet key.
Checked November 19, 2026.







