If Windows Update fails two or three times in a row, check system drive free space, driver conflicts, and disk health before changing settings. Repeated failures can trap you in retry loops, rollbacks, or a system that will not finish security fixes. This guide shows how to sort the cause by checking storage, drivers, and drive health first, then deciding what to fix next.

Step one: Run the update troubleshooter

Why does Windows Update keep failing?
A laptop screen shows the Windows Update settings page

The fastest first move is to run the built-in Windows Update troubleshooter, then retry once after checking free space on the system drive. That tool resets update services and often clears corrupted downloads. If the same failure returns, the pattern usually points to storage pressure, a bad cache, antivirus interference, or a driver problem.

Start with the built-in reset

  1. Open Settings > System > Troubleshoot > Other troubleshooters on Windows 11, or Settings > Update & Security > Troubleshoot on Windows 10.
  2. Run Windows Update.
  3. Restart the PC.
  4. Try the update once more.

Microsoft lists “Troubleshoot problems updating Windows” in its help topics, and its support hub includes a Windows Update FAQ. Microsoft also says Windows 11 is becoming “up to 20% more responsive,” while the Windows Experience Blog says Windows Update is being improved to reduce restarts. Those changes do not remove local causes on your PC. (Microsoft Support)

Likely causes to check first

Most repeated failures come from a short list, and the symptom tells you where to look. Stuck-at-percentage failures often trace to low space or a damaged download. Nightly retry loops usually point to the cache or a service issue. Rollbacks after install are more often drivers, storage hardware, or a servicing problem.

1. Low disk free space and full temporary storage

Free space matters before another retry. Windows needs room to unpack files, stage replacements, and write rollback data. Clear Downloads and the Recycle Bin first, then retry the update. If the drive is nearly full, the same failure can repeat even when the download itself is fine.

  1. Open Settings > System > Storage.
  2. Check free space on the system drive.
  3. Empty Recycle Bin.
  4. Clear large items from Downloads.
  5. Try Windows Update again.

If the system drive has around 9 GB free, a feature update may still stall near the end. That is enough room for the download to start, but not always enough for unpacking and rollback files. Clearing several gigabytes first often changes the result more than changing update settings.

2. Corrupted update cache or download folder

A broken cache can trap Windows in a retry loop. When the update downloads partially, fails verification, and then reuses the same bad files, the same error returns night after night. In that case, clear the Windows Update cache and let Windows rebuild it on the next attempt.

  1. Open Windows Terminal or Command Prompt as administrator.
  2. Run: net stop wuauserv
  3. Run: net stop bits
  4. Run: net stop cryptsvc
  5. Rename the cache folders: ren %windir%\SoftwareDistribution SoftwareDistribution.bak and ren %windir%\System32\catroot2 catroot2.bak
  6. Run: net start wuauserv, net start bits, and net start cryptsvc
  7. Retry Windows Update.

3. Third-party antivirus blocking writes

Security software can block system file writes during an update cycle. Pause third-party antivirus for one update cycle only, then re-enable it after the test. Do not remove it permanently just to diagnose one failed update. If the update succeeds with protection paused, the block is likely in the security software rather than Windows itself.

  1. Open the antivirus app.
  2. Pause real-time protection for one update cycle.
  3. Restart the PC.
  4. Run Windows Update.
  5. Turn protection back on right after the test.

A common first-timer mistake is to disable antivirus and then leave it off for days. That turns a test into a long exposure. Keep the pause short, test once, and then reactivate protection.

Why does Windows Update fail and retry every night?

Nightly retry loops usually mean Windows keeps finding the same bad download or blocked write and then schedules another attempt. If the system tries again after hours and fails in the same way, focus on cache corruption, storage space, and security software before chasing drivers or hardware.

Check the cache and security software

  1. Confirm that the system drive has free space.
  2. Clear Downloads and Recycle Bin.
  3. Run the Windows Update troubleshooter once.
  4. Pause third-party antivirus for one update cycle.
  5. Retry the update manually.

If the same file keeps failing at night, the Windows Update cache/download folder may need manual clearing. If the retry loop ends after antivirus is paused, the block is likely local security software. If it persists, move to servicing logs and drive health.

Why did the update roll back?

A rollback after install usually points away from the download phase and toward finalization. Driver incompatibility is a common trigger, especially for storage and chipset hardware. If the failure shows error code 0xC1900101, treat drivers and connected hardware as the first suspect, then inspect the Panther logs. (Microsoft Learn)

