To view all scheduled tasks, use schtasks; for detailed info, use schtasks /query; for specific formats, use /fo LIST, CSV, or TABLE; to view a specific task, use schtasks /query /tn "TaskName" with the full hierarchical name. 2. To create a task, use schtasks /create /tn "TaskName" /tr "path" /sc schedule /st time, optionally adding /sd, /ru, /rp, and /f; for example, schedule a weekly backup with specific days and SYSTEM account. 3. To run a task immediately, use schtasks /run /tn "TaskName"; to stop it, use schtasks /end /tn "TaskName"; to delete, use schtasks /delete /tn "TaskName", adding /f to force without confirmation. 4. To modify a task, use schtasks /change to update the run path, user, or password, but to change schedule, delete and recreate the task using /create /f. Key tips include using exact task names, quoting paths with spaces, leveraging SYSTEM account to avoid logon issues, verifying tasks in GUI if issues arise, and exporting/importing tasks via XML for deployment across systems, ensuring reliable automation through command-line control.

The schtasks command in Windows is a powerful command-line tool that lets you create, modify, view, and delete scheduled tasks. It's useful for automating scripts, managing maintenance tasks, or troubleshooting scheduled jobs—especially on servers or in scripts where GUI access isn't available.

Here’s how to use schtasks effectively for common task management operations.

1. Viewing Scheduled Tasks

To list all scheduled tasks on the system:

schtasks

For more detailed information, including the next run time and status:

schtasks /query

To see tasks in a table format with specific columns:

schtasks /query /fo LIST

Or in CSV format (useful for exporting):

schtasks /query /fo CSV > tasks.csv

To view a specific task:

schtasks /query /tn "TaskName"

Replace "TaskName" with the actual name of the task. Task names are hierarchical, like \Microsoft\Windows\Defrag\ScheduledDefrag.

2. Creating a Scheduled Task

Use schtasks /create to define a new task.

Basic syntax:

schtasks /create /tn "TaskName" /tr "C:\path\to\script.bat" /sc DAILY /st 09:00

• /tn – Task name (required)
• /tr – Task to run (program or script path)
• /sc – Schedule (e.g., ONCE, DAILY, WEEKLY, MONTHLY, MINUTE)
• /st – Start time (24-hour format, e.g., 09:30)
• /sd – Start date (optional, format: MM/DD/YYYY)
• /ru – User account to run the task (e.g., SYSTEM or DOMAIN\User)
• /rp – Password (if user requires one)
• /f – Force overwrite if task already exists

Example: Run a backup script every weekday at 8 PM

schtasks /create /tn "WeeklyBackup" /tr "C:\Scripts\backup.bat" /sc WEEKLY /d MON,TUE,WED,THU,FRI /st 20:00 /ru SYSTEM /f

Note: Running as SYSTEM avoids password prompts and is common for admin tasks.

3. Running, Stopping, and Deleting Tasks

• Run a task immediately:

schtasks /run /tn "TaskName"

Useful for testing without waiting for the schedule.

• Stop a currently running task:

schtasks /end /tn "TaskName"

• Delete a task:

schtasks /delete /tn "TaskName"

You’ll be prompted to confirm. Add /f to force deletion without confirmation:

schtasks /delete /tn "TaskName" /f

4. Modifying or Updating a Task

You can't directly "edit" a task, but you can recreate it with /create /f to overwrite.

Alternatively, use /change to update certain properties:

schtasks /change /tn "TaskName" /tr "C:\New\Script.bat" /ru "DOMAIN\User" /rp "Password123"

This changes the program to run and the user account, but doesn't alter the schedule.

For full changes (like frequency or time), you’ll need to delete and recreate the task.

Common Pitfalls & Tips

• Task names are case-sensitive in behavior: While they may display in mixed case, referencing them incorrectly can cause errors. Use exact names from /query.
• Paths with spaces: Always wrap paths in quotes: /tr "C:\My Scripts\run.bat"
• Run whether user is logged on or not: The GUI option isn't directly available in schtasks, but you can achieve it using /ru with a user and /rp, or by using schtasks in combination with XML import (advanced).
• Use Task Scheduler GUI to inspect: If a command-created task isn’t behaving, open Task Scheduler to verify triggers, conditions, and security options.

Bonus: Export and Import Tasks (Advanced)

You can export a task to XML via GUI or command:

schtasks /query /tn "TaskName" /xml > task.xml

Then import it on another machine:

schtasks /create /tn "TaskName" /xml task.xml

This is great for deploying consistent tasks across multiple systems.

Using schtasks gives you precise control over automation in Windows environments—especially useful in batch scripts, remote administration, or unattended setups.

Basically, once you know the key switches (/tn, /tr, /sc, /st), most tasks become just a one-liner. Just remember to test with /run after creating.

The above is the detailed content of How to use the schtasks command to manage scheduled tasks in Windows. For more information, please follow other related articles on the PHP Chinese website!