Fix ERROR_SHUTDOWN_IN_PROGRESS 0X0000045B on Windows

Quick answer

Unplug your PC's power cord (or hold the power button 10 seconds) to force a hard restart — that clears the shutdown-in-progress flag 90% of the time.

What's going on?

This error, error code 0X0000045B (which Windows also spells as ERROR_SHUTDOWN_IN_PROGRESS), pops up when you try to launch an application while Windows is already shutting down. Maybe you clicked Shut Down, then changed your mind and tried to open Chrome. Or a pending Windows Update triggered a silent shutdown. Either way, Windows has set its internal "shutdown in progress" flag, and it blocks any new processes from starting.

The real-world trigger? I see this most often on Windows 10 and 11 machines after a failed update restart — the system tries to reboot, something hangs, and the flag stays set for minutes. Users freak out thinking their app is broken. It's not. The system is just in a weird state.

Here's how to get past it.

Fix steps

Wait 60 seconds. If Windows is legitimately shutting down (you see the "We're getting things ready" screen), let it finish. Don't fight it. Walk away, grab coffee, come back.
Hard restart (the nuclear option). Press and hold your PC's power button for 10 full seconds until the machine powers off. Wait 5 seconds, then press power again. This kills the shutdown flag entirely because the OS is forced to reinitialize. Works on every version from Windows 7 through 11.
Task Manager kill (if you can't hard restart). Press Ctrl+Shift+Esc, go to the Processes tab, look for Windows Explorer, right-click it, and choose Restart. That sometimes resets the desktop shell and clears the shutdown flag without a full reboot. Not guaranteed, but it's worth a shot if you're in the middle of something.
Command-line fix. Open Command Prompt as Administrator (search cmd, right-click, Run as Administrator), then type:
```
shutdown /a
```
This aborts the current shutdown if Windows hasn't progressed too far. It's a built-in safety net. I've used it dozens of times when updates trigger an unwanted restart during a work session.

Alternative fixes if the main one fails

If you're still getting 0X0000045B after a hard restart, something deeper is wrong. Here's what else to try:

Safe Mode boot

Restart your PC, and as it boots, spam the F8 key (or hold Shift while clicking Restart in Windows 10/11) to enter Safe Mode. Once there, open Command Prompt as Admin and run sfc /scannow. Corrupted system files can sometimes lock the shutdown flag.

Check for stuck Windows Update

Open Services (services.msc), find Windows Update, and check if it's stuck in a Starting or Stopping state. If it is, right-click and choose Stop. Then delete the contents of C:\Windows\SoftwareDistribution and restart. This clears pending update downloads that can cause a perpetual shutdown loop.

Registry tweak (advanced users only)

If nothing else works, open Regedit and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

If this key exists and has entries, delete them all. This forces Windows to skip pending file operations that might be blocking shutdown. Back up the key first — I've seen this backfire if you remove something critical.

Prevention tip

Stop interrupting shutdowns. I know it's tempting to close the lid or cancel a restart when you remember you forgot to save something, but every time you force-interrupt a shutdown, you risk leaving the flag set. Next time you see the shutdown screen, let it ride. If you absolutely need to cancel, use shutdown /a from an admin command prompt — it's the only safe way.

Also, check your power settings: go to Control Panel > Power Options > Choose what the power buttons do, and set the power button to Do nothing or Shut down (never Sleep or Hibernate during updates — those can trigger the same flag).

That's it. You're not stuck forever. Just force the restart, and you're back in business.