Windows 11 Taking Forever to Shut Down or Restart? How to Fix It

You click Shut Down or Restart and then just… wait. The screen sits on “Shutting down” or “Restarting” for a minute, two minutes, sometimes long enough that you start wondering whether to just hold the power button and force it.

This is a different problem from a slow-to-boot PC, even though it feels related. Startup is mostly about hardware and drivers waking up in sequence; shutdown is about Windows asking every running app, service, and driver to close cleanly and then waiting for each one to actually confirm it’s done — and it only takes one thing not answering back to stretch a two-second shutdown into a two-minute one.

Quick explanation: this guide covers spotting the specific app or service holding up shutdown, the Windows shutdown timeout settings that control how long it waits before giving up, why Fast Startup can make restarts behave strangely even though it’s meant to speed things up, a driver failing to release the GPU or network adapter cleanly, and pending updates that install during shutdown and add several extra minutes on their own.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

Slow shutdown or restart is almost always one specific app, service, or driver refusing to close on cue, not the whole system failing at once. Open Task Manager right before you shut down and glance at what’s still running under high CPU or disk activity — that’s usually the culprit. If nothing obvious stands out, the next most common cause is Windows waiting to finish installing an update (look for “Working on updates, don’t turn off your PC” on the screen), followed by Fast Startup interacting oddly with a restart, and only then hardware or driver issues.

Why Slow Shutdown Isn’t the Same Problem as Slow Startup

When Windows starts up, it’s initializing hardware, loading drivers, and starting services roughly in sequence — a slow boot usually points to too much happening at once early on. Shutdown works in the opposite direction: Windows sends a close signal to every open app and running service and then waits for each one to acknowledge it before it can safely power down.
That waiting is exactly where things go wrong. A browser with dozens of tabs, a sync client mid-transfer, or a background service that’s hung rather than crashed can all sit there not responding to the close request, and Windows will wait a set amount of time before forcing them closed. The most reliable way to catch this in the act is to open Task Manager just before you shut down and watch which process is still pinned at high CPU or disk usage in the seconds after you click Shut Down.
Fixyfier’s Administrative Tools section puts Task Manager and Resource Monitor both a click away, which makes catching the specific process holding things up far faster than digging through Start menu search first.

The Shutdown Timeout Settings Windows Doesn’t Advertise

Windows doesn’t wait forever for a stuck app to close — it has built-in timeout values that control how long it gives an unresponsive app or service before forcibly ending it. On a healthy PC these rarely matter, but if they’ve been changed (by another utility, a group policy, or a past registry edit) to unusually long values, a single hung app can stretch shutdown out far longer than it should.
These live in the registry under HKEY_CURRENT_USER\Control Panel\Desktop as WaitToKillAppTimeout and under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control as WaitToKillServiceTimeout, both measured in milliseconds. You can check the current app timeout value from an elevated PowerShell window with the command below.
Get-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name WaitToKillAppTimeout
It’s worth being cautious here rather than slashing these values aggressively — set them too low and Windows will start force-closing apps before they’ve had a real chance to save unsaved work, which trades a slow shutdown for a data-loss risk. A modest reduction from an unusually high value is reasonable; going far below the Windows default isn’t.

Fast Startup Can Make Restarts Behave Strangely

Fast Startup is designed to make the next boot quicker by hibernating the Windows kernel session instead of fully shutting it down — but it only applies to a full shutdown, not a restart, which is where the confusion usually starts. If a restart feels sluggish specifically (while a full shutdown feels normal, or vice versa), Fast Startup interacting with the hybrid shutdown/hibernation state is a genuine, if confusing, real cause.
It’s controlled from Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable, where Turn on fast startup can be toggled off entirely as a test. If restarts clean up noticeably after that, Fast Startup’s hybrid state was the source of the inconsistency rather than a genuinely broken shutdown.
Fixyfier’s Security & Privacy section includes a Restore Default Power Plans option, useful if power settings have drifted from a custom tool or a past tweak and you’d rather reset the whole power configuration back to a known-good state than hunt down each setting individually.

A Driver Failing to Release Hardware Cleanly

