Waiting for Windows 11 to apply a monthly cumulative update only to watch the screen report: ‘We couldn’t complete the updates. Undoing changes. Don’t turn off your computer’ is a notoriously frustrating scenario. In severe cases, the machine enters a continuous restart loop, attempting to stage the update, failing at 98%, and taking thirty minutes to roll back changes upon every boot. This failure signifies that while Windows Update downloaded the package successfully, the local Component-Based Servicing (CBS) installer encountered locked files, a corrupted component store, or insufficient system partition space during the offline installation phase.
Common Causes of Windows Update Rollback Failures
Windows updates modify low-level operating system files and kernel drivers. Rollback loops typically stem from:
- Corrupted SoftwareDistribution Download Cache: Partially downloaded, incomplete, or damaged update payload files cached in
C:\Windows\SoftwareDistribution. - Component Store (WinSxS) Corruption: Missing or damaged assembly manifests within the Windows side-by-side component store preventing patch integration.
- Insufficient System Reserved Partition (EFI/MSR) Space: The hidden EFI system partition lacking sufficient unallocated storage to stage updated bootloader files.
- Third-Party Antivirus File Locking: Aggressive security suites locking system DLLs while the Windows Update agent attempts to replace them during shutdown.
Step 1: Clear the Windows Update SoftwareDistribution Cache
Purging the temporary update staging directory forces Windows to download pristine installation payloads directly from Microsoft update servers.
- Press the Windows Key, type
cmd, right-click Command Prompt, and select Run as administrator. - Stop the active background update services:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver - Rename the corrupted cache folders using command line commands:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old - Restart the update services:
net start wuauserv net start cryptSvc net start bits net start msiserver - Navigate to Settings > Windows Update and click Check for updates.
Step 2: Run DISM and System File Checker Scans
Repairing damaged system files and servicing manifests ensures Windows Update can verify prerequisite dependencies.
- In an elevated Command Prompt or PowerShell window, execute DISM to repair the local component store:
DISM /Online /Cleanup-Image /RestoreHealth - Allow the scan to reach 100% completion. DISM queries Windows Update servers to download fresh copies of any damaged system binaries.
- Immediately follow with the System File Checker scan:
sfc /scannow - Restart your computer once SFC confirms: ‘Windows Resource Protection found corrupt files and successfully repaired them.’
Step 3: Run the Built-in Windows Update Troubleshooter
Windows 11 includes an automated diagnostic engine that re-registers update DLLs and resets network adapters.
- Open Settings (Win + I).
- Navigate to System > Troubleshoot.
- Click on Other troubleshooters.
- Find Windows Update and click the Run button.
- Follow the automated wizard to resolve detected service configuration errors, then reboot.
Step 4: Install the Update Manually via Microsoft Update Catalog
If the automated Windows Update client repeatedly rolls back, downloading and executing the standalone MSU installer package bypasses client-side download bottlenecks.
- Open Settings > Windows Update > Update history to identify the failing Knowledge Base identifier (e.g.,
KB5034441). - Open your browser and navigate to the official Microsoft Update Catalog (
catalog.update.microsoft.com). - Type the KB number into the search bar and download the cumulative update matching your system architecture (e.g., x64-based Systems).
- Temporarily disable third-party antivirus shields, double-click the downloaded
.msufile, and follow the installer prompts.