‘Undoing changes’ is supposed to be a temporary safety net — but on Lenovo laptops it sometimes becomes the trap itself, spinning for hours with no progress. The rollback is reversing a failed update, and on machines with big Lenovo driver stacks, nearly full drives, or drive encryption, that reversal can slow to a crawl or freeze outright.

There are two problems to solve: the stuck rollback in front of you right now, and the update failure that triggered it (because retrying without fixing the cause just buys another rollback). This guide handles both in that order — recover first, diagnose second.

If the rollback eventually completes on its own, skip to the diagnosis section. For the general non-stuck rollback, the undoing changes troubleshooting guide covers the standard path.

Why this happens

  • Nearly full system drive: Rollback needs working space; a drive above 90% full makes the reversal crawl or stall.
  • Failing drive: Bad sectors in the rollback area freeze file operations silently — the spinner keeps turning with nothing happening.
  • Interrupted first rollback: A premature forced shutdown corrupts the rollback state, and the retry of the rollback itself hangs.
  • Lenovo driver restore conflict: A Lenovo driver that fails to restore to its pre-update version blocks the rollback sequence.
  • Drive encryption overhead: OPAL/TCG or BitLocker encryption multiplies the I/O cost of reversing thousands of files.
  • Corrupt rollback data: If the update’s own staging was corrupt, the rollback may lack clean data to restore from.
  • Original update failure unresolved: The update failed for a reason (driver, store, cache); the rollback inherits the same broken environment.

How to fix it

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

Fix 1: Wait properly — then verify it is truly stuck

Most ‘stuck’ rollbacks are just slow. Verify before intervening.

  1. Keep the charger connected; do nothing for at least 2 hours (3 on a hard drive).
  2. Watch for disk activity: drive LED, sounds, heat. Activity means progress.
  3. Only after hours of zero activity should you treat it as stuck and continue.

Fix 2: Force one clean shutdown if it is frozen

A single decisive shutdown is recoverable; endless waiting on a frozen rollback is not progress.

  1. Hold the power button 10 seconds until fully off.
  2. Disconnect all peripherals.
  3. Wait 30 seconds, power on with only the charger.
  4. Let the machine do whatever it does next — boot loop into Automatic Repair is expected and useful.

Fix 3: Recover through WinRE

The recovery environment gives you the tools to undo the damage safely.

  1. If Automatic Repair appears, go to Troubleshoot → Advanced options.
  2. Try System Restore to a pre-update point first — it is the gentlest recovery.
  3. If no restore point exists, use ‘Uninstall Updates’ → ‘Uninstall latest quality update’ (or feature update).
  4. If the machine boots normally afterward, the crisis is over — now diagnose the cause.

Fix 4: Free disk space from WinRE if the drive is full

A full drive stalls rollbacks. Make room before anything else.

  1. In WinRE → Command Prompt, identify your Windows drive letter (often D: in WinRE).
  2. Delete temp files and the SoftwareDistribution download cache: rd /s /q D:\Windows\SoftwareDistribution\Download.
  3. Run chkdsk D: /f to fix file system errors.
  4. Reboot and let the rollback or boot proceed with the freed space.

Fix 5: Update Lenovo drivers and BIOS before retrying

Lenovo-specific drivers are the leading trigger of the original failure. Fix them now.

  1. Once booted, open Lenovo Vantage and install all system/driver updates.
  2. Update the BIOS from Lenovo support for your exact model, charger connected.
  3. Update chipset and storage drivers specifically — they dominate rollback triggers.
  4. Reboot and confirm stability before touching Windows Update.

Fix 6: Clear the cache and repair the store

Eliminate the corrupt-payload and store-damage causes before the retry.

  1. Elevated prompt: stop wuauserv, cryptSvc, bits, msiserver; rename SoftwareDistribution; restart services.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
  3. Reboot. The environment is now clean for a retry.

Fix 7: Retry under controlled conditions

The retry must differ from the failed attempt or it will roll back again.

  1. Disconnect all peripherals; charger only.
  2. Uninstall third-party antivirus temporarily.
  3. Run the update with sleep disabled.
  4. If it rolls back again despite all this, check drive SMART health — and compare notes with the Update Assistant 99% guide , since Lenovo stalls share root causes. Microsoft’s Windows support hub documents the official recovery options as well.

Fix 8: Pause Lenovo Vantage updates during the retry window

Lenovo Vantage runs its own driver and BIOS update jobs on a schedule, and those jobs can collide with Windows Update’s rollback or retry — reintroducing the very driver trigger you just removed, mid-repair. This collision is more common than most people realize, because Vantage’s schedule ignores Windows Update activity entirely. Silencing Vantage during the repair window removes the variable completely — when the retry succeeds, you know the fix was yours, not luck. Re-enable everything afterward; Vantage is genuinely useful, it just needs to wait its turn.

  1. Open Lenovo Vantage → settings and disable automatic updates temporarily.
  2. Open Task Scheduler, find the Lenovo tasks, and disable the update-related ones for the duration of the repair.
  3. Complete the Windows Update retry with Vantage fully quiet and only the charger connected.
  4. After the update succeeds, re-enable Vantage updates and let it install everything it offers.
  5. Adopt the sequencing habit going forward: Vantage drivers first, Windows updates second — never let the two run simultaneously.

Closing

A Lenovo stuck on ‘undoing changes’ needs patience first — most are slow, not frozen — then one clean recovery through WinRE if truly stuck. Afterward, update Lenovo’s drivers and BIOS, clear the cache, repair the store, and retry under controlled conditions. The rollback only repeats when the original trigger is left in place.

Frequently asked questions

Why does 'undoing changes' get stuck on Lenovo laptops?
The rollback itself usually stalls because of disk-level slowness (a nearly full drive or a failing drive), a Lenovo driver that will not restore cleanly, or an interrupted first rollback attempt. On ThinkPads with OPAL/TCG drive encryption, the rollback’s disk operations can also slow dramatically.
How long should I wait on a stuck 'undoing changes' screen?
Give it a full 2–3 hours on the first occurrence, especially on hard drives. Lenovo laptops with large driver sets roll back more slowly. Only treat it as stuck after hours of zero disk activity. Disk activity is the only reliable signal; the on-screen spinner tells you nothing.
Will forcing a shutdown during 'undoing changes' brick my ThinkPad?
One forced shutdown during a stuck rollback is usually recoverable via WinRE (System Restore or update uninstall). Repeated forced shutdowns are what cause real damage. If the rollback is genuinely frozen for hours, one clean shutdown is the right call.
Do Lenovo drivers cause the original update failure?
Often yes. Lenovo’s power management, hotkey, and storage drivers are frequent rollback triggers when they are outdated. Updating them via Lenovo Vantage before retrying prevents the repeat failure. Pay special attention to the power management and storage drivers, which are the most common rollback triggers on ThinkPads and Ideapads.