How to fix Windows 11 Task Scheduler not running scheduled tasks or triggers

Summary

This guide helps you troubleshoot and resolve: How to fix Windows 11 Task Scheduler not running scheduled tasks or triggers. Follow the steps below to fix the issue.

Common Causes

When Windows 11 Task Scheduler fails to run your scheduled tasks or triggers, it can disrupt backups, script automation, and other essential processes. This guide walks you through diagnosing and resolving the most common causes, from simple service checks to permission and corruption issues. Most problems can be fixed without reinstalling Windows, but if you need a fresh start, our clean installation guide can help.

Quick Fix Steps

Before diving into detailed troubleshooting, try these common fixes in order:

1. Confirm the Task Scheduler service is running and set to Automatic.
2. Check that the task is enabled and the trigger conditions are correct.
3. Verify the user account running the task has the necessary permissions.
4. Review the task's Last Run Result and History for error codes.
5. Run the task manually using Run to test it outside its schedule.

Detailed Instructions

Check the Task Scheduler Service

The Task Scheduler depends on a background service that must be running. If it has stopped or is disabled, no scheduled tasks will execute.

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down and double-click Task Scheduler.
3. Set Startup type to Automatic.
4. If the service is stopped, click Start.
5. Click OK and close the Services console.

Verify the Task Is Enabled and Configured Correctly

1. Open Start, search for Task Scheduler, and launch it.
2. Locate your task in the relevant folder under Task Scheduler Library.
3. Confirm the Status column shows Ready, not Disabled.
4. In the right-hand Actions pane, click Enable if it appears.
5. Double-click the task and review each tab:
   • General: Ensure Run whether user is logged on or not matches your needs and the user account is correct.
   • Triggers: Confirm the schedule is active and not set to Disabled.
   • Conditions: Uncheck Start the task only if the computer is on AC power if you use a laptop on battery.
   • Settings: Tick Allow task to be run on demand and If the task fails, restart every if appropriate.
6. Click OK to save any changes.

Review History and Error Codes

The History tab provides detailed information about why a task failed. By default, history is disabled for all tasks.

1. In Task Scheduler, click Enable All Tasks History in the right-hand Actions pane.
2. Wait for the next scheduled run or right-click the task and select Run.
3. Select the History tab at the bottom of the middle pane.
4. Look for red error entries and note the event ID and result code.

Common result codes include:

• 0x0: Success.
• 0x1: Incorrect function, often a path or permission issue.
• 0x800710E0: The operator or administrator has refused the request.
• 0x80070005: Access denied. The user account lacks permission.
• 0x80070002: File not found. Check script paths and dependencies.

Fix Permission and Credential Issues

Tasks that run while no one is logged in must store credentials securely. If the password has changed or the account is locked, the task will fail.

1. Double-click the task and go to the General tab.
2. Click Change User or Group.
3. Enter the correct account (for system tasks use SYSTEM, for user tasks use your account or a dedicated service account).
4. Click OK, then re-enter the password when prompted.
5. Click OK to save.

Check Power and Sleep Settings

Windows will not wake the computer from sleep to run most tasks unless explicitly configured.

1. Open Settings from the Start menu.
2. Go to System then Power & battery.
3. Click the arrow next to the active power plan and choose Change plan settings.
4. Select Change advanced power settings.
5. Expand Sleep then Allow wake timers.
6. Set both On battery and Plugged in to Enable.
7. Click Apply then OK.

Repair Corrupted Task Scheduler Data

If Task Scheduler itself is broken, the underlying XML files in C:\Windows\System32\Tasks may be corrupted. You can reset the service to rebuild its cache.

1. Open an elevated Command Prompt by right-clicking Start and selecting Terminal (Admin).
2. Run the following commands one at a time:
   • net stop Schedule
   • net start Schedule
3. Close the terminal and reopen Task Scheduler.

Re-register the Task Scheduler Components

If the service starts but tasks still fail to trigger, the underlying COM components may need re-registration.

1. Open an elevated Command Prompt.
2. Run each of the following commands, pressing Enter after each:
   • regsvr32 /s schedsvc.dll
   • regsvr32 /s mstask.dll
3. Restart the computer when finished.

Troubleshooting

Task Runs Manually but Not on Schedule

This usually points to trigger conditions or power settings. Re-check the Triggers tab for any delay or sync settings, and confirm the computer is awake at the scheduled time. If the task is set to Start only if the computer is idle, any user activity will delay it indefinitely.

Script Tasks Fail with "Access Denied"

Ensure the script's folder allows read access for the account running the task. Network paths require either a UNC path with stored credentials or mapping the drive under the same account using net use in a wrapper script.

Tasks Disappear After Reboot

This typically indicates corruption in the Tasks folder or insufficient permissions on C:\Windows\System32\Tasks. Run sfc /scannow from an elevated Command Prompt to scan for system file corruption.

Tasks Run but Produce No Visible Result

If the task launches but the script or program completes silently, check that the script does not require an interactive desktop session. For tasks set to Run whether user is logged on or not, the process runs in a non-interactive session, so any UI prompts or console output will not be visible. Redirect output to a log file within the script to confirm it is executing correctly.

Still Having Issues?