Fix Cumulative Update Refusing to Install Due to Pending.xml on Windows 11
🔍 WiseChecker

Fix Cumulative Update Refusing to Install Due to Pending.xml on Windows 11

When a cumulative update fails to install on Windows 11, the error often points to a corrupted or stuck Pending.xml file in the Windows servicing stack. This file tracks pending operations like update installations and component removals. If Pending.xml becomes damaged or stuck, Windows Update cannot process new updates and refuses to install them. This article explains why the Pending.xml file causes update failures and provides step-by-step methods to remove or repair it so your cumulative update installs successfully.

Key Takeaways: Fixing Cumulative Update Failures Caused by Pending.xml

  • Delete or rename Pending.xml in C:\Windows\WinSxS: Removes the stuck operation so Windows Update can start fresh.
  • Run DISM with the RestoreHealth parameter: Repairs the servicing stack and checks for corruption in system files.
  • Use the Windows Update Troubleshooter: Automatically detects and resets common update-related issues including stuck pending operations.

ADVERTISEMENT

Why a Stuck Pending.xml Blocks Cumulative Updates on Windows 11

The Pending.xml file is located at C:\Windows\WinSxS and stores a list of operations that Windows needs to complete before the system is fully updated. These operations include installing or removing update packages, servicing stack updates, and component cleanup tasks. When a cumulative update installation is interrupted by a power loss, forced shutdown, or a failed update, the Pending.xml file may contain incomplete or corrupted entries. Windows Update reads this file at the start of every update session. If it finds a stuck operation, it refuses to install new updates because it cannot safely proceed with a pending task that might be in an unknown state.

Another common cause is a servicing stack update that did not finish correctly. The servicing stack is the component that installs Windows updates. If the stack itself is damaged, it may write incomplete data into Pending.xml. In some cases, third-party antivirus software or disk cleanup tools mistakenly modify the WinSxS folder, corrupting the file. The result is always the same: Windows Update downloads the cumulative update, prepares to install it, then fails with error codes like 0x80073712, 0x800f0922, or a generic message that says “Some update files are missing or have problems.”

Steps to Remove or Repair the Stuck Pending.xml File

Before you start, ensure you have administrative privileges on the Windows 11 device. The methods below require you to open Command Prompt or Windows PowerShell as an administrator. Back up important data before modifying system files.

Method 1: Delete or Rename Pending.xml Manually

  1. Open Command Prompt as administrator
    Press the Windows key, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes in the User Account Control prompt.
  2. Stop the Windows Update service
    Type net stop wuauserv and press Enter. Wait for the service to stop. This prevents Windows Update from interfering while you modify the file.
  3. Navigate to the WinSxS folder
    Type cd C:\Windows\WinSxS and press Enter. This is the directory where Pending.xml resides.
  4. Rename the Pending.xml file
    Type ren Pending.xml Pending.old and press Enter. Renaming is safer than deleting because you can restore the file if something goes wrong.
  5. Restart the Windows Update service
    Type net start wuauserv and press Enter. Then type exit to close Command Prompt.
  6. Run Windows Update again
    Open Settings > Windows Update and click Check for updates. The cumulative update should now download and install without the Pending.xml error.

Method 2: Use DISM to Repair the Servicing Stack

  1. Open Windows PowerShell as administrator
    Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin). Click Yes.
  2. Run the DISM RestoreHealth command
    Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This scans the servicing stack and repairs corruption. The process may take 10 to 30 minutes. Do not close the window.
  3. Wait for the operation to complete
    DISM will display a progress percentage. If it finds corruption, it will attempt to repair it using Windows Update or a local source. If the scan completes without errors, proceed to the next step.
  4. Run System File Checker
    Type sfc /scannow and press Enter. This checks all protected system files and replaces any corrupted ones. Restart your device after the scan finishes.
  5. Check for updates again
    Go to Settings > Windows Update and click Check for updates. The cumulative update should install normally.

Method 3: Run the Windows Update Troubleshooter

  1. Open Settings
    Press Windows + I to open Settings.
  2. Navigate to Troubleshoot
    Go to System > Troubleshoot > Other troubleshooters.
  3. Run the Windows Update Troubleshooter
    Find Windows Update in the list and click Run. The troubleshooter will scan for common issues, including stuck pending operations, and attempt to fix them automatically.
  4. Apply the recommended fixes
    If the troubleshooter finds problems, click Apply this fix. Follow any on-screen instructions. Restart your device when prompted.
  5. Retry the update
    Open Windows Update and click Check for updates. The cumulative update should proceed without the Pending.xml error.

ADVERTISEMENT

If the Cumulative Update Still Refuses to Install

If the main methods above do not resolve the issue, the Pending.xml file may be locked by another process or the corruption may be deeper. Use the following advanced steps.

Delete Pending.xml in Safe Mode

Booting into Safe Mode loads only essential drivers and services. This prevents the Windows Update service or other processes from locking Pending.xml.

  1. Boot into Safe Mode
    Press Windows + I to open Settings. Go to System > Recovery. Under Advanced startup, click Restart now. After the device restarts, select Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 or F4 to enter Safe Mode.
  2. Delete Pending.xml
    Open File Explorer and navigate to C:\Windows\WinSxS. Find Pending.xml, right-click it, and select Delete. If you cannot delete it, rename it to Pending.old as described in Method 1.
  3. Restart normally
    Close all windows and restart your device. Once back in normal mode, run Windows Update again.

Use the Media Creation Tool to Perform an In-Place Upgrade

If the Pending.xml file is persistently corrupted and all other fixes fail, an in-place upgrade reinstalls Windows 11 while keeping your files and apps. This repairs the servicing stack and clears all pending operations.

  1. Download the Media Creation Tool
    Go to the official Microsoft website and download the Windows 11 Media Creation Tool. Run the tool as administrator.
  2. Select Upgrade this PC now
    Accept the license terms. On the next screen, choose Keep personal files and apps. Click Install. The process takes about an hour.
  3. Verify the update after upgrade
    Once the upgrade completes, go to Settings > Windows Update and check for updates. The cumulative update should install without errors.

Pending.xml vs Other Update Failure Causes

Item Pending.xml Corruption Corrupt System Files Disk Space Issues
Description Stuck or damaged operation file blocks new updates Missing or damaged DLLs or executables prevent update installation Insufficient free space on the system drive stops update download and extraction
Primary symptom Update fails with error 0x80073712 or 0x800f0922 Update fails with error 0x80070002 or 0x80070570 Update fails with error 0x80070070 or message about low disk space
Fix method Delete or rename Pending.xml in WinSxS Run SFC /scannow and DISM RestoreHealth Free up disk space using Storage Sense or manual cleanup

The Pending.xml fix is specific to the servicing stack queue. If the error persists after clearing Pending.xml, run the System File Checker and DISM tools to rule out broader system file corruption. Always check disk space on the C: drive before attempting a cumulative update.

ADVERTISEMENT