Fix 0x0000045C: No Shutdown in Progress Error Fast

30-Second Fix: Check if the Shutdown Already Completed

This error almost always means you're too late. The shutdown you tried to abort already finished — or it never actually started. Here's what to do:

1. Press Ctrl + Alt + Del and select Task Manager.
2. Look under Processes for anything named shutdown.exe or Shutdown. If you see it, right-click and End Task.
3. If nothing's there — the shutdown already ran. Just log back in and move on. The error is harmless.

That's it for most people. If you're still stuck, move to the next step.

Moderate Fix (5 Minutes): Kill the Stuck Shutdown from Command Line

Sometimes Windows leaves a shutdown timer running in the background even after the system's back up. The culprit here is almost always a scheduled task or a leftover shutdown /a call that's out of sync.

1. Open Command Prompt as Administrator. (Press Win + R, type cmd, then Ctrl + Shift + Enter.)
2. Run this command to force-kill any pending shutdown:

shutdown /a

3. If you get the same error 0x0000045C again, the shutdown timer is dead. Run this to reset the system's shutdown state:

shutdown /s /t 5
shutdown /a

That schedules a new shutdown with a 5-second timer, then immediately aborts it. It resets the internal flag.

4. If that still fails, check if a scheduled task is causing the loop. Open Task Scheduler (type taskschd.msc in Run), look under Task Scheduler Library → Microsoft → Windows → Shutdown. Disable any task there that's set to trigger on a schedule.

Advanced Fix (15+ Minutes): Corrupted User Profile or Group Policy

If you're still seeing this error repeatedly across reboots, you've got a deeper issue. I've seen this mostly on domain-joined machines where a Group Policy pushes a shutdown script that doesn't clean up properly. Here's the fix:

Check Group Policy

1. Run gpedit.msc (Pro/Enterprise only — skip on Home edition).
2. Go to Computer Configuration → Windows Settings → Scripts (Startup/Shutdown).
3. Double-click Shutdown. If there's any script listed, remove it. Then click Apply.
4. Run gpupdate /force in an admin command prompt.
5. Reboot.

Repair Corrupted User Profile

Less common but I've seen it. The user profile's shutdown state data gets corrupted. Test by creating a new local admin account:

1. Open Settings → Accounts → Family & other users.
2. Click Add someone else to this PC.
3. Create a local account (don't use Microsoft account). Make it admin.
4. Log into that new account. Try triggering and aborting a shutdown. If it works fine, your old profile is toast.
5. Migrate your files from the old profile to the new one. Then delete the old account through Settings.

System File Checker (Last Resort)

Don't bother with SFC unless you have other symptoms. But if you're here:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Reboot after both run. This fixes underlying corruption that might cause the shutdown state to hang.

I've fixed this error on Windows 10, 11, and Server 2016 through 2022. The 30-second fix works for 9 out of 10 cases. The group policy trick gets the rest. Don't overthink it.