How to Fix Windows Updates Failing or Looping
Windows updates stuck in an endless loop or failing repeatedly? Here's how to break the cycle and get your system updated properly.
What's Happening
An update downloads, tries to install, fails or rolls back, and then tries the whole thing again — sometimes on every reboot. Understanding the loop helps you break it: Windows Update works in two phases. It downloads packages into a staging folder, then applies them to the live system during a restart. If a staged file is corrupt, a required servicing component is damaged, or there isn't enough room to apply the change, the install fails and Windows rolls back to keep the machine bootable — but the same broken package is still queued, so it simply tries again. The loop isn't Windows being stubborn; it's Windows repeatedly attempting an install that can't succeed until you remove whatever is blocking it. The fixes below target the three things that block it: bad staged files, damaged servicing components, and conflicts.
Quick Checks (Do These First)
- Don't interrupt a real install. If it says "Installing" or shows a percentage, give it 2–3 hours before assuming it's stuck — large feature updates genuinely take that long.
- Check free space. Updates need 10–20 GB free on the C: drive to stage and apply. Low disk space alone causes endless rollbacks.
- Disconnect extra USB devices. External drives and some peripherals can stall the apply phase.
- Note the exact error code. It's the single most useful clue and decides which fix below applies.
Read the Error Code Before You Touch Anything
The codes aren't random — they roughly group by which part of the loop is broken, and that tells you which fix to run first instead of grinding through all of them:
- 0x80070070, 0x80070008 (space/memory) → it's failing to stage or apply for lack of resources. Free up disk space and remove peripherals first; cache clearing won't help if there's nowhere to put the files.
- 0x8024xxxx codes → the update client/cache is the problem. Go straight to Fix 2 (clear the SoftwareDistribution cache); the troubleshooter (Fix 1) often does this for you.
- 0x800F08xx, 0x80073712 (servicing/CBS) → the component store itself is damaged. Skip cache clearing and go to Fix 3 (DISM then SFC); nothing else will stick until the store is repaired.
- Rollback with no clear code, only after a recent change → suspect a driver or third-party AV conflict (the "If Nothing Worked" section), not corruption.
Clearing the cache for a CBS-corruption code, or running DISM for a simple disk-space failure, just burns an hour. Let the code pick the starting point.
Step-by-Step Fixes
Fix 1: Run the Windows Update Troubleshooter
It resets update components and clears common cache problems automatically — the right first move for the 0x8024 family.
Windows + I> System > Troubleshoot > Other troubleshooters.- Run Windows Update, follow the prompts, restart, retry.
Fix 2: Clear the Windows Update Cache
This forces Windows to discard the corrupt staged packages and re-download clean ones.
Windows + R>services.msc. Right-click Windows Update > Stop.- In File Explorer go to
C:\\Windows\\SoftwareDistributionand delete everything inside it. - Back in services.msc, Start Windows Update again, then retry.
Fix 3: Repair the Component Store with DISM and SFC
This is the fix for the servicing/CBS error family — it rebuilds the store updates are applied into.
- Open Terminal (Admin).
DISM /Online /Cleanup-Image /RestoreHealth(10–20 minutes; needs internet).- Then
sfc /scannow. - Restart and retry the update.
Fix 4: Install the Update Manually
Bypasses a broken update client entirely.
- Note the KB number of the failing update (e.g. KB5034441).
- Search it at the Microsoft Update Catalog.
- Download the build matching your version (Settings > System > About) and run the .msu.
If Nothing Worked
- Driver conflict: outdated graphics or chipset drivers can block feature updates — update them from the manufacturer's site, not just Device Manager.
- Third-party antivirus: temporarily disable it; some products lock files the installer needs.
- System Restore: if the loop started after a change, roll back to before it.
- In-place upgrade: running setup from the Windows Installation Media repairs Windows while keeping files and apps — the strongest software-only fix.
Where DIY Stops — And Why
If DISM can't repair the store and an in-place upgrade still fails or loops, you've reached the wall — and the cause is usually below the operating system, where no update setting reaches:
- A failing drive — bad sectors corrupt update files the instant they're written, so every fresh download stages broken again no matter how many times you clear the cache. Hardware error codes (0x800F081F, 0x80070570) during updates are a classic sign. Confirming this needs a drive health check, and continuing to write to a dying drive risks the rest of your data.
- Unstable RAM — memory faults corrupt files in transit and produce blue screens specifically during the heavy I/O of an update. This needs a memory test to confirm, not more update troubleshooting.
- An unsupported or end-of-life machine — hardware that can't meet a new version's requirements will never complete that update, and deciding repair-vs-replace is a judgement call, not a checklist.
Telling "corrupt files" apart from "the drive writing those files is dying" is the diagnostic step a homeowner has no tools for — and it's the difference between a free fix and losing data to a disk you kept using. If you're local and you've hit hardware error codes or blue screens, that's the point worth handing off.
Need Professional Help?
If you're in the Tampa Bay area and need hands-on assistance, Geeks in Sneaks provides friendly, on-site tech support in Clearwater, Clearwater Beach, and Dunedin.
Related Topics
Need Professional Help?
If you're still having trouble, our expert technicians can help.
Learn about our pc repair serviceMore Windows Problems Fixes
See all Windows Problems fixes →Should I Worry About Windows Event Errors?
Found errors and warnings in Event Viewer and worried something is wrong? Here's the truth about Windows event logs and what you actually need to fix.
How Long Should a Windows PC Last?
Wondering if your PC is getting too old? Here's the realistic lifespan of Windows computers and when it's time to upgrade versus repair.
Why Does My Cursor Freeze Momentarily?
Mouse cursor stuttering or freezing for a second or two randomly? Here's what causes it and how to fix the annoying micro-freezes.
Is It Normal for Disk to Be Slow After Boot?
Computer sluggish for the first few minutes after starting up? Learn why this happens, when it's normal, and how to speed up your post-boot experience.
Is 80°C CPU Temperature Dangerous?
Worried about your CPU hitting 80°C? Here's the truth about CPU temperatures, what's safe, and when you actually need to be concerned.
Why Does My Fan Spin Up Randomly?
Computer fan suddenly revving up for no apparent reason? Here's why it happens, when it's normal, and when you should be concerned.
Are Windows Updates Really Necessary?
Wondering if you can skip those annoying Windows updates? Here's what you need to know about why updates matter and what happens if you ignore them.
Why Is Windows Search Using So Much Disk?
Windows Search Indexer maxing out your disk usage at 100%? Here's why it happens and how to fix it without losing search functionality.