Windows Schedule Reboot: Automate Restarts in 2026

There's a specific kind of dread that comes from watching a production server go down at 2:47 PM on a Tuesday. I've lived it — a colleague had kicked off a Windows Update install, forgotten to set a maintenance window, and the machine decided to finish the job right in the middle of the quarterly close. The fix wasn't complicated. What was missing was a simple, reliable way to schedule a reboot in advance.

The good news: you don't need third-party software to set up a Windows schedule reboot. Every tool you need ships with Windows, whether you're managing Windows 11, Windows 10, or Windows Server. This 2026 guide covers the built-in methods — Task Scheduler, the shutdown /r command, PowerShell, and Group Policy — with copy-paste steps and a few lessons I've picked up over fifteen years of managing Windows fleets. Whether you need a one-time restart or a recurring scheduled task trigger, there's a working approach below.

Why Should You Schedule a Reboot on Windows?

A reboot is the Windows equivalent of a good night's sleep. It clears memory leaks, resets stuck services, and finally applies those updates that have been sitting in a pending state for days. When you control the schedule, you control the "when" — which is often the difference between a non-event and a ticket storm.

The most common reasons teams schedule a reboot:

• Updates that refuse to finish. If the machine never restarts, security patches stay in a pending reboot state and never fully apply.
• Performance degradation. Windows and the applications running on it accumulate memory bloat over time. A nightly or weekly restart flushes that out.
• Servers and unattended desktops that need predictable maintenance. Nobody should have to wake up at 3:00 AM to reboot a machine manually.

The cost of getting this wrong is real. Gartner estimates the average cost of IT downtime at $5,600 per minute [需核实], and a single unplanned reboot during business hours can burn through that in a hurry.

Method 1: Schedule an Automatic Restart with Task Scheduler

Task Scheduler is the most reliable way to set this up. It's been part of Windows for over two decades and behaves consistently across Windows 11, Windows 10, and Server.

Create a Basic Task for a One-Time or Daily Reboot

The fastest path:

1. Press Win+R, type taskschd.msc, and hit Enter.
2. In the right-hand actions panel, click Create Basic Task.
3. Name it something obvious like "Nightly Reboot." Six months from now, you won't remember what "Task 12" does.
4. Choose Daily, Weekly, or One time. For a daily reboot, pick a time when nobody is using the machine. I typically recommend 3:00 AM, but make sure it doesn't overlap with your backup window.
5. For the action, select Start a program.
6. Set Program/script to shutdown and Add arguments to /r /t 0.

The /r flag restarts the machine; /t 0 removes the default 60-second delay. If you want users to see a countdown before the restart, use /t 300 instead — five minutes is usually enough to save work.

For multi-site deployments, check Synchronize across time zones in the trigger settings. Otherwise, a 3:00 AM restart in New York fires at 3:00 AM local time everywhere, which completely defeats your intent.

Configure Security Options So the Reboot Runs Without User Login

This is where I've seen more scheduled reboots fail than anywhere else. If the task runs under your personal account and "Run only when user is logged on" is selected, the reboot won't fire unless you're signed in. On a server or unattended workstation, that's a deal-breaker.

In the task's General tab:

• Select Run whether user is logged on or not.
• Set the user to NT AUTHORITY\SYSTEM or a dedicated service account.
• Check Run with highest privileges.
• If the machine sleeps overnight, check Wake the computer to run this task in the Conditions tab.

Using a regular account is a ticking clock — the task breaks the day that password changes. I debugged a call at 2:00 AM once for exactly that reason.

Method 2: Windows Schedule Reboot from the Command Line (shutdown /r + schtasks)

Task Scheduler's GUI is fine — until you need to deploy the same task to thirty machines. That's when the command line becomes your friend.

The Easiest One-Line Scheduled Reboot Command

Open Command Prompt as Administrator and run:

schtasks /create /tn "ScheduledReboot" /sc daily /st 03:00 /tr "shutdown /r /t 0"

That creates a scheduled task named "ScheduledReboot" that fires at 3:00 AM every day and restarts the machine immediately. For a one-time reboot, swap /sc daily for /sc once and add the date:

