|
| 1 | +--- |
| 2 | +title: Troubleshoot Task Scheduler Service Startup Failure |
| 3 | +description: Helps troubleshoot the failure to start the Task Scheduler service in Windows computers. |
| 4 | +ms.date: 04/21/2025 |
| 5 | +manager: dcscontentpm |
| 6 | +audience: itpro |
| 7 | +ms.topic: troubleshooting |
| 8 | +ms.reviewer: kaushika, warrenw, mamash, v-lianna |
| 9 | +ms.custom: |
| 10 | +- sap:system management components\task scheduler |
| 11 | +- pcy:WinComm User Experience |
| 12 | +--- |
| 13 | +# Troubleshoot issues with the Task Scheduler service not starting |
| 14 | + |
| 15 | +This article helps troubleshoot the failure to start the Task Scheduler service in Windows computers. |
| 16 | + |
| 17 | +Your scheduled tasks don't run or miss their schedules. When you open Task Scheduler, you receive the following error message: |
| 18 | + |
| 19 | +> The remote computer was not found. |
| 20 | +
|
| 21 | +The Task Scheduler service isn't started in the **Services** snap-in (**Services.msc**). When you start the Task Scheduler service, you receive one of the following error messages: |
| 22 | + |
| 23 | +- > The Task Scheduler service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs. |
| 24 | +- > Error 5: Access is denied |
| 25 | +- > Error 126: The specified module could not be found |
| 26 | +
|
| 27 | +Each error message has different causes and resolutions. |
| 28 | + |
| 29 | +## Error: The Task Scheduler service on Local Computer started and then stopped |
| 30 | + |
| 31 | +This error occurs because the Time Broker service is either stopped or disabled. To resolve the error, enable and start the service by using one of the following methods. |
| 32 | + |
| 33 | +> [!NOTE] |
| 34 | +> The Time Broker service coordinates the execution of background work for WinRT applications. If this service is stopped or disabled, background work might not be triggered. |
| 35 | +
|
| 36 | +### Use the Services snap-in |
| 37 | + |
| 38 | +Select **Start** > **Windows Administrative Tools** > **Services**, and check if the Time Broker service is running. If it isn't running or is disabled, enable it and then start it. |
| 39 | + |
| 40 | +### Use Registry Editor |
| 41 | + |
| 42 | +1. Open Registry Editor, and go to `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc`. |
| 43 | +2. In the right pane, check if the `Start` value is set to `3` by default. If not, modify it to `3`. |
| 44 | +3. Restart your computer and check if the Task Scheduler service is running. |
| 45 | + |
| 46 | +If that doesn't resolve the issue and you still can't start the Task Scheduler service, see the [Additional resources](#additional-resources) section. |
| 47 | + |
| 48 | +## Error 5: Access is denied |
| 49 | + |
| 50 | +This error occurs because the NT AUTHORITY\\SYSTEM account doesn't have write permissions to the System event log. The permissions might have been modified by a system administrator using a `CustomSD` registry key for other purposes. |
| 51 | + |
| 52 | +The Task Scheduler service runs under the SYSTEM account. By default, the SYSTEM account has write permissions to the System event log to allow the Task Scheduler service to log events into the System event log. |
| 53 | + |
| 54 | +The security of each log is configured locally through the values in the following registry key: |
| 55 | + |
| 56 | +`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog` |
| 57 | + |
| 58 | +If the System event log permissions are customized, the System log security descriptor is configured through the following registry key: |
| 59 | + |
| 60 | +`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\CustomSD` |
| 61 | + |
| 62 | +The security descriptor is specified using the Security Descriptor Definition Language (SDDL) syntax. The SDDL should grant the SYSTEM account Read, Write, and Clear permissions in the following context: |
| 63 | + |
| 64 | +`(A;;0xf0007;;;SY)` |
| 65 | + |
| 66 | +The value of SY (SYSTEM account) is `7`, which means Read(1)+Write(2)+Clear(4). If not, change it to `7` so it has the proper permissions to the System event log. Once the SDDL of the SYSTEM account has been corrected, restart the machine and check if the Task Scheduler service is started. |
| 67 | + |
| 68 | +You can also check the SDDL of the System event log by running the following command: |
| 69 | + |
| 70 | +```console |
| 71 | +wevtutil get-log "SYSTEM" |
| 72 | +``` |
| 73 | + |
| 74 | +The default values should look like: |
| 75 | + |
| 76 | +```output |
| 77 | +name: SYSTEM |
| 78 | +enabled: true |
| 79 | +type: Admin |
| 80 | +isolation: System |
| 81 | +channelAccess: O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x3;;;BO)(A;;0x5;;;SO)(A;;0x1;;;IU)(A;;0x3;;;SU)(A;;0x1;;;S-1-5-3)(A;;0x2;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573) |
| 82 | +``` |
| 83 | + |
| 84 | +For more information about how to modify the event log SDDL, see [Set event log security locally or via Group Policy](../../windows-server/group-policy/set-event-log-security-locally-or-via-group-policy.md). |
| 85 | + |
| 86 | +If that doesn't resolve the issue and you still can't start the Task Scheduler service, see the [Additional resources](#additional-resources) section. |
| 87 | + |
| 88 | +## Error 126: The specified module could not be found |
| 89 | + |
| 90 | +This error occurs because a file related to the Task Scheduler service is missing or can't be found. |
| 91 | + |
| 92 | +In this case, a required system file is missing, or the Task Scheduler service refers to an invalid file under its registry configuration. |
| 93 | + |
| 94 | +Determine if the service is configured correctly under its registry configuration: |
| 95 | + |
| 96 | +1. Open Registry Editor. |
| 97 | +2. Go to the Task Scheduler service location under the following path: |
| 98 | + |
| 99 | + `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Parameters` |
| 100 | + |
| 101 | +3. In the right pane, check if the registry value `ServiceDll` has the value data of `%systemroot%\system32\schedsvc.dll`. |
| 102 | +4. If it does, check if the **schedsvc.dll** file exists under **%systemroot%\system32**. |
| 103 | +5. If the DLL file is missing, [use the System File Checker tool to repair missing or corrupted system files](https://support.microsoft.com/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e). |
| 104 | +6. Once the repair is done, start the Task Scheduler service. |
| 105 | + |
| 106 | +If that doesn't resolve the issue and you still can't start the Task Scheduler service, see the [Additional resources](#additional-resources) section. |
| 107 | + |
| 108 | +## Additional resources |
| 109 | + |
| 110 | +Use the following event logs to view additional information about the service start failure: |
| 111 | + |
| 112 | +- System event logs |
| 113 | +- Application event logs |
| 114 | +- Task Scheduler event logs under: |
| 115 | + |
| 116 | + - **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **TaskScheduler** > **Maintenance** |
| 117 | + - **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **TaskScheduler** > **Operational** |
| 118 | + |
| 119 | +## Contact Microsoft Support |
| 120 | + |
| 121 | +If the preceding steps can't resolve the issue, contact Microsoft Support for further assistance. |
0 commit comments