Windows Task Scheduler

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Task Scheduler (taskschd.msc) is a component of Microsoft Windows that provides the ability to schedule the launch of programs or scripts at pre-defined times or after specified time intervals. It was first introduced in the Windows 95 Plus! pack as System Agent[1] but was renamed to Task Scheduler in Windows 98. The Windows Event Log service must be running before the Task Scheduler starts up.

This service should not be confused with the scheduler that allocates CPU resources to processes already in memory.


Task Scheduler 1.0[edit]

Task SchedulerX 1.0 is included with Windows 2000, Windows XP and Windows Server 2003.[2] It runs as a Windows Service, and the task definitions and schedules are stored in binary .job files. Tasks are manipulated directly by manipulating the .job files. Tasks can be added or deleted by using command-line tool AT or schtasks.[3] Each task corresponds to single action. On Windows 95, Windows 98 and Windows Me, the Task Scheduler runs as an application (mstask.exe). It also displays a status icon in the notification area on Windows 95 and Windows 98 and runs as a hidden service on Windows Me, but can be made to show a tray icon.[4] On the Windows NT family of operating systems, it is implemented as a Windows service.Task Scheduler 1.0 exposes an API to programmatically create tasks. It is accessed via the ITaskScheduler COM interface.

Microsoft provides a scheduling agent DLL, a sample VBScript and a configuration file to automate the Windows 2000/XP Task Scheduler.[5]

Task Scheduler 2.0[edit]

Task Scheduler 2.0 in Windows 7

Task Scheduler 2.0 was introduced with Windows Vista and included in Windows Server 2008 as well.[2] The redesigned Task Scheduler user interface is now based on Management Console. In addition to running tasks on scheduled times or specified intervals, Task Scheduler 2.0 also supports calendar and event-based triggers, such as starting a task when a particular event is logged to the event log, or when a combination of events has occurred. Also, several tasks that are triggered by the same event can be configured to run either simultaneously or in a pre-determined chained sequence of a series of actions, instead of having to create multiple scheduled tasks. Tasks can also be configured to run based on system status such as being idle for a pre-configured amount of time, on startup, logoff, or only during or for a specified time. XPath expressions can be used to filter events from the Windows Event Log. Tasks can also be delayed for a specified time after the triggering event has occurred, or repeat until some other event occurs. Actions that need to be done if a task fails can also be configured. The actions that can be taken in response to triggers, both event-based as well as time-based, not only include launching applications but also take a number of custom actions. Task Scheduler includes a number of actions built-in, spanning a number of applications; including send an e-mail, show a message box, or fire a COM handler when it is triggered. Custom actions can also be specified using the Task Scheduler API. Task Scheduler keeps a history log of all execution details of all the tasks. .[6] Windows Vista uses Task Scheduler 2.0 to run various system-level tasks;[7] consequently, the Task Scheduler service can no longer be disabled (except with a simple registry tweak).

Task Scheduler 2.0 exposes an API to programmatically create tasks. It is accessed via the ITaskService COM interface.[8] The Windows API does not, however, include a managed wrapper for Task Scheduler though an open source implementation exists. The Task Scheduler API is also exposed for scripting languages, including VBScript, JScript and Windows PowerShell.[9] The job files for Task Scheduler 2.0 are XML-based, and are human-readable, conforming to the Task Scheduler Schema.[8] Although possible, Microsoft advises not to create the job files by hand, and instead, use the Task Scheduler API. A command line utility for using Task Scheduler is also provided in terms of the schtasks.exe command.[10]

Other features[edit]

  • New security features, including using Credential Manager to store passwords for tasks on workgroup computers and using Active Directory for task credentials on domain-joined computers so that they cannot be retrieved easily. Also, scheduled tasks are executed in their own session, instead of the same session as system services or the current user.
  • Ability to wake up a machine remotely or using BIOS timer from sleep or hibernation to execute a scheduled task or run a previously scheduled task after a machine gets turned on.
  • Ability to attach tasks to events directly from the Event Viewer.


The Task Scheduler service works by managing Tasks; Task refers to the action (or actions) taken in response to trigger(s). A task is defined by associating a set of actions, which can include launching an application or taking some custom-defined action, to a set of triggers, which can either be time-based or event-based. In addition, a task also can contain metadata that defines how the actions will be executed, such as the security context the task will run in. Tasks are serialized to .job files and are stored in the special folder titled Task Folder, organized in subdirectories. Programmatically, the task folder is accessed using the ITaskFolder interface or the TaskFolder scripting object and individual tasks using the IRegisteredTask interface or RegisteredTask object.[11]

Column 'Last Result'[edit]

The Last Result column displays a completion code. The common codes for scheduled tasks are:[12]

  • 0x0: The operation completed successfully.
  • 0x1: An incorrect function was called or an unknown function was called.
  • 0xa: The environment is incorrect.


On Windows 2000 and Windows XP, tasks assigned to run with SYSTEM privileges do not function when the computer is prepared for disk imaging with sysprep. Sysprep changes security identifier (SID) to avoid duplication but does not update scheduled tasks to use the new SID. Consequently, all SYSTEM scheduled tasks fail to run on the imaged computers. There is no solution for this problem but one may reschedule the tasks to work around the issue.[13]

On Windows Vista or Windows Server 2008, where Service Pack 2 is not installed, the next execution time displayed in Task Scheduler may be wrong.[14]

On Windows Vista, 7, 2008, and 2008 R2: The MMC Component says that you are running "Task Scheduler 1.0" when in fact you are running 2.0, this is a trivial bug so it wasn't noticed, and is likely due to the re-write of the task scheduler. The Version has been corrected to 2.0 in Windows 8, and 2012

See also[edit]


  1. ^ Al Fasoltd. "Windows 98: Stable and fast, as well as 'new and improved'". The Syracuse Newspapers. Retrieved 2007-10-06. 
  2. ^ a b "About the Task Scheduler". Retrieved 2007-10-06. 
  3. ^ How To Use the AT Command to Schedule Tasks
  4. ^ How to Enable the Scheduled Tasks Icon in Windows Me
  5. ^ Task Scheduler Using VBScript
  6. ^ "Windows Vista Task Scheduler". Microsoft TechNet. March 3, 2006. Retrieved 2006-04-24. 
  7. ^ Description of the scheduled tasks in Windows Vista
  8. ^ a b Kenny Kerr. "Task Scheduler 2.0". MSDN. Retrieved 2007-10-06. 
  9. ^ "Task Scheduler Reference". Retrieved 2007-10-06. 
  10. ^ "Schtasks.exe (Windows)". Retrieved 2007-10-06. 
  11. ^ "Tasks (Windows)". MSDN. Retrieved 2007-10-06. 
  12. ^ "How to troubleshoot scheduled tasks in Windows XP and in Windows Server 2003". Microsoft Support. Microsoft. 22 May 2013. Retrieved 3 Sep 2013. 
  13. ^ "Scheduled tasks may not start if you used a System Preparation image to install Windows XP or Windows 2000". Microsoft Support. Microsoft. 1 July 2004. Retrieved 19 May 2012. 
  14. ^ "The value in the Next Run Time field in Task Scheduler is incorrect in Windows Vista and in Windows Server 2008". Microsoft Support. Microsoft. 15 October 2008. Retrieved 19 May 2012. 

External links[edit]