A Windows 11 update that hangs at a percentage, fails repeatedly, or refuses to install at all is one of the most common Windows complaints there is, and September 2026 has been a particularly bad month for it — Microsoft’s own KB5124008 update patched roughly 974 vulnerabilities, the largest single-month total on record, and larger updates statistically stall and fail more often than routine ones. Here’s what actually causes a stuck update and the fixes that resolve it, in the order worth trying them.
Why This Keeps Happening
A stuck or failed update almost always traces back to one of five things: a corrupted Windows Update cache left over from a previous failed attempt, not enough free space on the drive or the small EFI/System Reserved partition Windows uses during installation, corrupted system files that the update process can’t safely patch, a driver or BIOS setting that conflicts with what the update is trying to change, or — less commonly — a Windows 11 build old enough that it’s reached the end of its servicing window and can no longer update normally. Knowing which of these you’re dealing with saves you from trying fixes aimed at the wrong cause.
Rule Out the Obvious First
Before touching anything technical, give it time. Large cumulative updates can sit at the same percentage for genuinely long stretches — two to three hours isn’t unusual for a big one — and interrupting that process by force-restarting is far more likely to cause a real problem than the wait itself. While you’re waiting, check your free disk space: Windows needs meaningfully more than the update’s final installed size to complete it, since it stages files temporarily before replacing the old ones, and running low mid-installation is one of the most common causes of a hard failure rather than just a slow one.
Run the Windows Update Troubleshooter
Go to Settings > System > Troubleshoot > Other troubleshooters, find Windows Update, and run it. It’s a genuinely useful first automated step — it checks for the update service being stopped, corrupted update components, and a handful of other known configuration issues, and fixes several of them without any manual intervention. Restart afterward and check for updates again before moving to anything more involved.
Clear the Update Cache Manually
If the troubleshooter doesn’t resolve it, the update cache itself is the next most likely culprit. Stop the Windows Update, Background Intelligent Transfer, and Cryptographic services (wuauserv, bits, and cryptsvc — either through Services.msc or net stop commands in an elevated Command Prompt), then rename or delete the contents of C:WindowsSoftwareDistributionDownload and C:WindowsSystem32catroot2. Restart those three services and try the update again. This forces Windows to re-download the update fresh rather than resuming a corrupted partial download, and it resolves a large share of stuck-download cases specifically.
Repair System Files
If the update fails outright rather than just stalling, corrupted system files are a strong possibility. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt first — this repairs the underlying Windows image using Windows Update itself as a source — followed by sfc /scannow, which checks and repairs individual protected system files against that now-repaired image. Running SFC before DISM is a common mistake; SFC can’t fix files properly if the image it’s referencing is also damaged, so the order matters.
Install the Update Manually
If the automatic path keeps failing after the steps above, download the specific update directly from the Microsoft Update Catalog using its KB number (for example, KB5124008) and install it as a standalone package. This bypasses whatever is going wrong in the normal Windows Update pipeline and installs the same update through a different mechanism, which resolves cases where the issue is specific to the automatic delivery process rather than the update content itself.
When to Consider an In-Place Repair
If none of the above works and updates have been failing for more than one cycle, an in-place repair install — using the Windows 11 Installation Assistant or Media Creation Tool to reinstall Windows over itself while keeping your files, apps, and settings — resolves deeper corruption that targeted fixes can’t reach. It takes longer than the other steps, but it’s a genuine reset of the update mechanism without the data loss of a clean install, and it’s worth trying before assuming a full wipe is necessary.
What Not to Do
Don’t force a shutdown while the “Working on updates, don’t turn off your computer” screen is showing — interrupting that specific phase, as opposed to a stalled download beforehand, has a real chance of corrupting the installation in a way that’s harder to recover from than the original stuck update. Don’t mass-delete files in System32 based on generic online advice either; the cache-clearing steps above target specific, safe-to-remove folders, not system files in general. And don’t assume every stuck update means your PC is broken — a single failed attempt followed by a successful retry after a cache clear is the normal outcome, not the exception.
Related
If you’re specifically on the September 2026 update, see our breakdown of what KB5124008 changes and our list of its known issues and fixes to check whether your symptom is already a documented bug rather than an installation failure.
FAQ
How long should I wait before assuming a Windows update is actually stuck?
Give a large cumulative update two to three hours at the same percentage before intervening. Force-restarting too early is more likely to cause a real problem than a slow install is.
Will clearing the SoftwareDistribution folder delete my files?
No. It only removes cached update files that Windows re-downloads automatically. It does not touch your personal files, apps, or settings.
Should I run SFC or DISM first when repairing system files?
Run DISM /Online /Cleanup-Image /RestoreHealth first, then sfc /scannow. SFC checks files against the Windows image, so if that image is damaged, DISM needs to repair it first for SFC to work properly.
Is an in-place repair install the same as a clean install?
No. An in-place repair reinstalls Windows over itself while keeping your files, apps, and settings. A clean install wipes the drive. Try the repair option first since it resolves the same underlying corruption without the data loss.