How to Fix Windows Update Error 0x8024200B
What error 0x8024200B means
Error 0x8024200B has a blunt official name: WU_E_UH_INSTALLERFAILURE. Microsoft's own description says the installer failed to install (uninstall) one or more updates. That wording matters, because it tells you where the failure happened. The problem is not that Windows could not find the update, and it is not that your PC is too old for it. The download stage largely worked. The install stage did not.
Think of a Windows update as a two-part job. First, Windows Update downloads the package and checks that it arrived intact. Then the installer unpacks it, replaces system files, registers components, and cleans up after itself. Error 0x8024200B fires when that second part breaks down. The installer starts, hits something it cannot get past — a corrupted file in the cache, a transfer service stuck in a bad state, a system file that does not match what the update expects, or a driver that conflicts with the new files — and gives up. Windows records the update as failed and, the next time you check, offers it to you again as if nothing happened.
That is why this error is so stubborn. A plain retry rarely helps, because the retry walks into the same obstacle: the same broken cache files, the same stuck queue entry, the same outdated printer driver. Until you remove the obstacle, the installer fails the same way every time. The good news is that the obstacle is almost always one of a short list of usual suspects, and the fixes below work through them in order, from the easiest to the most thorough.
It also helps to know what this error is not. It does not mean your files are at risk, and it does not mean the update itself is broken for everyone. If the same update installs fine on other PCs, the package is fine — something on this PC is getting in the installer's way. Finding and removing that blockage is the whole job.
Common causes
- Corrupted update cache files: a download interrupted by a dropped connection, a sleep, or a restart leaves partial or damaged files that the installer cannot use.
- A stuck BITS transfer job: the Background Intelligent Transfer Service moves update files in the background, and a job wedged in its queue can poison every retry of the same update.
- Damaged system files or component store: if the files the update needs to replace are already corrupted, the installer cannot complete its work and rolls the update back as failed.
- Outdated or conflicting printer drivers: old printer drivers are a repeatedly reported trigger for 0x8024200B, especially during feature upgrades, because the installer cannot migrate them.
- Temporary files and low disk space: a cluttered temp folder or a nearly full system drive can starve the installer of the working room it needs to unpack and stage the update.
How to fix error 0x8024200B — step by step
Work through these fixes in order. Most people clear this error by step 4.
- Restart the PC and retry the update. Restart your computer so a pending reboot or a stuck update service stops blocking the install. Open Settings, go to Windows Update, and click Check for updates. A clean restart often clears a one-off installer failure, because the update engine starts fresh instead of resuming a broken install attempt.
- Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters, click Run next to Windows Update, and follow the prompts. Let the tool apply any repairs it finds, restart the PC, and check for updates again.
- Delete temporary files and clear the update cache. Press Win plus S, type Disk Cleanup, select your C drive, and remove Temporary files, Temporary Internet Files, and Delivery Optimization Files. Then open an admin terminal, run
net stop wuauservandnet stop bits, delete everything insideC:\Windows\SoftwareDistribution\Downloadwithout deleting the Download folder itself, and restart the two services withnet start wuauservandnet start bits. - Clear the BITS queue. Open an admin terminal and run
bitsadmin /reset /allusersto clear any jobs stuck in the Background Intelligent Transfer Service queue. A stalled or corrupted transfer job can make the installer fail again and again on the same update, even after the download itself looks complete. - Repair system files with DISM and SFC. Right-click Start and choose Terminal (Admin). Run
DISM.exe /Online /Cleanup-image /Restorehealthand wait for it to finish, then runsfc /scannow. These tools repair the component store and corrupted system files that can make the update installer fail partway through an install. - Reset the Windows Update components. Open an admin terminal and run
net stop wuauserv,net stop cryptSvc,net stop bits, andnet stop msiserver. RenameC:\Windows\SoftwareDistributionto SoftwareDistribution.old andC:\Windows\System32\catroot2to catroot2.old, then restart the four services withnet start wuauserv,net start cryptSvc,net start bits, andnet start msiserverso Windows rebuilds fresh update caches, then check for updates again. - Remove outdated printer drivers and retry. Open Settings, go to Bluetooth and devices, then Printers and scanners, and remove any printer you no longer use. Then open Device Manager, expand Print queues, right-click any old or unknown printer driver, and choose Uninstall device. Outdated printer drivers are a known trigger for 0x8024200B during upgrades, and removing them lets the installer finish cleanly.
Did this fix it? Quick checklist
- The update installs with no 0x8024200B showing in update history
- Settings, then Windows Update shows You are up to date
- The update history lists the update as Successfully installed
- The PC restarts normally with no undoing changes loop afterward
If the error persists after all seven steps, download the update manually from the Microsoft Update Catalog: go to catalog.update.microsoft.com, search for the KB number of the failing update (you can find it in Settings, then Windows Update, then Update history), and install the standalone package for your system type. The manual installer bypasses the usual update pipeline, so a damaged cache or a stuck queue cannot stop it. If even that fails, run a clean boot — open System Configuration, hide all Microsoft services, disable the rest, restart, and try the update with nothing third-party running — because a background program may be the last thing standing between the installer and a clean finish.
Frequently asked questions
What does error 0x8024200B mean?
Error 0x8024200B is Microsoft's WU_E_UH_INSTALLERFAILURE condition: the installer failed to install (uninstall) one or more updates. In plain terms, Windows Update downloaded the update but the installer could not finish installing it, so the update is left failed in your update history and Windows keeps offering it again.
Is error 0x8024200B dangerous for my PC?
No. It blocks only the updates that failed to install; your files, apps, and everything already installed are untouched. The error means an install step failed, not that your system is damaged. It is safe to keep using your PC while you work through the fixes, though you should not ignore the failed update for long, since it may contain security fixes.
Why does the same update keep failing with 0x8024200B?
The failed install leaves broken files, a stuck BITS transfer job, or a conflicting driver behind, so Windows retries the same install and hits the same failure each time. Clear the update cache and the BITS queue, repair system files with DISM and SFC, and remove any outdated printer drivers, then check for updates again with a clean slate.
Can I fix 0x8024200B without using command-line commands?
Often, yes. Restart the PC, run the Windows Update troubleshooter in Settings, delete temporary files with Disk Cleanup, and remove old printers you no longer use. Those steps alone fix it for many people. If the update still fails, the command-line cache and component reset is the next step, and downloading the update manually from the Microsoft Update Catalog is a reliable fallback.