Windows Update Keeps Failing? Stop Clicking Retry and Do This Instead

Windows Update failed. Again.

So Windows gives you one helpful option: Retry. You click it. It downloads the same update, tries the same installation, fails at the same point, and shows you the same error.

So naturally, it offers you Retry again. Because apparently the operating system’s entire troubleshooting strategy is “maybe this time.”

Prefer to watch instead of read? Here’s the full walkthrough — or skip it and keep reading below.

A Real Example: Plenty of Disk Space, Update Still Fails

Here’s why guessing doesn’t work. In mid-2026, Microsoft confirmed a problem with the May security update for Windows 11 (KB5089549). On some computers, it would restart, reach about 35–36%, fail, roll everything back, and show error 0x800f0922.

The cause turned out to be a nearly full EFI System Partition — a small, hidden partition Windows uses to start the computer. Some machines had about 10 MB free on it. You could have hundreds of gigabytes free on your C: drive and still hit this, because it’s a completely different partition.

Microsoft fixed that specific issue in a later update. But the lesson sticks: the same “update failed” message can have completely different causes, and only the details tell you which one you’ve got.

When Retrying Actually Makes Sense

Retrying once is reasonable. Your internet connection may have dropped, Microsoft’s servers may have hiccuped, or the download may have been interrupted.

So restart the computer and try one more time. If it fails again at roughly the same percentage with the same error code, stop. Nothing has changed — same servicing system, same system files, same partitions, and thanks to caching, often the same downloaded update package. You’re just telling Windows to go fail again, but this time really believe in itself.

Step 1: Find the KB Number and the Error Code

Go to Start → Settings → Windows Update → Update history. Under Quality updates, find the one that failed and write down two things:

• The KB number (for example, KB5089549)
• The error code (for example, 0x800f0922)

Search for those — not “Windows Update failed.” That’s about as useful as telling a mechanic “it broke.”

Then check Microsoft’s Windows release health page for your version of Windows. It’ll tell you whether this is a known, widespread problem or something specific to your machine.

And check the dates on any advice you find. A seven-year-old Windows 10 forum post telling you to delete three folders, disable four services, and edit the registry may have nothing to do with your computer. Make sure the advice matches your problem before you start performing surgery with a shovel.

Step 2: Rule Out the Simple Stuff

Restart — don’t Shut Down. They aren’t always the same thing. With Fast Startup enabled, a normal shutdown can preserve part of the previous system state. A full Restart gives Windows Update and its services a genuinely clean start.

Check your free space. For a cumulative update, aim for at least 20–30 GB free on C:. Updates need working space during installation, not just room for the download.

Unplug extras. External drives, memory cards, and USB docks can interfere with an update or its restart. Keep the keyboard and mouse — we’re troubleshooting Windows, not convincing the computer it’s been abandoned.

Check your antivirus vendor’s support page if you use third-party security software, in case there’s a known conflict with the update. Don’t just uninstall it because someone in a forum wrote “worked for me.”

Then restart and try the update again.

Step 3: Run the Windows Update Troubleshooter

Go to Start → Settings → System → Troubleshoot → Other troubleshooters and run the Windows Update troubleshooter.

It isn’t especially powerful, but it can catch stuck services, wrong settings, and some damaged update components. Let it finish, restart, and try again.

Step 4: Repair the Windows Component Store (DISM + SFC)

Windows Update depends on the component store — think of it as the warehouse where Windows keeps its system components and replacement files. If that warehouse is damaged, an update can download perfectly and still fail during installation. Error 0x80073712 is a common sign.

Right-click Start, open Terminal (Admin), and run:

DISM /Online /Cleanup-Image /RestoreHealth

Let it finish. It will sit at one percentage long enough to make you wonder if the computer quietly resigned. Don’t close the window. When it completes, run:

sfc /scannow

DISM repairs the underlying Windows image; System File Checker then uses it to repair the system files you’re actually running. (More on why the order matters: Why SFC /Scannow Never Works (Until Now).)

