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:
- Confirm the Task Scheduler service is running and set to Automatic.
- Check that the task is enabled and the trigger conditions are correct.
- Verify the user account running the task has the necessary permissions.
- Review the task's Last Run Result and History for error codes.
- 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.
- Press
Win + R, typeservices.msc, and press Enter. - Scroll down and double-click Task Scheduler.
- Set Startup type to Automatic.
- If the service is stopped, click Start.
- Click OK and close the Services console.
Verify the Task Is Enabled and Configured Correctly
- Open Start, search for Task Scheduler, and launch it.
- Locate your task in the relevant folder under Task Scheduler Library. Confirm it is not hidden and is not located in a non-standard folder.
- Confirm the Status column shows Ready, not Disabled.
- In the right-hand Actions pane, click Enable if it appears.
- 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. If the task should run regardless of who is logged on a shared workstation, confirm it is not restricted to a specific user account.
- Triggers: Confirm the schedule is active and not set to Disabled. Check for any network conditions that might prevent execution.
- 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.
- 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. Task Scheduler history requires the Windows Event Log service to be running.
- Press
Win + R, typeservices.msc, and press Enter. - Confirm the Windows Event Log service is running and set to Automatic.
- In Task Scheduler, click Enable All Tasks History in the right-hand Actions pane.
- Wait for the next scheduled run or right-click the task and select Run.
- Select the History tab at the bottom of the middle pane.
- 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.
- Double-click the task and go to the General tab.
- Click Change User or Group.
- Enter the correct account (for system tasks use
SYSTEM, for user tasks use your account or a dedicated service account). - Click OK, then re-enter the password when prompted.
- Click OK to save.
Check Power and Sleep Settings
Windows will not wake the computer from sleep to run most tasks unless explicitly configured.
- Open Settings from the Start menu.
- Go to System then Power & battery.
- Under Screen and sleep, adjust the sleep timers to prevent the computer from sleeping during scheduled task windows.
- Click Additional power settings to open Control Panel.
- Select Change advanced power settings.
- Expand Sleep then Allow wake timers.
- Set both On battery and Plugged in to Enable.
- 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.
C:\Windows\System32\Tasks, export any tasks you wish to keep. Right-click each task in Task Scheduler and select Export to save a backup copy.- Open an elevated Command Prompt by right-clicking Start and selecting Terminal (Admin).
- Run the following commands one at a time:
net stop Schedulenet start Schedule
- Close the terminal and reopen Task Scheduler.
Test with a Simple Task
To isolate whether the issue is task-specific or affects the scheduler as a whole, create a simple test task:
- Open Task Scheduler and click Create Basic Task.
- Name it Test Task and set a trigger to run one minute from now.
- Set the action to start a program and enter
notepad.exeorcalc.exe. - Complete the wizard and wait for the scheduled time.
- If the simple task runs but your original task does not, the issue is specific to the original task's configuration, permissions, or script.
- If the simple task also fails, the issue is scheduler-wide and you should continue with the service and component checks in this guide.
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. Tasks configured to Run whether user is logged on or not run in Session 0 and cannot display a UI. Modify the script to write output to a log file instead of attempting to show a window.
Event Viewer Diagnostics
For deeper diagnostics beyond Task Scheduler history, open Event Viewer:
- Press
Win + R, typeeventvwr.msc, and press Enter. - Navigate to Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational.
- Review error and warning events for detailed failure information that may not appear in the Task Scheduler History tab.
Still Having Issues?
💻 Open a Ticket