Some shutdown delays trace back to a driver rather than a running app — a GPU driver mid-task, a network adapter still holding an active connection, or a USB or storage controller driver that doesn’t respond promptly to the power-down signal. These delays tend to be consistent and reproducible rather than random, which is a useful clue: if shutdown is slow every single time by roughly the same amount, a driver is a more likely explanation than a one-off stuck app.
Updating the driver for whichever piece of hardware you suspect — usually the graphics card or the network adapter first, since those cause this most often — through the manufacturer’s site or Windows Update resolves most cases. A recently updated driver that introduced the problem is also worth rolling back as a test.
Fixyfier’s Administrative Tools section includes a Device Manager shortcut, which gets you straight to updating, rolling back, or disabling a specific device’s driver without navigating through Windows Settings first.
NordVPN
One Thing Worth Knowing

The Same Background Chatter That Delays Shutdown Is Worth Encrypting

A slow shutdown is often a sign of just how much runs quietly in the background on a typical PC — apps and services syncing, checking in, or phoning home long after you thought they were idle, sometimes right up until the moment you try to shut down. NordVPN encrypts that always-on background traffic, so whatever's chatting away in the background isn't doing it in the clear.

Secure Your Connection

Pending Updates Installing During Shutdown

“Working on updates, don’t turn off your PC” is the single biggest cause of a shutdown or restart that suddenly takes far longer than usual, and it’s easy to miss if the screen doesn’t show that message right away — Windows silently begins installing downloaded updates as part of the shutdown process itself, and a larger cumulative update can add several extra minutes on its own.
There isn’t a safe way to skip this once it’s started without risking an incomplete installation, so the better move is checking for and installing pending updates ahead of time, on your own schedule, rather than letting them queue up and surface unexpectedly the next time you shut down.
This is worth checking whenever the slow shutdown started right after an update notification appeared — if it’s a Windows Update itself failing to install cleanly rather than just taking a while, that’s covered in more depth in a dedicated guide on Windows Update stuck downloading or installing.

A Scheduled Task Waking Up Right at Shutdown

Less commonly, a scheduled task — a backup job, a maintenance script, or something an app installed to run on a timer — happens to fire right around when you shut down, and Windows waits for it the same way it waits for any other running process. This tends to show up as an intermittent slow shutdown rather than one that’s slow every single time, since it only bites when the timing lines up.
Reviewing what’s actually scheduled to run, and at what times, is the only reliable way to rule this in or out — a task set to run daily around your typical shutdown time is worth rescheduling to a moment when the PC is more likely to be idle instead.
Fixyfier’s Administrative Tools section puts Task Scheduler a click away, so checking for tasks with a suspiciously convenient trigger time doesn’t require hunting through Windows’ own admin tools menu first.

Frequently Asked Questions

Is it safe to force shut down my PC if it’s stuck on the shutdown screen?

It’s not ideal, but it’s usually safe as a last resort if the screen has been stuck for several minutes with no disk activity — holding the power button for a few seconds forces a hard shutdown. The bigger risk is doing this while Windows is actively installing an update, since interrupting that can occasionally cause update-related problems on the next boot, so it’s worth waiting a bit longer if you see an update message on screen first.

Why does my PC shut down fine but restart slowly, or the other way around?

This points fairly specifically at Fast Startup, which only applies to a full shutdown and not to a restart. A meaningful difference between how long shutdown takes versus how long restart takes is one of the clearer signals that Fast Startup’s hibernation behavior, rather than a stuck app or driver, is the actual cause.

Does a slow shutdown mean my PC has malware?

It’s possible but far from the most likely explanation — a stuck app, a pending update, or Fast Startup account for the overwhelming majority of slow shutdowns. Malware is worth ruling out if the slowdown appeared alongside other symptoms like unexpected network activity or unfamiliar processes in Task Manager, but it shouldn’t be your first assumption on its own.

Let Fixyfier Help You Catch What’s Slowing Shutdown Down

Fixyfier puts Task Manager, Resource Monitor, Task Scheduler, and Device Manager all a click away under Administrative Tools, so spotting the specific app, task, or driver holding up shutdown takes seconds instead of digging through several different Windows menus one at a time.