How to Reset the Servicing Stack After a Failed LCU on Windows 11

When a Latest Cumulative Update fails to install on Windows 11, the servicing stack itself can become corrupted. The servicing stack is the component that handles update installation, and a failed LCU can leave it in an inconsistent state. This prevents future updates from installing correctly. This article explains how to reset the servicing stack using built-in Windows tools. You will learn three methods: DISM, System Update Readiness Tool, and manual Component-Based Servicing reset.

Why a Failed LCU Corrupts the Servicing Stack

The servicing stack is a set of files and components that Windows uses to install, uninstall, and service updates. It runs before any update payload is applied. When a Latest Cumulative Update fails mid-installation, the servicing stack can be left with incomplete registry entries, pending file operations, or locked component manifests. This state is called a corrupted servicing stack. Symptoms include update errors 0x800f0922, 0x80073712, or the message “The servicing stack cannot be updated.” The root cause is that the update process did not finish its transaction log in the Component-Based Servicing store. Resetting the stack clears these stuck transactions and allows the next update to start cleanly.

Steps to Reset the Servicing Stack Using DISM

DISM Deployment Imaging and Servicing Management is the primary tool for servicing stack repair. Run these commands from an elevated Command Prompt or Windows Terminal Admin.

1. Open Command Prompt as Administrator
   Press the Windows key, type cmd, right-click Command Prompt, and select Run as administrator. Confirm the User Account Control prompt.
2. Check the servicing stack health
   Type DISM /Online /Cleanup-Image /CheckHealth and press Enter. This command reports whether the servicing stack detects corruption but does not repair it.
3. Scan for servicing stack corruption
   Type DISM /Online /Cleanup-Image /ScanHealth and press Enter. This scans all component store files and reports any corruption.
4. Restore the servicing stack
   Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This command connects to Windows Update to download healthy servicing stack files. The process may take 15 to 30 minutes. Do not close the window.
5. Verify the repair
   After completion, run DISM /Online /Cleanup-Image /CheckHealth again. The output should state that the component store is repairable or that no corruption was detected.

If the online repair fails because Windows Update itself is broken, proceed to the next method using an offline source.

Steps to Reset the Servicing Stack Using an Offline Windows Image

When the online DISM repair cannot connect to Windows Update, use a Windows 11 installation ISO or USB drive as the repair source.

1. Obtain Windows 11 installation media
   Download the Windows 11 Media Creation Tool from Microsoft’s website. Run it and select Create installation media USB flash drive or Download ISO file. Mount the ISO by double-clicking it or insert the USB drive. Note the drive letter, for example D.
2. Identify the install.wim file
   In the installation media, navigate to D:\sources. The file install.wim or install.esd contains the healthy servicing stack files.
3. Run DISM with the /Source parameter
   Open Command Prompt as Administrator. Type the following command and press Enter:
   DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess
   The /LimitAccess switch prevents DISM from contacting Windows Update. Replace D with the actual drive letter of your installation media.
4. Specify the image index if needed
   If the install.wim contains multiple editions, you must specify the index. To list indexes, run DISM /Get-WimInfo /WimFile:D:\sources\install.wim. Then add /Index:1 to the command, replacing 1 with the correct index number for Windows 11 Pro or Home.
5. Wait for the repair to complete
   The command will extract healthy servicing stack files from the offline image and replace corrupted ones. This may take 20 to 40 minutes. After completion, restart your PC.

Steps to Manually Reset the Component-Based Servicing Store

If DISM repairs succeed but the LCU still fails, the CBS store may have a stuck pending transaction. Clearing these files forces Windows to rebuild the store.

1. Stop the Windows Update service
   Open Command Prompt as Administrator. Type net stop wuauserv and press Enter. Then type net stop bits and press Enter.
2. Delete the CBS log and pending.xml
   Type del C:\Windows\Logs\CBS\CBS.log and press Enter. Then type del C:\Windows\WindowsUpdate.log and press Enter. Next, type del C:\Windows\Servicing\pending.xml and press Enter. This removes the transaction log that the failed LCU left behind.
3. Clear the SoftwareDistribution folder
   Type rmdir /s /q C:\Windows\SoftwareDistribution and press Enter. This removes all downloaded update files. They will be re-downloaded fresh during the next update check.
4. Restart the services
   Type net start wuauserv and press Enter. Then type net start bits and press Enter.
5. Run System File Checker
   Type sfc /scannow and press Enter. This checks all protected system files and replaces corrupted ones with cached copies. Restart your PC after the scan completes.

If the Servicing Stack Reset Fails

“The servicing stack cannot be updated” error persists

This error means the DISM repair itself failed because the servicing stack is too damaged. In this case, use the Windows 11 Reset This PC feature. Go to Settings > System > Recovery. Under Reset this PC, click Reset PC. Choose Keep my files to reinstall Windows 11 without removing your personal data. This replaces the entire servicing stack with a clean version from the installation media.

Update error 0x800f0922 after reset

This error indicates a disk space issue. The servicing stack requires at least 10 GB of free space on the system drive. Free up space by running Disk Cleanup: press Windows key, type Disk Cleanup, select the system drive, and click Clean up system files. Select Windows Update Cleanup and Delivery Optimization Files.

Failed LCU reappears after successful reset

If the same LCU fails again after a servicing stack reset, the LCU package itself may be corrupted. Download the LCU manually from the Microsoft Update Catalog. Search for the KB number, download the standalone package, and install it by double-clicking the .msu file. If it fails, the LCU is incompatible with your system build.

Item	DISM Online Repair	DISM Offline Repair	Manual CBS Reset
Requires internet	Yes	No	No
Repairs servicing stack	Yes	Yes	No clears transaction logs only
Risk of data loss	None	None	Low if pending.xml is deleted incorrectly
Best for	Minor corruption with working Windows Update	Severe corruption with broken Windows Update	Stuck pending updates after successful DISM repair

The servicing stack is a core Windows component that must remain healthy for all update operations. By using DISM with online or offline sources, you can repair most corruption caused by a failed LCU. If those methods fail, a manual CBS reset clears stuck transactions. After resetting the servicing stack, always run Windows Update again to install the LCU from scratch. For persistent failures, use the Reset This PC feature to restore the entire servicing stack to a clean state.