Restart the services you stopped earlier:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
net start trustedinstaller
Finally, reset the Windows Update cache via the UI:
Resolving error 0x8024a22a requires a methodical, escalation-based strategy. Users should avoid “shotgun” registry edits and instead follow a logical progression:
Phase 1: Service Restoration
Phase 2: SoftwareDistribution Reset
Phase 3: DISM and SFC Scans
Phase 4: Windows Update Troubleshooter
Experiencing the 0x8024a22a error? You are not alone. This frustrating Windows Update error typically appears when trying to download feature updates (like Windows 10 version 22H2 or Windows 11) or cumulative quality updates. It often comes with a message stating: "There were some problems installing updates, but we’ll try again later."
Most standard troubleshooting guides will tell you to run the Windows Update Troubleshooter or reboot your PC. If you are reading this, you have likely tried that already—and it didn’t work.
In this article, we provide a "better" approach. We will move beyond the superficial fixes and address the root causes: corrupted update components, pending reboots stuck in a loop, and damaged servicing stacks. 0x8024a22a windows update error better
Most guides tell you to delete the SoftwareDistribution folder. That is fine, but the Catroot2 folder is equally important for error 0x8024a22a.
ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\System32\catroot2 Catroot2.bak
Why both? SoftwareDistribution stores download history. Catroot2 stores signature files for Windows updates. If they are out of sync, the "pending store commit" cannot resolve.
The built-in troubleshooter is the first line of defense. It can automatically detect and fix inconsistencies in the update service settings. Restart the services you stopped earlier: net start
Status: Action Required Severity: Medium Affected Component: Windows Update Service / Background Infrastructure