The “Restarting” screen with its endless spinner is one of Windows 10’s most stressful sights. The update was installing, the laptop rebooted as expected, and then… nothing. Minutes become an hour, the dots keep circling, and you start wondering whether the machine will ever come back.
In most cases it will — either by finishing on its own or with a careful nudge. The critical skill is distinguishing a slow install from a frozen one, because the recovery steps differ completely. This guide starts with that assessment, then walks through the recovery ladder from a safe power cycle up to the deeper repairs. If your screen specifically shows the restarting screen variant with no progress , the same principles apply, with screen-specific notes there.
Why this happens
- Driver handoff stall: A driver fails to unload or reload across the restart boundary, freezing the boot sequence.
- Antivirus filter conflict: Security drivers intercept the restart’s file operations and deadlock.
- Failing storage drive: Bad sectors hit during the restart’s heavy disk writes stall the process.
- Corrupted update state: A half-applied update leaves the boot configuration in limbo.
- Peripheral interference: A connected USB device’s driver blocks the restart sequence.
- Low-level disk errors: File system corruption that the running OS tolerated becomes fatal during the offline phase.
- Insufficient power: On laptops, a dying battery causing a brownout mid-restart corrupts the in-flight update.
- BIOS handoff issues: Firmware that misbehaves during the warm reboot stalls before Windows even loads.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Wait and verify it is actually stuck
Most “stuck” restarts are just slow — especially on hard drives.
- Note the time and give it a full additional hour if you have not already waited two.
- Watch the disk activity light: flickering means the install is still working.
- Listen for fan and disk sounds indicating ongoing activity.
- If there is any sign of life, keep waiting — some Windows 10 updates take three hours on mechanical drives.
- Only proceed when there has been zero activity for over an hour.
Fix 2: Perform a controlled power cycle
Once the stall is confirmed, a careful shutdown is the standard recovery. Microsoft covers interrupted-update recovery on the Windows support hub .
- Hold the power button for ten seconds until the laptop powers off completely.
- Unplug the charger and remove the battery for thirty seconds if it is removable.
- Reconnect power and turn the laptop on.
- Windows will typically resume the update, roll it back, or boot to the desktop — give it up to an hour.
- If it boots normally, immediately check update history to see what happened.
Fix 3: Boot into Safe Mode and clear the state
If normal boot stalls again, Safe Mode bypasses the problematic drivers. Our Windows 11 safe-mode update guide describes the same technique on the newer OS.
- Force the laptop off twice during the Windows logo to trigger automatic repair.
- Go to Troubleshoot > Advanced options > Startup Settings and choose Safe Mode.
- Once in Safe Mode, open Command Prompt as administrator.
- Run
net stop wuauservandnet stop bits, then rename the SoftwareDistribution folder as described in Fix 4. - Restart normally — the update will re-download cleanly.
Fix 4: Clear the update cache from recovery
When you cannot reach the desktop at all, clear the cache from the recovery command prompt.
- Boot into the Windows Recovery Environment (installation media > Repair your computer if needed).
- Open Troubleshoot > Advanced options > Command Prompt.
- Find your Windows drive letter — in WinRE it is often D:, so verify with
dir D:\Windows. - Run
ren D:\Windows\SoftwareDistribution SoftwareDistribution.oldwith the correct letter. - Exit and choose Continue to boot Windows normally.
Fix 5: Run Startup Repair
Automatic repair fixes boot configuration damage from the interrupted update.
- In WinRE, go to Troubleshoot > Advanced options > Startup Repair.
- Let it run — it diagnoses and repairs boot issues automatically.
- If it reports it could not repair, note the log location and continue to Fix 6.
- If it succeeds, restart and observe whether the update completes.
- Check update history once booted.
Fix 6: System Restore to before the update
Roll the system back to a known-good point, sidestepping the stuck state entirely.
- In WinRE, go to Troubleshoot > Advanced options > System Restore.
- Choose a restore point dated before the problematic update.
- Let the restore complete — allow thirty minutes or more.
- Boot to the desktop and pause updates for a week.
- Use the pause to update drivers before retrying.
Fix 7: Check the drive and update drivers
Recurring restart stalls point at hardware or driver rot — fix the root cause before the next update.
- Back up your files once you can boot.
- Run
chkdsk C: /ffrom an elevated Command Prompt and let it complete. - Update storage, display, and chipset drivers from the manufacturer’s site.
- Uninstall third-party antivirus temporarily before the next update attempt.
- Retry the update with the charger connected and peripherals disconnected.
Fix 8: Disable fast startup
Fast startup’s hybrid shutdown can trap a half-finished update state across reboots, making the stall recur.
- Open Control Panel and go to Power Options > Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup.
- Shut down fully (not restart) and power on fresh.
- Retry the update with fast startup off — re-enable it later if you prefer it.
Closing
A Windows 10 update stuck on “Restarting” is frightening but almost always recoverable: wait long enough to be sure, power-cycle once, and use the recovery environment if needed. The pattern behind repeat stalls is consistent — aging drivers, aggressive antivirus, or a tired drive — and addressing it between updates keeps the spinner from ever overstaying its welcome again. The update will finish; the laptop is not bricked; work the ladder calmly.
