The screen says “Restarting.” The dots spin. Ten minutes pass. Thirty. An hour. Your Lenovo laptop is frozen in the limbo between shutting down and coming back up, and every instinct says to hold the power button — while another instinct warns you not to touch it during an update.

Both instincts have a point. Interrupting a genuinely working update is bad; waiting forever on a dead one is pointless. The skill is telling them apart, and the rule is simple: real update restarts show progress or disk activity, while stuck ones show neither for a very long time.

This guide covers the waiting test, the safe force-shutdown, and the recovery sequence if the update needs to be rolled back. Work through these in order — diagnose first, then act.

Why this happens

  • Driver hanging during shutdown. A misbehaving driver refuses to unload, freezing the restart sequence.
  • Servicing operation deadlocked. The update’s install phase wedges waiting on a resource that never frees.
  • Disk errors stalling file operations. Bad sectors or filesystem corruption halt the update’s file writes.
  • Lenovo firmware utilities interfering. Lenovo Vantage or BIOS-level tools can conflict with the restart handshake.
  • Corrupted update package. A damaged download deadlocks mid-install instead of failing cleanly.
  • Insufficient disk space. The update runs out of working room during the restart phase.
  • Fast Startup state corruption. A damaged hibernation file confuses the shutdown-restart cycle.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Apply the 90-minute rule before touching anything

Do nothing yet. Note the time, and watch for signs of life: the spinning dots animation (frozen dots versus moving dots), the disk activity light or sounds, and any percentage text. A working update restart shows moving dots, periodic disk activity, and usually a percentage.

If 90 minutes pass with frozen dots, zero disk activity, and no percentage change, it is stuck — proceed to Fix 2. If there is any sign of progress, keep waiting; large updates on slower SSDs genuinely take a while, and interrupting a working update creates the exact mess you are trying to avoid.

Fix 2: Force shutdown safely, then cold boot

Once you have confirmed the stall, hold the power button for 5-10 seconds until the laptop powers off. Unplug the charger, wait 30 seconds (this drains residual power and clears hung hardware states), then plug back in and power on.

In most cases, Windows detects the interrupted update and either resumes it or rolls it back automatically — watch for “Undoing changes” or a resumed percentage. Let whatever it does finish completely. Do not interrupt the rollback; it is repairing the interruption you just caused, and it needs to complete.

Fix 3: Boot into Safe Mode if normal boot fails

If the laptop loops back to the stuck “Restarting” screen or fails to boot, interrupt the boot three times in a row (hold power during the Windows logo) to trigger the Recovery Environment. Go to Troubleshoot, Advanced options, Startup Settings, Restart, then press 4 for Safe Mode.

Safe Mode loads a minimal driver set, bypassing whatever driver hung the restart. If Safe Mode works, the problem is almost certainly a third-party driver — note any devices with warnings in Device Manager. If even Safe Mode fails, stay in the Recovery Environment and continue to Fix 4.

Fix 4: Uninstall the problematic update from recovery

In the Recovery Environment, go to Troubleshoot, Advanced options, “Uninstall Updates.” Try “Uninstall latest quality update” first — this removes the cumulative update that likely caused the hang. If the trouble started with a feature update, use “Uninstall latest feature update.”

Restart after the uninstall. This returns the system to its pre-update state and should restore normal booting. Do not let Windows reinstall the same update immediately — pause updates for a week (Settings, Windows Update) while you fix the root cause. The undoing changes guide covers the rollback experience in detail.

Fix 5: Update Lenovo drivers and BIOS before retrying

The most common root cause of restart hangs on Lenovo machines is a driver that cannot handle the shutdown sequence — often storage, chipset, or power management drivers. Open Lenovo Vantage (or Lenovo support ) and install all pending BIOS and driver updates.

An outdated BIOS is a particularly common culprit for restart-phase hangs, because the update’s restart handshake involves firmware-level power transitions. Keep the charger connected during the BIOS flash. After updating everything, restart normally once to confirm clean booting before you unpause Windows Update.

Fix 6: Check disk health and free space

A failing drive can stall updates during file operations. Open Command Prompt as administrator and run chkdsk C: /f — schedule it for the next restart if prompted, then restart and let it complete. Also run a SMART check via your manufacturer’s diagnostic or wmic diskdrive get status.

Free up space too: aim for 15+ GB on C:. Updates that run out of working room during the restart phase hang instead of failing gracefully. If chkdsk finds and repairs errors, that may have been the entire problem — disk corruption is a silent cause of exactly this symptom. Microsoft documents disk checking in their Windows support resources .

Fix 7: Clean boot and staged update retry

Before letting the update try again, eliminate software conflicts: press Win+R, type msconfig, go to Services, check “Hide all Microsoft services,” click “Disable all,” then in Task Manager’s Startup tab disable all startup items. Restart — this is a clean boot with minimal third-party software.

Unpause updates and let the previously-failing update install in this clean state. If it succeeds, re-enable services in halves to identify the conflicting program — Lenovo utilities, antivirus suites, and “optimizer” tools are the usual suspects. If it still hangs even clean-booted, the issue is at the driver or servicing level, and the cumulative update failure guide for Lenovo is your next step.

Closing

A Lenovo laptop stuck on “Restarting” after an update needs patience first (the 90-minute rule), a safe force-shutdown second, and rollback third if normal boot will not return. The long-term fix is addressing why the restart hung — usually an outdated Lenovo driver or BIOS, sometimes disk issues — before the update tries again. Updates are resumable and rollbacks are automatic; your files were never in the danger you feared.

Frequently asked questions

How long should 'Restarting' take during a Windows update?
A normal update restart takes 5 to 20 minutes depending on the update size and your SSD speed. Feature updates can take up to an hour. If the ‘Restarting’ screen with the spinning dots has shown zero progress change for over 90 minutes — no percentage, no disk activity light — it’s stuck and the recovery steps in this guide apply.
Will holding the power button damage my laptop?
Holding the power button to force a shutdown is safe for the hardware. The risk is to the update in progress: interrupting it can leave the update half-applied, which is exactly why Windows has automatic rollback and recovery. Only force shutdown after confirming it’s genuinely stuck (90+ minutes, no disk activity), not during normal slow progress.
What if it gets stuck on 'Restarting' again after I force shutdown?
That suggests the update itself is the problem rather than a one-time hang. Boot into Safe Mode or the Recovery Environment, roll back the update via ‘Uninstall updates,’ then address the root cause — usually a driver conflict or corrupted download — before letting that update install again. The guide walks through this sequence.
How do I know the update didn't corrupt my files?
Windows updates don’t touch your personal files — they modify system files, and a failed update triggers automatic rollback to the pre-update state. After recovery, spot-check your documents and confirm your desktop looks normal. If the rollback completed, everything is as it was. File damage from updates is extraordinarily rare.