STATUS_SHUTDOWN_IN_PROGRESS 0XC00002FE Fixed

Hung Services Blocking Shutdown

I've seen this error more times than I can count. The culprit here is almost always a service that's stuck in a stop-pending state. Your machine boots fine, but when you try to launch an app — boom, you get 0XC00002FE. Windows thinks it's mid-shutdown because a service never properly quit.

This happens a lot after a forced power-off or a Windows Update that didn't finish cleanly. I've fixed it on Windows 10 22H2 and Windows 11 23H2 the same way.

Step 1: Kill Hung Services

Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or Terminal Admin). Run this:

tasklist /svc | findstr /i "shutdown"

If nothing returns, check for services stuck in "Stop Pending" state. Run:

sc query | findstr /i "STOP_PENDING"

That'll show you the service name. Then force-kill it with:

sc query [service_name]
sc stop [service_name]

If sc stop hangs, use taskkill on the PID associated with that service. Find the PID from sc queryex, then:

taskkill /PID [PID] /F

I've had TrustedInstaller and wuauserv (Windows Update) cause this. Kill them, restart the app.

Step 2: Clear Pending Shutdown State

Sometimes Windows hardcodes a shutdown flag in memory. Run this to clear it:

shutdown /a

That aborts any pending shutdown. If it says "No shutdown in progress", move to the next cause.

Driver Causing Power State Confusion

Another common cause I've seen — a driver that's not handling sleep or hibernate transitions correctly. This shows up on laptops especially, after closing the lid or putting the machine to sleep. You wake it up, try to open Chrome, and get 0XC00002FE.

The driver is telling Windows the system is still going to sleep even though it's awake. Dumb, but fixable.

Step 1: Check the System Event Log

Open Event Viewer (eventvwr.msc). Go to Windows Logs > System. Filter by Event ID 6008 (unexpected shutdown) or 41 (Kernel-Power). Look for any driver-related warnings right before the error timestamp.

In my experience, it's often a network driver (Realtek or Intel) or a graphics driver (NVIDIA or AMD). Update them directly from the manufacturer's site — never rely on Windows Update for drivers.

Step 2: Disable Fast Startup

Fast Startup is a hybrid shutdown/sleep mode that half the time causes this exact error. Turn it off:

1. Open Control Panel > Power Options
2. Click Choose what the power buttons do
3. Click Change settings that are currently unavailable
4. Uncheck Turn on fast startup (recommended)
5. Hit Save

Reboot. I'd say this fixes about 30% of cases alone.

Registry Session Manager Leftovers

This one's rarer but when it hits, it's a nightmare. The Session Manager registry key can store pending operations that confuse Windows at boot. Happens after a failed Windows Update or a disk-check error.

Step 1: Check PendingFileRenameOperations

Open Regedit (regedit.exe). Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Look for a value named PendingFileRenameOperations. If it exists and has data, that's your culprit. Windows tries to rename/move files on next boot, but gets stuck.

You can safely delete that value. Or better, back it up first (right-click > Export). Then delete it.

Step 2: Clear Pending Boot Operations

Same key — look for PendingBootOperations or BootExecute. The default for BootExecute is autocheck autochk *. Anything else? Likely leftover from a failed update. Delete the extra entries.

I once saw BootExecute with a path to a dead driver DLL. Removed it, error gone.

Reboot after registry changes. If the error persists, check the PendingFidoList or PendingFileRenameOperations2 values — same deal.

Quick-Reference Summary

One last thing — don't bother with sfc /scannow or DISM unless you suspect corruption from a bad shutdown. They rarely fix 0XC00002FE specifically. Save your time.