0x000004A6: A system shutdown is already scheduled

This pops up when Windows already has a pending shutdown, restart, or logoff. The fix is usually canceling that scheduled action or clearing the scheduled tasks holding it.

The 30-Second Fix: Cancel the Scheduled Shutdown

What's actually happening here is that Windows has a pending shutdown (or restart, or logoff) triggered by something — usually a user command, an update installer, or a scheduled task. The OS won't let you start another shutdown until you cancel the first one.

Open Command Prompt as Administrator (hit Win+X and choose Terminal Admin). Run:

shutdown /a

The /a flag stands for abort. It cancels any pending system shutdown, restart, or logoff. If you see a message like "A system shutdown has already been scheduled", the abort should succeed immediately. You'll get a balloon notification saying "The scheduled shutdown has been cancelled."

This works for about 90% of cases. The reason it's so effective is that Windows queues shutdown as a single pending state — you can only have one active shutdown request, and shutdown /a removes it entirely, regardless of what triggered it.

The 5-Minute Fix: Check for Hidden Scheduled Tasks

If shutdown /a fails (maybe it says "No system shutdown is in progress") but the error still shows up when you try to shut down or install something, then the pending shutdown is likely held by a scheduled task or Windows Update itself.

First, open Task Scheduler (hit Win+R, type taskschd.msc, press Enter). Navigate to Task Scheduler Library and look for any task named something like "Shutdown", "Restart", "UpdateOrchestratorReboot", or "RebootTask". Right-click and disable or delete it.

Second, check for pending Windows Update actions. Open Settings > Update & Security > Windows Update > View update history. Look for any update marked "Pending restart". If you see one, go back to the main Update page and click Restart now — let it complete. That clears the pending state.

If you're in a corporate environment, Group Policy might be forcing a scheduled shutdown. Open Command Prompt as Admin and run:

gpresult /h C:\gpresult.html

Open that HTML file and search for "shutdown" or "logoff". You'll see if a policy is enforcing a shutdown at a specific time.

The 15+ Minute Fix: Manual Cleanup in Registry and Task Scheduler

When neither of the above works, something has corrupted the shutdown state. This is rare but happens after a Windows update that failed mid-install, or if a third-party tool (like a VPN or remote management app) left a dangling shutdown request.

Launch Task Scheduler as Admin. Go to Task Scheduler Library and sort by Triggers. Look for tasks with a trigger set to "At system startup" or "On an event" that execute shutdown.exe. Disable anything that's clearly not yours. Then, in the right-hand pane, click Refresh — sometimes stale tasks vanish on refresh.

Next, open Registry Editor (Win+R, type regedit, press Enter). Navigate to:

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

If this key exists, it means Windows thinks a reboot is required for an update. Do not delete it unless you're sure the update is complete and the system is stable. Instead, check which update is pending by looking at the RebootRequired key's subkeys. You can safely delete it only if you've already installed the update and rebooted.

Still stuck? Open an elevated PowerShell and run:

Stop-Service -Name wuauserv -Force
Get-ScheduledTask -TaskPath "\Microsoft\Windows\UpdateOrchestrator\" | Where-Object {$_.TaskName -match "Reboot"} | Disable-ScheduledTask

This disables the update-related reboot scheduler. Restart the computer manually. After the restart, re-enable the service and tasks:

Start-Service -Name wuauserv
Get-ScheduledTask -TaskPath "\Microsoft\Windows\UpdateOrchestrator\" | Where-Object {$_.TaskName -match "Reboot"} | Enable-ScheduledTask

The reason step 3 works is that Windows Update's reboot scheduling hooks into the same shutdown queue, and by temporarily disabling the scheduler, you force the OS to discard any stale pending state. On reboot, it creates a fresh one.

If none of this clears the error, you likely have a corrupt system file. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth — but that's a whole other article.