schtasks /create /tn "OneTimeReboot" /sc once /st 22:00 /sd 12/31/2026 /tr "shutdown /r /t 0"

Need to force-close applications that might block the restart? Add /f:

schtasks /create /tn "ScheduledReboot" /sc daily /st 03:00 /tr "shutdown /r /f /t 0"

A quick caution: /f closes programs without saving. If users might have unsaved work, skip it or use a longer /t delay instead.

Manage Scheduled Reboot Tasks with schtasks

You won't always get things right the first time. Here's the command reference for managing the task:

Method 3: Use PowerShell to Schedule Automatic Reboots

PowerShell is my go-to when I need more control than schtasks offers — especially for remote machines or tasks with custom conditions.

Register a Scheduled Task with PowerShell

The ScheduledTasks module gives you a clean, scriptable way to create reboot tasks. Here's a copy-paste script for a daily 3:00 AM restart:

$trigger = New-ScheduledTaskTrigger -Daily -At 3:00AM

$action = New-ScheduledTaskAction -Execute 'shutdown.exe' -Argument '/r /t 0'

Register-ScheduledTask -TaskName 'ScheduledReboot' -Action $action -Trigger $trigger -User 'SYSTEM' -Force

The -Force flag overwrites an existing task with the same name, which makes re-deployment painless.

One thing I learned the hard way: if you omit -User 'SYSTEM', the task registers under your account and breaks the day your password expires. That's a classic 2:00 AM page.

Reboot a Remote Computer on a Schedule with PowerShell

For remote machines, you can create the scheduled task on the target system via PowerShell Remoting:

Invoke-Command -ComputerName WEB-SRV01 -ScriptBlock {
    $trigger = New-ScheduledTaskTrigger -Daily -At 3:00AM
    $action = New-ScheduledTaskAction -Execute 'shutdown.exe' -Argument '/r /t 0'
    Register-ScheduledTask -TaskName 'ScheduledReboot' -Action $action -Trigger $trigger -User 'SYSTEM' -Force
}

This requires WinRM to be enabled and your account to have admin rights on the remote host. For immediate, ad-hoc reboots, keep it simple:

Restart-Computer -ComputerName WEB-SRV01 -Force

Control Windows Update Reboot Schedule with Active Hours and Group Policy

If Windows Update keeps forcing reboots at awkward moments, you're solving the wrong problem. Windows includes controls designed specifically to prevent that.

Set Active Hours to Stop Unwanted Restarts

Active hours tell Windows when you're typically using the machine, so it won't auto-restart during that stretch. In Windows 11: Settings → Windows Update → Advanced options → Active hours. You can set a manual range — up to 18 hours — or let Windows learn your usage patterns and adjust automatically. Windows 10 offers the same feature under Settings → Update & Security → Windows Update → Change active hours.

A practical approach: set active hours to cover the full day except a small overnight window (say, 3:00 AM to 5:00 AM) for updates and restarts. Then pair that with your own scheduled reboot task for consistent maintenance.

Use Group Policy to Enforce Reboot Maintenance Windows

On domain-joined machines, Group Policy gives you central control. Navigate to:

Computer Configuration → Administrative Templates → Windows Components → Windows Update

The policies that matter:

• Configure Automatic Updates — set a scheduled install day and time.
• No auto-restart with logged-on users — prevents forced restarts while someone is signed in.
• Deadline policies — enforce reboots after a pending reboot state persists for a set number of days.

These policies require Windows Pro, Enterprise, or Server. On Windows 11 Home, use Task Scheduler or PowerShell instead.

Windows Server Schedule Reboot: Maintenance Window Best Practices

Scheduling a reboot on a server has more at stake than on a workstation. A badly timed restart can drop a database mid-transaction or terminate active VPN sessions. Over the years, I've settled on a few practices that consistently prevent pain.

Plan a Server Restart Schedule That Avoids Disruption

• Choose quiet hours based on actual usage data, not assumptions. If you're unsure when your server is quiet, check Performance Monitor or your monitoring tool before setting the schedule.
• Stagger restarts in clustered services. Rebooting three web servers simultaneously behind a load balancer defeats the purpose of redundancy.
• Verify backup jobs don't overlap your restart window. A reboot during an open-file backup is a classic route to a corrupted backup set.
• Align restarts with your organization's change-management calendar, even for automated tasks.

