How to fix Error 1116 on Windows 11

by

Windows 11 Error 1116: “Unable to Abort the System Shutdown Because No Shutdown Was in Progress”

Why This Error Happens

Error 1116 occurs when a script, command, or application attempts to cancel a system shutdown (typically via shutdown /a) but the operating system has no active shutdown, restart, or logoff sequence registered in its state machine. This is usually a timing/race condition—the shutdown either already completed, was never successfully initiated, or was canceled by another process before your abort command executed. It can also occur if scheduled tasks, batch scripts, or third-party power-management tools issue an abort command redundantly, or after a Group Policy/registry misconfiguration causes shutdown events to fire inconsistently.

Step-by-Step Resolution Guide

  1. Verify Shutdown State Before Aborting
    Open Command Prompt as Administrator and check for pending shutdowns manually before running an abort command:
   shutdown /a

If Error 1116 appears immediately, this confirms no shutdown is currently queued—so no action is needed.

  1. Inspect Scheduled Tasks and Scripts
    Open Task Scheduler (taskschd.msc) and review any tasks that trigger shutdown /s or shutdown /a. Check for duplicate or overlapping triggers under Task Scheduler Library, especially tasks tied to power events, logon, or maintenance windows. Disable or consolidate redundant triggers.

  2. Check Event Viewer for Timing Conflicts
    Open Event Viewer (eventvwr.msc) → Windows Logs → System. Filter by Event ID 1074 (shutdown initiated) and 1116 (abort failure) to correlate timestamps. This reveals whether another process or user already canceled the shutdown first.

  3. Update Shutdown-Related Group Policies
    Go to Local Group Policy Editor (gpedit.msc) → Computer Configuration > Administrative Templates > System > Shutdown. Ensure no conflicting policies (e.g., “Turn off Automatic Restart” or scripted shutdown countdown values) are causing shutdown events to fire and clear faster than scripts can react.

  4. Update or Reinstall Affected Third-Party Software
    If a specific application (backup tool, remote management agent, etc.) triggers the abort command, check for updates via Settings > Windows Update > Advanced Options or the vendor’s site. Outdated shutdown-hook APIs are a common cause of this race condition.

Alternative or Verification Steps

  • Verify the fix: Run shutdown /r /t 60 to schedule a delayed restart, then immediately run shutdown /a. If the abort succeeds without Error 1116, the shutdown state is being tracked correctly.
  • Alternative workaround: Wrap your abort command in a conditional script that checks the shutdown state via query system or PowerShell’s Get-CimInstance Win32_OperatingSystem before calling shutdown /a, preventing redundant abort attempts.