Inspect the rollback logs

  1. Open C:\$WINDOWS.~BT\Sources\Panther.
  2. Check setupact.log for the last steps before rollback.
  3. Check setuperr.log for the explicit error line.
  4. Look for storage, chipset, or driver entries around the failure time.
  5. If a driver update recently landed, use Device Manager > the device > Properties > Driver > Roll Back Driver.

Suppose a Wi‑Fi adapter or printer stops working right after a quality update finishes, but the PC still boots normally. That is a driver-regression pattern, not a download problem. Rolling back the device driver is safer than replacing hardware at the first sign of trouble.

Do not interrupt a feature update rollback that shows “undoing changes made to your computer.” That screen can run for a long time. If it gets interrupted, the system may need repair before Windows will update again.

Failure triage checklist

Failure triage checklist
A Windows update failure dashboard with warning panels and a magnifying glass

This checklist separates the three failure modes that matter most: stuck at a percentage, nightly retry loops, and rollback after install. Use the symptom to pick the likely cause, then inspect the matching log file. The escalation threshold tells you when to stop repeating the same fix and move to deeper repair.

Symptom Most likely cause First action Log file to inspect Escalation threshold
Stuck at a percentage, especially near the end Low disk space, corrupted download, or a blocked write Free space, clear Downloads and Recycle Bin, then run the troubleshooter Windows Update logs and, if needed, setuperr.log If it sits for about 2 hours with no drive activity, move to cache reset and log review
Fails and retries every night Corrupted update cache or security software interference Pause third-party antivirus for one cycle and clear the update cache Windows Update logs If the same package fails again after cache reset, inspect servicing logs
Rolls back after install Driver incompatibility or failing storage hardware Check for 0xC1900101, then roll back the broken device driver if needed setupact.log and setuperr.log If rollback repeats on a clean retry, suspect storage or a repair install

Still not working?

Still not working?
Windows Update settings screen showing update status and options

If the basic reset does not help, move to system image repair and servicing logs. Use DISM for deeper repair, then read CBS.log for signs of component-store damage. If the machine still fails after that, a repair install or vendor service may be the next step, especially when storage problems keep returning.

Run deeper repair and check servicing logs

  1. Open Command Prompt as administrator.
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. After DISM finishes, open C:\Windows\Logs\CBS\CBS.log.
  4. Look for repeated servicing errors or failed package writes.
  5. If the same failure returns after DISM, suspect a failing drive or seek repair help.

Woodstock Computer Repair says a stuck update should get two hours before any forced shutdown. That is a sensible cutoff when the drive is still active. But if the same error appears again after cache repair, DISM, and driver rollback, repeated failure is no longer a normal slow install.

Prevention: Before major updates, keep a few extra gigabytes free on the system drive and remove stale downloads. That lowers the chance of unpacking failures and retry loops.

On Windows 10, the settings path often starts in Settings > Update & Security. On Windows 11, the update page is under Settings > Windows Update. The fix order stays mostly the same on both versions, but the symptom matters more than the version.

Keep reading

Frequently asked questions

How do I fix a Windows update that keeps failing on Windows 11?

Start with Settings > System > Troubleshoot > Other troubleshooters > Windows Update, then check Settings > Windows Update for free space pressure and retry once. If it still fails, inspect setupact.log and setuperr.log under C:\$WINDOWS.~BT\Sources\Panther.

How do I fix a Windows update that keeps failing on Windows 10?

Open Settings > Update & Security > Troubleshoot, run the Windows Update troubleshooter, and then clear enough space on C: for unpacking. If the update rolls back, use Device Manager to roll back the last driver change and check setuperr.log.

Could a full drive be causing Windows updates to fail?

Yes. A full or nearly full system drive is one of the most common reasons for retry loops. Clear Downloads and Recycle Bin first, then retry. If the drive remains cramped, Windows may download the update but fail during unpacking or rollback staging.

Should I remove antivirus if Windows updates keep failing?

Do not uninstall it first. Pause third-party antivirus for one update cycle, run the update, and then turn protection back on. If the update succeeds while protection is paused, the security software likely blocked a write. If it still fails, the cause is probably elsewhere.

When is a failed Windows update a sign of a bad drive?

Suspect storage when failures repeat after free-space cleanup, cache reset, and DISM repair, or when the machine also slows down, hangs, or rolls back with no clear driver clue. Repeated rollback plus no useful log progress in setupact.log can point to failing storage hardware.