Introduction

Windows Task Scheduler not running usually means one of three things: the scheduler service itself is unhealthy, the task never met its trigger conditions, or the task launched but immediately failed under a non-elevated or restricted account. The right fix comes from separating those layers instead of just clicking Run again.

Symptoms

  • Scheduled tasks never start at the expected time
  • Running the script manually works, but the scheduled task does not
  • Task History is empty, disabled, or shows failure codes
  • The issue appears after account, policy, or reboot changes

Common Causes

  • The Task Scheduler service is stopped or unhealthy
  • Trigger conditions such as idle state, AC power, or network availability prevent execution
  • The task runs without the privileges or account rights it needs
  • Task history or recent policy changes hide the real startup failure

Step-by-Step Fix

  1. 1.Check the Task Scheduler service itself
  2. 2.Confirm the scheduler service is running before looking at one task in isolation.
powershell
Get-Service Schedule
  1. 1.Inspect task history and result codes
  2. 2.Use Task Scheduler history or PowerShell to see whether the task launched and failed, or never launched at all.
powershell
Get-ScheduledTask -TaskName \"MyTask\" | Get-ScheduledTaskInfo
  1. 1.Review trigger and condition settings
  2. 2.Conditions such as idle, power, or network can prevent a task from starting even when the schedule is correct.
  3. 3.Verify run level and account rights
  4. 4.If the task needs elevation or service-style rights, correct those before testing again.

Prevention

  • Keep Task Scheduler history enabled on critical systems
  • Document trigger conditions and run level requirements with the task itself
  • Test scheduled tasks after policy, account, or reboot-related changes
  • Monitor the scheduler service and task result codes for silent failures