Windows 10 may be in its twilight, but millions of laptops still run it — and they still hit “We couldn’t complete the updates, undoing changes” with regularity. The causes skew a little different than on Windows 11: years of accumulated cumulative updates have bloated the component store, vendors have stopped refreshing drivers for older models, and the update cache has had years to fragment. The rollback mechanics are identical, though — a failed transaction being reversed — and so is the repair logic.
There is one Windows 10-specific consideration before you start: the menus moved. Troubleshooters live under Settings, then Update & Security, then Troubleshoot; Update history sits under Windows Update, then View update history. The commands — DISM, SFC, the net stop/start service dance — are exactly the same. Work through the fixes below in order, noting the failed KB and error code first.
And a practical note for older hardware: if this laptop has a mechanical hard drive, multiply every time estimate in this guide. Rollbacks and repairs that take 20 minutes on an SSD can take two hours on a spinning disk. That is normal, not broken.
Why this happens
- Years of accumulated WinSxS bloat: superseded update payloads crowding the component store and the system drive.
- Vendors abandoning driver updates: old drivers that modern cumulative updates cannot migrate cleanly.
- A fragmented, aging update cache: years of SoftwareDistribution history raising corruption odds.
- Low disk space on older small drives: the staged update plus rollback snapshot exceeding available room.
- Third-party antivirus with deep hooks: legacy security suites interfering with file replacement.
- Pending servicing operations: unfinished previous updates leaving the stack inconsistent.
- Failing aging hardware: older SSDs and HDDs developing read errors the installer reads as corruption.
- A specific cumulative update with a known bug: some months’ updates simply break on certain configurations.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Let the rollback finish and record the failure
Patience first, evidence second. The error code shapes everything downstream.
- Keep the charger connected and give the “undoing changes” screen 30 to 60 minutes (longer on HDDs), watching the disk light.
- Once on the desktop, go to Settings, then Update & Security, then Windows Update, then View update history.
- Note the failed KB number and error code.
- If the desktop never appears, the Windows 10 undoing-changes stuck guide covers the recovery path in detail.
Fix 2: Run the Windows Update troubleshooter
Windows 10’s troubleshooter resets the classic failure points automatically.
- Go to Settings, then Update & Security, then Troubleshoot, then Additional troubleshooters.
- Run the Windows Update troubleshooter and apply all recommended fixes.
- Restart the laptop.
- Check for updates again. If the troubleshooter will not run, see our troubleshooter repair guide .
Fix 3: Deep-clean years of update bloat
On a long-running Windows 10 install, this step alone frequently breaks the loop.
- Run Disk Cleanup as administrator and click “Clean up system files.”
- Select Windows Update Cleanup, Temporary files, and Previous Windows installations — this can reclaim 10 to 15 GB.
- Confirm at least 20 GB free on C: afterward.
- Turn on Storage Sense under Settings, then System, then Storage for ongoing hygiene.
- Retry the update with the reclaimed space.
- For the deepest clean, also tick “Device driver packages” in Disk Cleanup’s system-files view — years of superseded drivers can occupy several gigabytes on old installs.
Fix 4: Reset the update cache
Standard servicing repair: a corrupted cache fails the same package identically forever.
- Open Command Prompt as administrator.
- Run
net stop wuauserv,net stop cryptSvc,net stop bits,net stop msiserver. - Rename
C:\Windows\SoftwareDistributiontoSoftwareDistribution.oldandC:\Windows\System32\catroot2tocatroot2.old. - Restart the services and reboot.
- Check for updates on a stable connection. Microsoft’s update support pages document this procedure.
Fix 5: Repair the component store with DISM and SFC
Years of patching make store damage more likely on Windows 10 — repair it before retrying.
- In an elevated Command Prompt, run
DISM /Online /Cleanup-Image /RestoreHealth. - Allow 15 to 40 minutes on older hardware.
- Follow with
sfc /scannow. - Reboot and retry the update.
Fix 6: Update drivers from the manufacturer and strip interference
Old drivers are a prime Windows 10 rollback trigger — refresh them from the source.
- Visit your laptop manufacturer’s support site and install the latest Windows 10 drivers for your model, especially chipset and storage.
- Disconnect all USB peripherals except keyboard and mouse.
- Temporarily disable third-party antivirus and disconnect VPNs.
- Retry the update in this clean state.
- If a specific driver update keeps failing, hide it with the show-or-hide updates troubleshooter.
- After success, re-enable your antivirus and reconnect peripherals one at a time to confirm nothing reintroduces the conflict.
Fix 7: In-place upgrade repair with the Media Creation Tool
The definitive fix for a Windows 10 servicing stack that will not heal — reinstall Windows over itself, keeping everything.
- Download Microsoft’s Media Creation Tool for Windows 10 from the official software download page .
- Run it and choose “Upgrade this PC now.”
- Select “Keep personal files and apps” when prompted.
- Allow one to two hours for the repair to complete.
- Afterward, updates should install cleanly — verify in Update history.
Closing
Windows 10’s undoing-changes loop is usually a maintenance story: years of update bloat, aging drivers, and a cache that has never been reset. The deep cleanup in Fix 3 plus a cache reset resolves most cases without touching the heavier tools. And if the loop keeps returning on hardware that qualifies, treat the repaired system as your launchpad for a planned Windows 11 upgrade — on your schedule, not the rollback screen’s. Once updates flow again, make the cleanup a monthly ten-minute habit: it keeps a Windows 10 machine updating smoothly for years.