Restart and try the update again.

Don’t Start Deleting Random Windows Folders

This is where online advice gets dangerous. You’ll see people telling you to delete SoftwareDistribution, delete Catroot2, clear every temp file in sight, edit the registry, or — just for fun — resize the EFI partition.

Those folders do matter. SoftwareDistribution holds Windows Update’s download cache and working files, and resetting it can help when a download is corrupt or stuck. But there’s a right way: stop the related services, then rename the folder instead of deleting it. That way the old contents still exist if something goes sideways.

Same goes for Catroot2. And make absolutely sure it’s catroot2 — not catroot. Those are different folders. Deleting the wrong system folder because a guide used bold text is still deleting the wrong system folder.

Step 5: Reset the Windows Update Components (the Safe Way)

Only if the steps above didn’t work. Open Terminal (Admin) and stop the update services:

net stop wuauserv
net stop bits
net stop cryptsvc

Rename the cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Start the services again:

net start cryptsvc
net start bits
net start wuauserv

Restart the computer. Windows automatically rebuilds fresh copies of both folders. Try the update again — and once everything’s updating normally, you can delete the .old folders.

Step 6: Install the Update Manually

If Windows Update itself keeps failing, search for your KB number in the official Microsoft Update Catalog. Download the package that matches your Windows version — most current home PCs are x64. (If you’re still running 32-bit Windows, congratulations. Say hi to your pet T-Rex.)

Never download Windows updates from random file sites or “driver” pages. If a site has six fake Download buttons and one real one, close it. The Update Catalog isn’t pretty, but it’s official — and pretty isn’t what we’re asking from Windows Update right now.

• If the standalone package installs: the problem was Windows Update’s download or detection process.
• If it fails with the same error: the underlying servicing system is the problem. Downloading the same update from five websites won’t fix that.

About Error 0x800f0922 and the EFI Partition

Back to that error code. Do not assign the hidden EFI partition a drive letter and start deleting things. It holds your boot files. Delete the wrong one, and your problem goes from “Windows Update won’t install” to Windows won’t boot.

1. First, make sure you’ve installed (or at least tried) the latest cumulative update — Microsoft already shipped a fix for the specific May 2026 issue.
2. If the newest update still fails with 0x800f0922, confirm the cause before touching anything. Open the servicing log at C:\Windows\Logs\CBS\CBS.log and look for entries like SpaceCheck: Insufficient free space and ServicingBootFiles failed.

That’s your evidence. The error code alone doesn’t prove the EFI partition is full — the same code can show up for other partition and servicing problems. If you aren’t comfortable working with boot partitions, get help from someone who is. A hidden boot partition is not the place for trial and error.

Last Resort: An In-Place Repair Install

If the troubleshooter, DISM, SFC, the component reset, and the standalone package have all failed, stop stacking random fixes. The next reasonable step is an in-place repair install:

1. Download the current Windows 11 installation media directly from Microsoft.
2. Launch Setup from inside Windows.
3. Choose the option to keep your personal files and apps.

That reinstalls the Windows system components while keeping your programs, settings, and data — far less destructive than Reset This PC or a clean install.

But back up your important files first. A repair install is designed to keep your files; that doesn’t make it a backup. The worst time to discover your documents only existed in one place is halfway through repairing that place.

The Short Version

1. Write down the exact KB number and error code.
2. Restart (not Shut Down), check free space, and unplug extra devices.
3. Check Microsoft’s release health page for known problems.
4. Run the Windows Update troubleshooter.
5. Run DISM, then System File Checker.
6. Reset the Windows Update components — rename, don’t delete.
7. Try the standalone package from the Microsoft Update Catalog.
8. If Windows servicing itself is broken, back up and do an in-place repair install.

A failed update doesn’t mean your computer is broken. It means something the installer needed wasn’t in the condition it expected. The error code tells you where to look — the Retry button doesn’t.

And remember my friends… stay grumpy.