Fix ERROR_SERVER_SHUTDOWN_IN_PROGRESS (0X000004E7)

Quick answer for pros

Reboot the server. If you can't connect, use IPMI or a physical console to force restart. Check Windows Update logs for pending restarts.

Why this error happens

You're trying to connect to a server that's in the middle of shutting down. Maybe you just kicked off a Windows Update install and forgot. Or someone else on your team triggered a restart. The server rejects any new connections while it's shutting down. This is normal behavior — the server isn't broken, it's just busy saying goodbye.

I see this a lot with Windows Server 2016 and 2019 after automatic updates install during off-hours. But it can also happen if the power supply flickers and the server starts a graceful shutdown.

Step-by-step fix

1. Wait 5 minutes. Seriously. Most shutdowns complete within 2 minutes. If you're patient, the server will come back up and you can connect again.
2. Check if the server is still shutting down. Try pinging the server from another machine. If you get no response, it's still shutting down or off.
3. Use physical console or IPMI. If you can't RDP, use a KVM over IP, iDRAC, iLO, or a local monitor and keyboard. Log in as admin. Look for a popup that says 'Windows is shutting down' or 'Restart pending'.
4. Cancel the shutdown. Open a command prompt as admin and type:

   shutdown /a

   This aborts the shutdown if it hasn't reached the final phase. You'll see a message 'Shutdown is aborted' in the system tray.
5. If that fails, force restart. Type:

   shutdown /r /t 0

   This restarts the server immediately. After reboot, check Event Viewer for what triggered the shutdown. Look under System logs for Event ID 1074.

Alternative fixes if the main one doesn't work

• Check Windows Update. Sometimes updates get stuck. Go to Settings > Update & Security > Windows Update and click 'Restart now' if it shows a pending restart.
• Run a repair. If the server keeps going into shutdown loop, boot from Windows installation media, choose 'Repair your computer', then 'Troubleshoot' > 'Advanced options' > 'Startup Repair'.
• Disable automatic updates temporarily. If this keeps happening during peak hours, set Active Hours so updates don't interrupt work. Or use Group Policy to delay updates.

Prevention tips

Set your Windows Update active hours on the server. For Windows Server 2019 and 2022, you can configure this in Settings or via Group Policy under 'Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify active hours range for updates'.

Also, create a scheduled task that checks for pending restarts every 30 minutes and emails your team. Here's a quick PowerShell script you can run as a task:

$PendingReboot = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update' -Name RebootRequired -ErrorAction SilentlyContinue
if ($PendingReboot) { Send-MailMessage -To 'admin@yourcompany.com' -From 'server@yourcompany.com' -Subject 'Server pending restart' -SmtpServer 'smtp.yourcompany.com' }

Finally, don't restart critical servers during work hours unless you've warned everyone first. A quick email or Slack message saves a lot of panic.

Pro tip: If you're on a terminal server and users keep getting this error, check if they're all connecting to the same session host that's stuck shutting down. Move them to another host in the farm.