Windows Update Keeps Re-downloading Fix the Download Cache the Safe Way
The same update downloads, fails, and downloads again — sometimes for weeks — while its cache folder quietly grows into gigabytes. The download cache is corrupt, and Windows will keep tripping over the same broken files until the cache is reset. Here is the safe reset that technicians actually use.
✍️ Technical Anshu🪟 Windows 11⏱️ 7 minute fix
🎥 Watch the full process in the video — update cache cleanup inside the complete after-update routine
Windows Update downloads everything into C:\Windows\SoftwareDistribution\Download before installing it. If that download is interrupted or a file is damaged, Update does not always notice — it retries the same broken package, or re-downloads the whole thing again. The fix is to stop the update services, set the old cache aside, and let Windows build a fresh one. Done this way, nothing installed is removed — only the download staging area is rebuilt.
Administrator Command Prompt — the cache reset, example session
C:\Windows\System32> net stop wuauserv
The Windows Update service was stopped successfully.
C:\Windows\System32> net stop bits
The Background Intelligent Transfer Service was stopped successfully.
C:\Windows\System32> ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
C:\Windows\System32> net start wuauserv
C:\Windows\System32> net start bits
Four commands do the whole reset. The folder is renamed, never deleted — your rollback stays in place until the new cache proves itself.
Example command session. Exact wording of service messages varies slightly by build.
1
The Symptoms of a Corrupt Download Cache
The same update appears, downloads to 100 percent, fails, and starts again on the next check
An update sits at a fixed percentage or cycles between downloading and installing for days
C:\Windows\SoftwareDistribution\Download has grown to several GB — far beyond one update worth of files
Free space on C: keeps dropping even though no update ever completes
If instead your whole drive filled overnight and System files show hundreds of GB, check the CapabilityAccessManager bug first — that is a different fire
2
Why the Cache Breaks and Why Retrying Never Heals It
A cumulative update is a large package, and its download can be cut by a shutdown, a sleep, a lost connection or a full disk. Windows keeps the partial result and the installer's repair attempts often re-validate the same damaged pieces. Restarting the PC does not clear it, because the cache is designed to survive restarts. That design is good for resuming downloads — and bad at forgiving a package that is damaged in a way the checker misses. The reset gives Update an empty desk to work on.
3
The Safe Reset — Stop, Rename, Restart
Open Command Prompt or Terminal as administrator
Stop the two services that use the cache: net stop wuauserv and then net stop bits
Rename the cache folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old — renaming, not deleting, keeps a way back
Start the services again: net start wuauserv and net start bits
Open Settings → Windows Update → Check for updates. Windows creates a fresh SoftwareDistribution folder and downloads clean copies
If a service reports it was not started, it was simply idle — the start commands and the update check wake everything needed
4
What You Honestly Lose — and What You Do Not
Not lost: every update already installed stays installed. The reset touches the download staging area, not the installed updates themselves
Reset: the "View update history" list may appear empty afterwards, because that view is fed from the old folder's records. The updates are still on the system — only the diary page is new
Expected: the next update check takes longer and downloads full packages again. That is the point of a fresh cache, not a new problem
Keep SoftwareDistribution.old for a few days. Once updates install cleanly, delete it through File Explorer to reclaim its space for good
5
If the Same Update Still Fails After a Fresh Cache
A fresh cache rules out download damage. If the identical update still refuses to install, the problem sits deeper — in the component store or in the update itself.
Run the built-in Windows Update troubleshooter from Settings → System → Troubleshoot
Repair the component store image with DISM /Online /Cleanup-Image /RestoreHealth from an administrator prompt, then try the update again
Check the drive is not nearly full — updates need working room, and a starved disk produces exactly these loops
If the failing item is one specific KB that fails on many machines, waiting for Microsoft to revise it is sometimes the professional answer. Pause updates for a week rather than fighting daily
🔴 Rename first, delete later. The .old cache folder is your undo button. Delete it only after Windows Update has run cleanly on the fresh cache — and never rename the folder while the update services are still running.
🎥 Watch the Complete Video Guide
The update cache reset, live — plus the rest of the after-update cleanup, in the video.
Yes — it is the standard technician reset. Stopping the Windows Update and BITS services, renaming C:\Windows\SoftwareDistribution, and restarting the services only clears the download staging area. Installed updates are not removed. The visible side effect is that the update history list can look empty afterwards, because that view reads records from the old folder.
How much space should the update cache normally use?
During an active download it can legitimately hold the size of the update being fetched — a few hundred MB to a few GB for a large cumulative or feature update. Once updates finish installing, the Download folder should shrink back to a small size. A folder that stays at several GB for weeks, with the same update re-downloading, is the corrupt-cache pattern.
Windows Update still loops after the reset. What now?
With a fresh cache, download damage is ruled out. Next steps in order: run the Windows Update troubleshooter, repair the component store with DISM /Online /Cleanup-Image /RestoreHealth, make sure the C drive has real free space, and if one specific KB fails everywhere, pause updates for a week — Microsoft occasionally revises a bad update.
This guide is based on the Technical Anshu C drive full after update video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