Few things are as maddening as watching your laptop spin on the blue “Restarting” screen long after it should have finished. You told it to restart ten minutes ago, and it’s still showing that little dotted circle, going nowhere. This usually happens after a Windows update, a driver install, or a program that refused to close cleanly.
The hang is almost always caused by something that won’t let go: a stuck Windows Update component, a service that won’t stop, a misbehaving driver, or an external device Windows keeps waiting on. Here’s how to break out of it and stop it from coming back.
Why this happens
- A Windows update got stuck mid-restart. The update service downloaded files but can’t finish applying them, so the restart sequence waits indefinitely for a step that will never complete.
- A background service or app won’t terminate. Some third-party services (antivirus, backup tools, updaters) ignore Windows’ shutdown requests, and the restart timer never expires.
- A driver is hanging the shutdown sequence. Display, storage, or network drivers that fail to respond to the power-off command keep the whole restart pipeline stuck.
- Fast Startup is conflicting with a fresh restart. The hybrid shutdown state can hold onto broken session data that a normal restart was supposed to clear.
- An external device is stalling the process. USB drives, docking stations, and SD cards can make Windows wait on hardware responses during the hardware re-enumeration that happens at boot.
- Corrupted system files or a damaged update cache. If key files in the update store are corrupt, every restart attempt trips over the same broken step.
How to fix it
Work through these in order, from the quickest and safest fixes to the deeper ones. Stop as soon as restarts work normally again.
Fix 1: Force a clean shutdown and disconnect everything
Before doing anything fancy, rule out the simple causes.
- Hold the power button for 10 seconds until the laptop powers off completely.
- Unplug every USB device: drives, docks, hubs, receivers, SD cards. Leave only the charger connected.
- Wait 30 seconds, then power on and sign in.
- Try restarting from Start > Power > Restart and watch whether it completes this time. If it does, one of those devices was the culprit — plug them back one at a time to find it.
Fix 2: End the hanging processes before you restart
If restarts hang but shutdowns work, a stubborn program is likely the cause.
- Press Ctrl + Shift + Esc to open Task Manager.
- Look under Processes for anything marked Not responding, especially third-party updaters, backup tools, or antivirus components.
- Select each one and click End task.
- Go to the Startup apps tab and disable anything non-essential — you can re-enable them later.
- Try the restart again. A clean boot, described in our guide to performing a clean boot on Windows 11 , is the deeper version of this step if the problem persists.
Fix 3: Turn off Fast Startup
Fast Startup is a known cause of restart hangs because it turns restarts into glorified log-offs.
- Open Control Panel > Hardware and Sound > Power Options.
- Click Choose what the power buttons do, then Change settings that are currently unavailable.
- Uncheck Turn on fast startup (recommended) and click Save changes.
- Shut down fully, wait 10 seconds, power on, and test a restart.
Fix 4: Clear the stuck Windows Update cache
This is the fix for hangs that started right after a Windows update.
- Press Win + S, type
cmd, right-click Command Prompt, and choose Run as administrator. - Stop the update services:
net stop wuauservnet stop bitsnet stop cryptSvc - Rename the update folders so Windows rebuilds them fresh:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.old - Restart the services:
net start wuauservnet start bitsnet start cryptSvc - Go to Settings > Windows Update and click Check for updates — let any pending updates install cleanly, then restart. If an update is corrupted, the Microsoft Update Catalog lets you download and install it manually as a standalone package.
Fix 5: Run the system file and image repair tools
Corrupted system files can break the restart pipeline itself.
- Open an elevated Command Prompt (as administrator).
- Run
sfc /scannowand wait for it to complete — about 10–15 minutes. - Then run
DISM /Online /Cleanup-Image /RestoreHealth. This needs internet access. - Restart and test. If you can’t reach the desktop at all, both tools also run from the Command Prompt option inside the recovery environment (see Fix 6).
Fix 6: Use Startup Repair from the recovery environment
If the laptop won’t boot properly after the forced shutdown, let Windows repair itself.
- Force the laptop off, then power on. Interrupt the boot by holding the power button at the logo screen. Do this three times to trigger the Windows Recovery Environment.
- Go to Troubleshoot > Advanced options > Startup Repair.
- Let it run — it diagnoses boot problems and fixes common ones automatically. Our walkthrough of using Startup Repair on Windows 11 covers what to do if it says it couldn’t repair your PC.
Fix 7: Check for a failing drive
Repeated restart hangs paired with slowness can signal a dying storage drive.
- Open an elevated Command Prompt.
- Run
chkdsk C: /f /r— type Y when asked to schedule it, then restart. The scan runs before Windows loads and can take a while on large drives. - After booting, check drive health: in PowerShell (Admin), run
Get-PhysicalDisk | Select FriendlyName, HealthStatus, OperationalStatus. - If the health status shows anything other than Healthy, back up your files immediately and plan a drive replacement — no software fix will save a failing drive. Microsoft’s Windows support hub documents the recovery options if Windows itself won’t start at this point.
Closing
A laptop stuck on the restarting screen feels broken, but the cause is usually mundane: a stuck update, a stubborn service, or an external device Windows keeps waiting on. Force a clean shutdown, disconnect your peripherals, and clear the update cache, and most hangs disappear. If the problem keeps returning after every update, keep the update services and drivers healthy — that’s what prevents the next hang before it starts.