Trigger a Restart After Update Installation

A fixed schedule isn't always what you need. Sometimes you want the reboot to happen as soon as updates finish installing. Windows records a pending reboot state in the registry:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

You can also watch for event ID 19 from the Windows Update Client source in the System log, which signals that a restart is required. A minimal PowerShell check:

$rebootRequired = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired"
if ($rebootRequired) {
    Restart-Computer -Force
}

I've deployed this exact script in more client environments than I can count. It closes the gap between "updates installed" and "machine actually restarted."

Troubleshooting: Scheduled Restart Not Working or Windows Keeps Restarting

So you set up the task, waited overnight, and nothing happened. Or worse — Windows is stuck in a restart loop. Both are fixable.

Why Won't My Scheduled Reboot Task Trigger?

Start with Task Scheduler. Open your task and inspect Last Run Time and Last Task Result. A result of 0x0 means the task ran successfully, so the problem is in your command or arguments. 0x41303 means the task hasn't run at all yet.

The most common culprits I see:

• The task runs under a user whose password expired. This is the #1 cause.
• The machine was asleep or off at the scheduled time. Enable Wake the computer to run this task.
• The Task Scheduler service was disabled by group policy or security software.

And check the argument itself. I've debugged "failed" reboots where the action was shutdown /s instead of /r. It happens.

How to Stop an Unwanted Reboot Loop

If Windows is caught in a restart loop, first abort any pending restart:

shutdown /a

If the loop is caused by a recent update or driver, boot into Windows Recovery Environment (hold Shift while clicking Restart on the login screen) and uninstall the offending update from Advanced options → Update History → Uninstall updates.

Windows 11 Home Limitations and Third-Party Tool Alternatives

Windows 11 Home doesn't include Group Policy Editor, so your options are Task Scheduler and PowerShell — both work perfectly fine.

Frequently Asked Questions

Can I set my PC to restart at a certain time?

Yes. The fastest method: press Win+R, type taskschd.msc, click Create Basic Task, set the trigger to your desired time, and use shutdown with argument /r for the action. For a no-GUI version:

schtasks /create /tn "RebootAt3" /sc once /st 03:00 /tr "shutdown /r /t 0"

The PC must be powered on — or support wake timers — at the scheduled time.

How do I schedule a daily restart in Windows 11?

Open Task Scheduler, create a Basic Task with a Daily trigger, set the time, and use shutdown /r as the action. The PowerShell equivalent:

$trigger = New-ScheduledTaskTrigger -Daily -At 3:00AM
$action = New-ScheduledTaskAction -Execute 'shutdown.exe' -Argument '/r /t 0'
Register-ScheduledTask -TaskName 'DailyReboot' -Action $action -Trigger $trigger -User 'SYSTEM' -Force

Set Active Hours under Windows Update as well, so the update service doesn't override your chosen restart time.

What command schedules a shutdown and restart in Windows?

Two commands work together: shutdown /r restarts the machine (add /t 0 for zero delay), and schtasks /create schedules when that command runs. The standard combination:

schtasks /create /tn "ScheduledReboot" /sc daily /st 03:00 /tr "shutdown /r /t 0"

Why does Windows reboot automatically after updates?

Windows Update requires a reboot to finalize critical updates. If a pending reboot state exists, Windows will eventually restart the machine, usually during inactive hours. Active Hours and Group Policy can limit when those restarts happen, but after several days — or for urgent security patches — Windows may override active hours to complete installation.

Final Thoughts

All the built-in methods — Task Scheduler, schtasks, and PowerShell — are reliable for a Windows schedule reboot. Match the method to your environment: the GUI for one-off tasks, scripts for automation, and Group Policy for enterprise control.

When something fails, don't assume it's Windows being Windows. Check the task's account permissions, verify the trigger, and confirm the Task Scheduler service is running. In my experience, 90% of "scheduled reboot not working" issues trace back to one of those three.

Bookmark this guide for the next time a reboot catches you off guard, share it with your IT team, and if you're still stuck, drop a comment below — I'll help you get your scheduled reboot working.