Most Windows 11 update errors come down to a broken download or damaged system files, so the error code matters far less than the order you work in. Restart properly, unplug external drives, make sure the C drive has at least 20 GB free and the clock is set automatically, then run the Windows Update troubleshooter. If it still fails, reset the update components from an administrator Terminal, then run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
Applies to: Windows 11 (23H2, 24H2, 25H2) and Windows 10 (22H2) | Last updated: August 21, 2026
Key Takeaways
- Nearly every Windows 11 update error, including the codes starting with 0x8, comes down to one of two things: a download that got corrupted, or damaged system files underneath. Looking up your specific code sends you to the same fixes.
- Do a restart rather than a shutdown. Updates finish installing during a restart, and Microsoft asks for at least 20 GB of free space on a 64-bit install before an upgrade will go through.
- If you have ever used a tool to pause or block updates, put it back to normal before anything else. Nothing in this guide can work around a policy that is still blocking Windows Update.
- Renaming the DataStore and Download folders inside SoftwareDistribution forces Windows to download a clean copy of the update. Renaming rather than deleting means you can put them back if something goes wrong.
- Run DISM before SFC, never the other way round. SFC repairs your system files from a local copy, and DISM is what repairs that copy. Running SFC first on a damaged source is why people get “found corrupt files but was unable to fix some of them”.
Quick Steps
- Restart the PC properly, and unplug external drives, docks and USB hubs.
- Check Settings > System > Storage for at least 20 GB free on the C drive, and Date & time for Set time automatically being on.
- Set any update-blocking tool or policy back to normal, then check for updates again.
- Run Settings > System > Troubleshoot > Other troubleshooters > Windows Update.
- Open Terminal as administrator and reset the update components with the commands below.
- Run
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow, then restart. - Still failing? Install that one update by hand from the Microsoft Update Catalog, or use Reinstall now under Settings > System > Recovery.
In This Guide
- Why the error code hardly matters — two causes behind almost all of them.
- The quick checks — five things that fix it for most people.
- The built-in troubleshooter — hit and miss, but 30 seconds.
- Reset the update components — the step that fixes most update errors.
- DISM, then SFC — and why that order is not optional.
- Install the update by hand — skip Windows Update entirely.
- The repair install — what I do long before a clean install.
Why the Error Code Hardly Matters
On Windows 11 an update error usually shows up as an update that fails to install, often with a code starting with 0x8. It is tempting to search that exact code and hope for a targeted answer. In practice, nearly all of them trace back to the same two causes: the update file downloaded badly, or a system file underneath is damaged.
Microsoft’s own common Windows Update errors table makes the point better than I can. 0x800f081f is component store corruption, and the fix listed is DISM followed by SFC. 0x8007000D means invalid or corrupted data was downloaded, and the fix is to redownload the update. Different codes, same two answers.
So instead of chasing your code, work through this in order. Each step is cheaper and less disruptive than the one after it, and you stop as soon as the update goes through.
The Quick Checks That Fix It for Most People
Do a proper restart, not a shutdown. Updates finish installing on the restart, and with Fast Startup enabled a shutdown is not the same thing. Start > Power > Restart. Microsoft lists this first in its guide to troubleshooting Windows update problems, because it also clears applications that are holding files open.
Unplug external hardware. External drives, docks and USB hubs genuinely trip up updates, and Microsoft explicitly asks you to remove them before retrying. Leave your keyboard and mouse plugged in, disconnect everything else, and try again.
Check your free space. Open Settings and look at Storage. Microsoft’s requirement is at least 20 GB free for a 64-bit install, and an almost-full C drive is a very common reason for an update that keeps failing at the install stage. If you are short, my guide on how to clean up your C drive covers where the space usually goes.
Check your clock. In your date and time settings, make sure Set time automatically is on. If the clock is wrong, the secure connection to Microsoft’s servers fails, and the update never gets far enough to tell you that is the problem.
Undo anything that blocks updates. If you have ever used a tool to pause or switch off Windows Update, including the Windows Update Policy setting in my own tool Winhance, set it back to normal first. The same applies to registry edits or Group Policy rules you may have applied at some point. Nothing else in this guide will help while an update block is still in place.
Then go back to Settings > Windows Update and check for updates again. For a lot of people, that is where this ends.
Run the Built-In Troubleshooter
Go to Settings > System, scroll down to Troubleshoot, then Other troubleshooters. Windows Update is the first entry under Most frequent. Click Run and let it finish.
What it does is check that the update services are running and clear a stuck download. It is hit and miss, and I will not pretend otherwise. It also takes about 30 seconds, so it is worth doing before you start typing commands. Microsoft documents this path on its Windows Update troubleshooter page, and on current builds it may also point you at an automated troubleshooter inside the Get Help app.
Reset the Update Components by Hand
This is the step that fixes most Windows 11 update errors, and it is doing by hand what the troubleshooter tries to do automatically. Right-click the Start button and choose Terminal (Admin), then accept the UAC prompt.
It has to be administrator. Running these in a normal Terminal window gives you access denied on every command. If you are following another guide and getting “access denied”, this is almost always why.
First, stop the three services involved: the Windows Update service itself, the BITS service that does the downloading, and the cryptographic service that checks the update files are signed.
net stop bits
net stop wuauserv
net stop cryptsvcNow rename the two folders inside SoftwareDistribution where Windows keeps the update files it has downloaded, plus the catroot2 folder that holds the signature information (You can also rename them using file explorer like I show in the video):
ren C:\Windows\SoftwareDistribution\DataStore DataStore.bak
ren C:\Windows\SoftwareDistribution\Download Download.bak
ren C:\Windows\System32\catroot2 catroot2.bakThen start the three services again:
net start bits
net start wuauserv
net start cryptsvcGo back to Settings > Windows Update and check for updates. You should see it start downloading from scratch rather than resuming, which is the whole point. If a download got corrupted halfway through, Windows keeps trying to install that same broken file, and moving the folders out of the way is what forces it to fetch a clean copy.
These are Microsoft’s own documented reset commands, taken from its additional resources for Windows Update page. Note that they rename the two subfolders inside SoftwareDistribution rather than the whole folder. Renaming rather than deleting means the originals are still there if you ever need them back.
If a rename says access denied, one of the services is still running. Run the three stop commands again and check each one reports success before you retry. If a stop command says the service is not started, that is fine, carry on.
Once updates are installing normally again, the three .bak folders are dead weight. You can delete C:\Windows\SoftwareDistribution\DataStore.bak, C:\Windows\SoftwareDistribution\Download.bak and C:\Windows\System32\catroot2.bak, or leave them, they are harmless either way.
DISM First, Then SFC
If the reset did not do it, the problem is probably not the download at all. It is a damaged system file underneath. In the same administrator Terminal window, run DISM first:
DISM /Online /Cleanup-Image /RestoreHealthLet it finish, then run:
sfc /scannowOr chain the commands into a single command:
DISM /Online /Cleanup-Image /RestoreHealth; sfc /scannow; shutdown /r /t 30The order matters and it is not a style preference. SFC repairs your system files from a local copy that Windows keeps. DISM repairs that copy itself, pulling clean files from Windows Update. Run SFC first against a copy that is already damaged and it will tell you it found corrupt files but could not fix them, which is exactly the message people end up searching for.
Microsoft says the same thing plainly on its System File Checker page: you should run DISM prior to running the System File Checker.
DISM will sit at a percentage and look frozen, usually somewhere around 20 percent. It is not stuck. Leave it alone until it reports the restore operation completed successfully, which can take anywhere from five to twenty minutes. Then run SFC, restart, and try the update again. I went through both commands in more detail, including what each result message actually means, in my guide on running DISM and SFC in the correct repair order.
Install the Update by Hand From the Microsoft Update Catalog
If one specific update just will not install while everything else goes through, you can skip Windows Update and install that one yourself.
Open your update history in Settings > Windows Update and find the update that keeps failing. It will be listed with a KB number, something like KB5101650. Copy that number, then go to the Microsoft Update Catalog and search for it.
Pick the row that matches Windows 11 and your version, on x64, and download it. What you get is a standalone installer that you run yourself, which skips the part of Windows Update that was failing. It is the most reliable way past a single stubborn update.
Match the version. The catalog lists updates for several Windows versions and architectures on one results page. Downloading the wrong one wastes your time, because the installer will simply tell you it does not apply to this computer.
The Repair Install, Long Before a Clean Install
This is the last one, and it is the step I would reach for well before wiping the machine. Go to Settings > System > Recovery, and you will find a row called “Fix problems using Windows Update” with a Reinstall now button.
It downloads a repair copy of the Windows version you are already on and reinstalls it over the top. Your files, your apps and your settings stay where they are. Microsoft’s page on reinstalling the current version of Windows confirms it preserves apps, files and settings. It is a repair install, not a reset.
Keep the PC on power and connected to the internet for the whole thing, and expect it to take a while. In most cases this fixes the errors that nothing else will. If you want to know what the more drastic options actually cost you before you consider them, I compare them in how to reinstall Windows without losing data.
When the Update Installs Fine but Breaks Something
That is a different problem, and it has been happening a lot lately. If an update goes in cleanly and then something stops working, the answer is not in this guide. Uninstall that update, then pause updates for a while so it does not immediately come back.
I have covered both sides of that separately: how to uninstall Windows 11 updates walks through removing the one that caused it, and how to pause Windows 11 updates shows how to hold updates until any date you pick, including the part most people miss about keeping the pause going.
Frequently Asked Questions
Do I need to look up my specific Windows update error code?
Usually not. Microsoft’s own error table sends most common codes to the same two remedies: redownload the update, or repair the system files with DISM and SFC. Working through the steps in order gets you there faster than researching the code.
Is it safe to rename the SoftwareDistribution folders?
Yes, as long as you stop the three services first. Windows recreates the folders the moment the services start again, and renaming rather than deleting keeps the originals available. The only thing you lose is the download cache and your local update history list.
Why does DISM look stuck at 20 percent?
It is not stuck. DISM sits at a percentage while it works through the component store, and Microsoft warns that the operation can take several minutes. Do not close the window before it reaches 100 percent, because an interrupted run leaves the component store in a worse state.
Will the repair install delete my files or programs?
No. Reinstall now under Settings > System > Recovery reinstalls the same Windows version over the top and preserves your apps, files and settings. That is what separates it from Reset this PC, which removes your installed programs.
Do these fixes work on Windows 10?
The commands are identical on Windows 10 (22H2), and the troubleshooter and Settings paths are close enough to follow. Bear in mind that Windows 10 reached end of support on 14 October 2025, so unless you are on Extended Security Updates, there is not much left for it to install.
