STATUS_SERVER_SHUTDOWN_IN_PROGRESS (0XC00002FF) – Server shutting down

Quick answer

If you see 0XC00002FF, the server is shutting down. Wait 5–10 minutes. If it doesn't come back, force a reboot via iDRAC, iLO, or the power button.

What this error really means

STATUS_SERVER_SHUTDOWN_IN_PROGRESS (0XC00002FF) isn't a bug – it's the server telling you it's going down. You might see this when you try to open an SMB share, connect via RDP, or run a remote management tool and Windows slaps you with "The server machine is shutting down."

This happens in a few common scenarios:

• Scheduled reboot: You kicked off a restart from Windows Update or a manual reboot and jumped the gun trying to connect again.
• Pending updates: The server already downloaded updates and is sitting at a "Restart required" state. The next time it reboots, it installs them, and during that process any remote connection gets this error.
• Crash or blue screen: The server crashed, dumped memory, and is rebooting. Clients trying to connect during the reboot see this error.
• Stuck shutdown: A service or process refuses to stop, holding up the shutdown for minutes. You try to connect and get the error.

The real fix is figuring out why the server is shutting down, not fixing the error itself. The error is just a symptom.

Step-by-step fix

1. Wait 5–10 minutes. This is the first thing I tell every tech. If the server is rebooting, it'll come back. Watch the network activity or ping the server. Once you get a reply, try connecting again.
2. Check physical or remote console. If you have iDRAC, iLO, or a KVM, open the console. You'll either see the Windows login screen (updates finished), a "Configuring updates" screen, or a blue screen with a crash dump.
3. Force a reboot if stuck. If the server is stuck on "Shutting down" or "Restarting" for more than 15 minutes, force a power cycle. Use iDRAC/iLO to send a cold reset, or press the power button on the chassis for 10 seconds. After it reboots, check the Event Viewer for shutdown origin (Event ID 1074).
4. Check for pending updates. If the server is stuck on "Configuring updates – xx%", wait. Updates can take 30–60 minutes on older servers. If it's stuck at 0% for over an hour, you may need to force reboot and run dism /online /cleanup-image /restorehealth from Safe Mode.

Alternative fixes if the main one fails

Option A: Remote shutdown from another machine

If you can't even get to the console but the server is responsive on the network (even partially), run this from another machine on the same domain:

shutdown /r /m \\SERVERNAME /t 0 /f

Replace SERVERNAME with the actual name or IP. The /f flag forces running apps to close. This often kicks a stuck shutdown out of its coma.

Option B: Check for a hung shutdown script

If the server reboots normally but you still see the error on clients intermittently, it could be a Group Policy shutdown script hanging. Run gpedit.msc and go to Computer Configuration → Windows Settings → Scripts (Startup/Shutdown). Check for any scripts that might be timing out. Remove them temporarily to test.

Option C: Boot into Safe Mode

If the server won't fully boot and you keep seeing the error during startup, force it into Safe Mode. Do this by interrupting the boot sequence three times (press the power button during Windows logo) to trigger Automatic Repair, then go to Troubleshoot → Advanced Options → Startup Settings → Restart → Safe Mode. Once in Safe Mode, check the System log for critical errors.

Prevention tip

Don't schedule reboots during business hours. Set a maintenance window using Windows Updates or shutdown /r /t 3600 to delay the reboot by an hour. Also, create a simple PowerShell script that checks if the server is stuck in a shutdown state (using Get-WinEvent for Event ID 1074) and sends you an alert. I've seen too many servers sit dead for hours because nobody noticed the shutdown got stuck.