Windows Update Fails Repeatedly in History – Fix

You've seen it: the same update fails over and over in Windows Update history.

It's frustrating, but the cause is almost always the same: corrupted update cache files or a component store that's slightly broken. The good news is you don't need to reinstall Windows.

The Fix: Reset the Update Cache Manually

What's actually happening here is that Windows Update downloads the same corrupted package each time because the cache isn't cleared. The system thinks it already has part of the update, then fails when trying to apply it.

1. Press Windows + R, type services.msc, and hit Enter.
2. Find Windows Update in the list. Right-click it and choose Stop.
3. Now open File Explorer and go to C:\Windows\SoftwareDistribution.
4. Delete everything inside that folder. You don't need to delete the folder itself—just the files and subfolders inside. Some files might be locked—skip them for now.
5. Go back to Services, right-click Windows Update again, and choose Start.
6. Open Windows Update and check for updates again.

If step 4 gets stuck because a file is in use, you can boot into Safe Mode and do it there. Or use this command in an elevated Command Prompt to stop the service, delete the folder, and restart the service in one go:

net stop wuauserv
rmdir /s /q C:\Windows\SoftwareDistribution
net start wuauserv

The reason step 3 works is that SoftwareDistribution is where Windows stores all downloaded update files. By deleting them, you force Windows to download the update fresh instead of trying to reuse a broken copy.

Why This Works (The Short Version)

Windows Update doesn't check if the files it already downloaded are intact. It just sees 'already downloaded' and tries to apply them. If one byte is wrong, the whole thing fails. Deleting the cache removes that bad data. Simple.

Less Common Variations That Might Apply

1. Component Store Corruption

Sometimes the problem isn't the update cache but the component store itself. This happens more often on systems that have run many updates or had a failed feature update. Run these two commands in an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

DISM fixes the component store. SFC then checks system files. Always run DISM first—SFC relies on a healthy component store.

2. Stuck Pending Restart

If you see error 0x8024200d, the update is waiting for a reboot that never happened. Go to Settings > Update & Security > Windows Update and click Restart now. If the button is grayed out, check for pending file rename operations with chkdsk /f—that usually triggers the reboot.

3. Third-Party Antivirus Blocking Updates

I've seen Norton and McAfee specifically block update downloads. Temporarily disable real-time protection. If the update goes through, you found the culprit. Don't leave it off—just disable it for the update.

4. Network Issues

Your DNS might be caching a bad response. Flush it:

ipconfig /flushdns
netsh winsock reset

Then restart your PC.

How to Prevent This From Happening Again

There's no magic bullet, but two things help:

• Don't skip updates. The longer you wait between updates, the more likely a component store corruption will happen. Set Windows Update to install automatically, or at least check monthly.
• Keep your system drive healthy. Run chkdsk C: /f every few months. A bad sector on the drive can corrupt update files silently. Windows won't tell you—it just fails updates.

Also, if you're on a slow or metered connection, use the Delivery Optimization settings to limit background downloads. That reduces the chance of partial downloads getting corrupted.

That's it. No registry edits, no third-party tools, no reinstalling Windows. Just clear the cache, fix the component store, and you're done.