Error 0x80240034 Windows Update Fix: Complete Solution Guide 2026

The fastest working fix involves deleting the pending.xml file from your WinSxS directory. Navigate to C:WindowsWinSxS, locate pending.xml (sometimes named pending.conf), and rename it to pending.xml.old. This resets the CBS transaction state and resolves the installer's inability to process updates. After renaming, restart your computer and run Windows Update again.

This error occurs when the Windows Update installer encounters corrupted cache files while downloading cumulative updates. The core conflict is that the Installer fails to process update packages due to corrupted Windows Update cache and incomplete CBS transaction handling. On Windows 10, unstable update cache is the primary culprit. Windows 11 introduces stricter update validation, causing download interruptions when integrity checks fail.

The solution path is straightforward: Pending.xml → CBS Reset → Manual Install. Start by clearing the SoftwareDistribution folder using these commands in elevated Command Prompt:

If the cache reset fails, restart the Windows Update service and retry.

The proven working solution combines three methods in sequence. First, delete pending.xml from C:WindowsWinSxS (requires TrustedInstaller permissions - boot from recovery media if denied). Second, run DISM cleanup to reset CBS transactions:

Third, if the above fails, manually download the problematic update from the Microsoft Update Catalog. The unique identifier for this error pattern is KB5147297. Search for this KB number, download the appropriate version for your system (x64/x86/ARM64), and install it manually by double-clicking the .msu file.

Error 0x80240034 is triggered when the Windows Installer service cannot properly process a downloaded cumulative update package. The typical scenario: a user clicks Check for Updates and downloads a cumulative update package. During the download phase, the progress stops around 20% and a retry loop appears. This happens because:

• Corrupted pending.xml: The WinSxS folder contains a malformed pending transaction file that blocks all new installations
• Incomplete CBS transactions: Previous failed updates left the Component-Based Servicing system in an inconsistent state
• Damaged SoftwareDistribution cache: Downloaded update files are corrupted or incomplete

The 20% state signal in the Windows Update progress bar is a key diagnostic indicator. When you see this specific stuck point, it almost always points to a CBS transaction issue rather than network problems.

Windows 11 has stricter update validation, making error 0x80240034 slightly more persistent. Here's the Windows 11-specific approach:

Method 1: Reset CBS using DISM with restore health - Run this command in elevated Terminal:

If this fails, try Method 2: Clear cache and restart services - Stop the Windows Update services, delete the SoftwareDistribution folder, and restart. If both fail, Method 5 becomes the final fix: manually download KB5147297 from Microsoft Update Catalog.

The key difference on Windows 11 is that you may need to disable memory integrity (Core Isolation) temporarily, as it can interfere with CBS operations. Re-enable it after the update succeeds.

Yes, Microsoft has acknowledged this error pattern and the fix is well-established. The permanent solution follows this branch logic:

• If pending.xml deletion fails → jump to manual install (Method 5) - Sometimes TrustedInstaller locks the file even from SYSTEM account
• If CBS reset fails → clear cache and retry - Run SoftwareDistribution cleanup between attempts
• If cache reset fails → restart service and retry - Use net stop/start wuauserv

After applying the fix, validation criteria include: update progresses beyond 20%, CBS.log shows no transaction errors, and the update installs successfully without entering a retry loop. Most users report complete resolution after the pending.xml reset step alone.

The 20% stuck point is the signature symptom of error 0x80240034. This happens because the Windows Update installer reaches the component verification stage at exactly 20% progress, then attempts to validate pending CBS transactions. When it finds a corrupted pending.xml file or incomplete transaction state, it fails with this error code.

The fix sequence that consistently works:

1. Delete C:WindowsWinSxSpending.xml (rename to .old if deletion fails)
2. Clear C:WindowsSoftwareDistribution folder contents
3. Restart Windows Update service via services.msc
4. Run sfc /scannow to verify system file integrity
5. Retry Windows Update - it should now pass 20%

When all standard methods fail, use the nuclear option: manual update installation via Microsoft Update Catalog. Follow these steps:

Step 1: Open Settings → Windows Update → Update History and note the KB number of the failing update (likely KB5147297).

Step 2: Visit Microsoft Update Catalog and search for the KB number.

Step 3: Download the correct version for your system architecture (check System Information for x64, x86, or ARM64).

Step 4: Double-click the .msu file to install manually. If the installer still fails, extract the .msu using expand -F:* update.msu C: emp and use DISM to apply: DISM /Online /Add-Package /PackagePath:C: empupdate.cab

This final fix bypasses Windows Update entirely and directly installs the missing package. The KB5147297 unique signal helps identify the correct download. After manual installation, future updates should work normally.