This is the scenario: the update installed, Windows asked for a restart, and now your laptop has displayed “Restarting” with spinning dots for an unreasonable amount of time. It’s the worst kind of stuck because you can’t see progress, you can’t cancel, and every instinct says to hold the power button — which might be exactly the wrong move if the update is actually mid-write. The difference between a slow restart and a hung one is the most important diagnosis in this guide, because everything else follows from it.
Post-update restarts are Windows’ heavy-lifting phase: replacing in-use system files, migrating drivers, updating boot data. Windows 11’s cumulative updates have grown larger, and this phase has grown longer with them — 20 to 40 minutes is normal on modern hardware. But “normal” has a limit, and beyond it lies the hang: a driver refusing to unload, Fast Startup colliding with the restart, or a peripheral holding the shutdown sequence hostage. Here’s how to tell which you’re facing and what to do about each.
Why this happens
- A driver won’t unload: Storage, display, or network drivers hanging the shutdown sequence — the top cause of repeat hangs.
- Fast Startup collision: The hybrid shutdown state conflicts with the update’s restart, freezing the handoff.
- USB peripherals stall shutdown: Docks, external drives, and printers holding the sequence waiting for responses.
- Disk errors: Bad sectors in the paths being written turn a normal restart into an hours-long crawl.
- Stacked updates: Multiple updates queuing file operations into one marathon restart.
- Antivirus file hooks: Security software inspecting every file swap during the update.
- Corrupt hibernation file: A damaged hiberfil.sys breaking the hybrid shutdown path.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Verify stuck vs. slow before touching anything
Ninety percent of the damage in this scenario is self-inflicted — force-restarting a working update. Diagnose first.
- Start a timer from when the Restarting screen appeared. Allow 90 minutes (SSD) or 2 hours (HDD).
- Listen for drive activity and watch for fan speed changes — both mean work is happening.
- Observe the spinner: smooth animation = responsive system; frozen for 30+ minutes = likely hung.
- If your laptop has a drive activity LED, blinking = progress.
- Keep AC power connected throughout — never let the battery die here.
- Only continue to Fix 2 after an hour of zero activity.
Fix 2: Force the restart safely
For a confirmed hang, a forced shutdown is correct. Windows checkpoints update progress and resumes.
- Hold power for 10 seconds until the laptop shuts off.
- Disconnect all USB devices, docks, external drives, and printers.
- Wait 30 seconds, then power on with only AC connected.
- You’ll typically see “Working on updates” complete within 10–30 minutes.
- If it reaches the desktop, go to Settings > Windows Update > Update history to verify the update installed.
- If it hangs again at the same point, continue to Fix 3.
Fix 3: Disable Fast Startup permanently
Fast Startup is implicated in a large share of restart hangs. Disabling it costs a few seconds of boot time and buys reliable restarts.
- Open Control Panel > Hardware and Sound > Power Options.
- Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup (recommended) and save.
- Test with a manual Restart — it should complete cleanly.
- As a bonus, also run
powercfg /hibernate offthenpowercfg /hibernate onin elevated Command Prompt to rebuild a potentially corrupt hibernation file.
Fix 4: Update the drivers that hang shutdowns
The repeat-hang pattern almost always traces to one driver. Update the usual suspects proactively.
- Open Device Manager and update drivers under Storage controllers, Display adapters, and Network adapters (right-click > Update driver).
- Get chipset and storage drivers from your maker: Dell , HP , Lenovo .
- Update graphics from NVIDIA, AMD, or Intel’s official driver pages rather than relying on Windows Update’s versions.
- Our driver update guide covers the systematic approach.
- After updating, the next Patch Tuesday restart should complete normally — if it doesn’t, one specific driver is the culprit (see Fix 6).
Fix 5: Repair servicing damage from the interrupted update
A hang-interrupted update can leave the component store inconsistent, poisoning future updates.
- Open Command Prompt as administrator.
- Run
DISM /Online /Cleanup-Image /RestoreHealth. - Run
sfc /scannowafter DISM completes. - Run
chkdsk C: /fto catch filesystem damage from the hard shutdown. - Restart cleanly and verify Settings > Windows Update shows a healthy state.
- This post-hang cleanup is what separates “recovered” from “recovered and stable.”
Fix 6: Find the hanging driver with a clean boot
If hangs recur after driver updates, isolate the offender methodically instead of guessing.
- Run
msconfig, check Hide all Microsoft services, and Disable all. - Disable all startup items in Task Manager.
- Restart — if the restart is now fast, a third-party driver or service was hanging it.
- Re-enable in halves to narrow it down: services first, then startup items.
- Frequent culprits: VPN clients, third-party disk tools, RGB/peripheral software, old printer drivers.
- Update or uninstall the identified culprit. If it’s a driver Windows Update keeps reinstalling, see our driver failure guide for hiding it.
Fix 7: Change your update-restart habits
Prevention is a procedure, not just a setting.
- Before major updates, disconnect docks and USB peripherals — reconnect after.
- Use Restart (not Shut down) when Windows requests it post-update.
- Don’t stack a month of deferred updates into one session if you can avoid it — smaller, frequent rounds restart faster.
- Keep 20 GB free on C: so staging never becomes the bottleneck.
- If a specific update hangs repeatedly, uninstall it in Safe Mode and pause updates until Microsoft revises the package — the same approach in our 24H2 Restarting screen guide .
Closing
The “Restarting” hang is a patience test with a technical core: verify it’s truly stuck before forcing anything, then eliminate the repeat causes — Fast Startup, stale drivers, and connected peripherals. One clean recovery plus the preventive steps above turns a monthly ordeal into a non-event. Your updates will still take their 20–40 minutes; they just won’t take your evening.
