Why Windows 11 Shuts Down So Slowly and How to Fix It

What Windows actually does when you press Shut down

When you click Shut down, Windows broadcasts a close request to every open app, waits for each to confirm, then flushes the disk caches, stops the services and writes the final power state. The built-in patience is a few seconds per app and five seconds per service — the WaitToKillServiceTimeout — so one misbehaving program that ignores the request adds its own timeout to every single shutdown. Updates add another layer: with a staged patch, Windows finishes installing it during shutdown, and the screen tells you so honestly (Installing updates, don't turn off your PC).

Fast Startup, enabled by default on many OEM installs, complicates the picture: it closes your session but hibernates the kernel instead of a full shutdown, so this shutdown also writes a multi-gigabyte hiberfil.sys image. On machines with lots of RAM that phase alone can take a minute, and a corrupted image makes it hang — which is why holding Shift while clicking Shut down bypasses Fast Startup once and runs the full sequence.

• The blue screen before shutdown names the apps that are blocking — close them and the delay disappears
• Pending Windows updates install at power-off and legitimately add minutes
• One hung service waits out its WaitToKillServiceTimeout on every single shutdown
• Fast Startup writes a hiberfil.sys image at shutdown, which is slow on big-RAM machines
• Shift + Shut down forces a full shutdown and bypasses Fast Startup once
• Event Viewer > Windows Logs > System shows which app or service delayed the last power-off

Finding your specific blocker

Start with the obvious: if the blue Apps are preventing shutdown screen appears, note the apps listed — one of them is your delay — and make a habit of closing them before powering off. Open Event Viewer (Win+R, eventvwr.msc), go to Windows Logs > System and look at the events around the last shutdown time: Service Control Manager warnings (IDs 7031 and 7043) point to services that did not shut down cleanly, and in the application log, Application Hang events (ID 1002) name the programs that froze.

Two registry settings decide much of the wait. ClearPageFileAtShutdown, off by default, wipes the pagefile at power-off — if someone enabled it for security, every shutdown takes roughly as long as your RAM is big; the value lives under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. AutoEndTasks in HKCU\Control Panel\Desktop (set to 1) tells Windows to force-close apps instead of asking you — handy on an unattended machine, but unsaved work is lost, so think twice. And if the power button carries the update icon, use Update and shut down once and let it finish, instead of interrupting it every evening.

The habits and settings that end slow shutdowns

Close your apps before shutting down — trivial, but it removes the biggest variable. Reboot weekly instead of only shutting down: with Fast Startup on, a shut-down PC never truly restarts its drivers, and accumulated driver state is a classic cause of drawn-out shutdown-and-boot dramas. If shutdown still crawls, disable Fast Startup in Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable, and uncheck Turn on fast startup — on a desktop the boot-time cost is minor and shutdown becomes a clean, predictable sequence. Keep the GPU and chipset drivers updated too, because hangs while unloading drivers are a well-known source of extra shutdown minutes.

Questions and Answers

Read next

All articles · FAQ