Fix Windows 11 Cumulative Update Keeps Failing

Issue type: Windows Update | Applies to: Windows 10, Windows 11

If a Windows 11 cumulative update keeps failing to install, the cause is usually a corrupted Windows Update cache, low working space, security software interference, or damaged system files that the update needs before it can complete. The right fix is to identify the failure point first, then repair that part of Windows instead of pressing “Retry” again and again.

Open Settings > Windows Update > Update history first. The specific error code next to the failed update narrows the cause significantly. Codes like 0x80073712 and 0x800f081f usually point to update component or repair-source problems, while rollback messages such as “Something didn’t go as planned. Undoing changes” mean the update started installing but failed during the reboot or staging phase.

Also check Settings > System > Storage and confirm that the system drive has at least 15–20 GB free. Cumulative updates need temporary space before and during installation, so a nearly full drive can create the same symptom as a damaged update cache.

What to Do First: Windows 11 Cumulative Update Keeps Failing

1. Note the exact error code from Settings > Windows Update > Update history.
2. Confirm at least 15–20 GB of free space on the system drive.
3. Restart the PC once using Restart, not Sleep or Hibernate, then retry the update from Settings.
4. Run the built-in Windows Update troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.
5. If the troubleshooter does not fix it, reset the Windows Update cache using the commands below.
6. If the cache reset does not fix it, run SFC and DISM to repair system files and the component store.

Reset the Windows Update Cache

A corrupted SoftwareDistribution folder is one of the most common reasons a cumulative update fails again at the same point. This folder stores downloaded update files. If the downloaded package is incomplete or damaged, Windows may keep trying to install the same broken files instead of downloading a clean copy.

Open Command Prompt as administrator and run these commands in order:

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv
net start bits
net start cryptsvc
net start msiserver

Restart the PC after the commands finish, then check for updates again. Renaming the folders is safer than deleting them because Windows rebuilds fresh versions automatically while the old folders remain available if you need to inspect them later. This cache problem can also appear when Windows Update is not downloading in Windows 11, so the repair steps overlap if you see both symptoms.

Run SFC and DISM to Repair System Files

If the update still fails after a cache reset, the problem may be a damaged Windows component store. Cumulative updates depend on existing system files, and if those files are missing or inconsistent, the installer may fail even when the update download itself is clean.

Open Command Prompt as administrator and run:

sfc /scannow

Let the scan finish completely. Then run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, restart the PC and run SFC one more time:

sfc /scannow

Running SFC again after DISM matters because DISM repairs the source Windows uses for component repair. If DISM fails with a repair-source or component-store message, compare the code with our guide to Windows Update error 0x800f081f, because that error often points to missing repair files or component-store damage.

Check Free Space Beyond the Main Drive

Normal storage space is the first thing to check, but it is not the only storage area that can affect updates. On some upgraded systems, especially PCs that moved from Windows 10 to Windows 11, the hidden EFI System Partition may be small or nearly full. That can contribute to update failures during the reboot phase, especially when Windows rolls back after showing “Something didn’t go as planned.” It is not the first cause to assume, but it is worth checking if cache repair and SFC/DISM do not change the result.

To check the layout, right-click Start, open Disk Management, and look for the partition labeled EFI System Partition. You do not need to change it during the first diagnosis. Just note whether it is unusually small or nearly full, especially on older upgraded PCs.

⚠️ Warning: Do not delete, format, or manually resize the EFI System Partition unless you have a full backup and know exactly what you are changing. A mistake here can make Windows fail to boot.

Install the Failed KB Manually

If Windows Update keeps failing but the error does not clearly point to system-file damage, install the failed KB manually. This bypasses part of the normal Windows Update delivery process and can work when the Settings app gets stuck during detection, download, or staging.

1. Open Settings > Windows Update > Update history.
2. Write down the KB number of the failed cumulative update.
3. Search that KB number in Microsoft Update Catalog.
4. Download the package that matches your system architecture, usually x64.
5. Run the downloaded .msu file and follow the prompts.
6. Restart the PC when the installer asks.

This is also useful when the update process never moves past the download stage. If your update freezes before it begins installing, use our guide for Windows Update stuck at 0 percent before moving to deeper repair steps.

Disable Third-Party Security Software for One Test

Third-party antivirus, VPN, firewall, and system-cleaner tools can interfere with update services. Do not remove security software as a first step, but it is reasonable to temporarily disable third-party protection for one controlled test after you have already reset the cache and checked storage.

1. Disconnect from unnecessary VPN software.
2. Temporarily pause third-party antivirus protection if it allows a short timed pause.
3. Restart the PC.
4. Try the cumulative update again from Windows Update.
5. Turn protection back on immediately after the test.

If the update works only while the tool is disabled, check that product’s update logs and exclusions. Do not leave your PC unprotected just because one update succeeded.

Use Update History to Avoid Repeating the Wrong Fix

Different update symptoms need different fixes. If the update fails before downloading, the problem is usually delivery or update-service related. If it downloads but fails during installation, the problem is more likely cache, storage, or system-file related. If it reaches a reboot percentage and rolls back, check component repair, drivers, storage, and any software that loads at startup.

If you see “Pending install” for a long time instead of a failed error code, use the steps in our guide to Windows Update pending install, because that state is different from a failed cumulative update.

Common Mistake

The most common mistake is force-restarting the PC during the installation phase because the percentage appears frozen; cumulative updates can sit at the same number for several minutes while Windows stages files, and forcing a restart during that phase can turn a repairable failed update into a damaged installation.

Best Next Step

If the same cumulative update still fails after resetting the cache, running SFC/DISM, checking storage, and trying the KB manually, use Microsoft’s official troubleshoot problems updating Windows guide and then consider an in-place repair install, because repeated failure after component repair usually means Windows itself needs a deeper repair while keeping your files and apps.

Frequently Asked Questions

Why does my Windows 11 cumulative update fail every time?

It usually fails every time because Windows is retrying the same broken update files, the component store is damaged, the system drive lacks enough working space, or another program is interrupting the installer.

Is it safe to reset the Windows Update cache?

Yes. Resetting the cache removes temporary update files and forces Windows to download clean copies. It does not delete personal files, apps, documents, photos, or Windows settings.

Should I skip a cumulative update that keeps failing?

You can pause updates temporarily while troubleshooting, but you should not ignore the problem for long. Cumulative updates include security fixes, and the next update may fail for the same reason if the underlying issue is not repaired.

Can a failed cumulative update be caused by low disk space?

Yes. Windows needs free space to download, unpack, and stage update files. Keep at least 15–20 GB free on the system drive before trying the update again.

Do I need to reset Windows if a cumulative update keeps failing?

Usually no. Resetting Windows should be a last resort. Cache repair, SFC, DISM, manual KB installation, and an in-place repair install are safer steps to try first.