Windows Update Not Working? Fix a Bloated SoftwareDistribution Download Cache

While troubleshooting a Windows computer where Windows Update wasn't working correctly, I found something unusual.

Inside:

C:\Windows\SoftwareDistribution\Download

there were 2,176,966 files.

Yes—over two million files in a directory used by Windows Update.

That raised two questions:

1. Why had so many files accumulated in the Windows Update download cache?
2. Could this be contributing to failed updates, high disk activity or sluggish performance?

An oversized or corrupted update cache can contribute to update failures, storage consumption and disk activity. But the file count alone does not prove that the cache caused the update failure or made the computer slow.

This guide explains how to investigate the folder, reset the Download cache only and verify Windows Update afterwards.

What is the SoftwareDistribution folder?#

Windows uses C:\Windows\SoftwareDistribution to manage parts of the Windows Update process.

Two important subfolders are:

Windows normally manages these directories automatically. Interrupted downloads, repeated update attempts and servicing issues can sometimes leave problematic content behind.

This guide resets the Download cache—not the entire SoftwareDistribution directory. A broader Windows Update reset is a separate, more disruptive troubleshooting operation.

Can millions of files slow down Windows?#

Potentially, yes. The performance impact depends on whether those files are actively being accessed, the drive type, total directory size and available storage.

Disk I/O overhead#

If Windows Update repeatedly enumerates, reads or writes cache files, it can create considerable disk activity. Older HDDs are especially vulnerable to random-access workloads, but SSDs still need time to process millions of filesystem operations.

Antivirus activity#

Microsoft Defender or another antivirus may inspect cache files as they are accessed. Large numbers of operations can increase CPU and disk use.

Low disk space#

The cache may take up substantial storage. If the system drive is nearly full, Windows has less room for updates, temporary files and normal application workloads.

File enumeration and deletion#

Calculating folder properties, listing millions of files or recursively deleting them can be extremely slow.

Important: Windows does not continuously scan every file in this directory. A huge directory can have little effect on day-to-day performance if the files are not being accessed and there is plenty of free space.

Step 1 — Check file count and folder size#

Open File Explorer and navigate to:

C:\Windows\SoftwareDistribution

Right-click Download → Properties.

Windows will calculate:

• Number of files and folders.
• Total size.
• Size on disk.

With millions of files, calculating Properties may itself take a long time.

Why size matters#

Two million tiny files and a few huge update packages can have very different storage footprints. Check both the count and how much space remains on the system drive.

In PowerShell:

Get-Volume -DriveLetter C |
  Select-Object DriveLetter, SizeRemaining, Size

If the C: drive is almost full, storage pressure may be contributing to the problem.

Step 2 — Investigate disk activity#

Press Ctrl + Shift + Esc to open Task Manager.

Select Performance → Disk and look at active time and read/write activity when the computer is slow.

For more detail, press Windows + R and run:

resmon

In Resource Monitor → Disk, inspect which processes and files are actively being accessed.

You may observe:

• svchost.exe hosting Windows Update services.
• Microsoft Defender scanning active files.
• Windows servicing tasks.
• I/O involving paths under SoftwareDistribution.

If disk activity is sustained and associated with update processing, it may explain part of the slowdown. It does not necessarily identify the root cause: a failing drive, update loop or another service may be involved.

Step 3 — Record the Windows Update problem#

Open:

Settings → Windows Update → Update history

Look for:

• Failed KB updates.
• Downloads that never finish.
• Updates that retry repeatedly.
• An error code you can research.
• A pending restart.

Write down the relevant KB number and error code before resetting anything.

Run the Windows Update troubleshooter#

Navigate to:

Settings → System → Troubleshoot → Other troubleshooters → Windows Update

Where available, run the troubleshooter and follow the instructions. On some Windows 11 releases, it launches through the Get Help app.

If updates still fail and cache corruption appears plausible, continue.

Step 4 — Safely reset the Windows Update Download cache#

The aim is to rename the cached download directory, let Windows Update recreate it and check whether the issue is resolved.

Before proceeding:

• Save open work.
• Allow pending Windows updates to finish and restart if Windows requests it.
• Sign in with an administrator account.
• On company-managed devices, check the organisation's WSUS/Intune or update servicing policies.
• If Windows is actively installing updates, do not forcibly stop servicing or rename its working files.

Stop the relevant services#

Open Command Prompt as Administrator and run:

net stop wuauserv
net stop bits

• wuauserv is the Windows Update service.
• BITS is Background Intelligent Transfer Service.

A message saying a service was already stopped is not necessarily a problem.

If Windows reports that a service cannot stop during an active update, stop here and let servicing finish rather than forcing it.

Rename the download cache#

Run:

ren "%SystemRoot%\SoftwareDistribution\Download" Download.old

This renames:

C:\Windows\SoftwareDistribution\Download

to:

C:\Windows\SoftwareDistribution\Download.old

Why rename instead of delete? Renaming is normally much quicker than recursively deleting millions of files, and it lets you verify that Windows Update works with a fresh directory before removing the backup.

Renaming does not free disk space: all the original files remain in Download.old.

If a Download.old folder already exists, don't overwrite or delete it blindly. Choose another clearly labelled backup name after identifying the existing folder.

If the rename reports the folder is in use, confirm no update installation is active and check that the necessary services actually stopped.

Restart the services#

Run:

net start bits
net start wuauserv

Restart Windows, open Settings → Windows Update and select Check for updates.

Windows can create a fresh Download directory as needed and download required update files again.

The first update scan or download after resetting the cache may take longer than usual.

Step 5 — Verify the original update failure is resolved#

Don't stop at “the folder was renamed successfully”. Test the actual problem.

1. Check for Windows updates.
2. Retry the update that previously failed.
3. Wait for download and installation to complete.
4. Restart if requested.
5. Confirm the update appears successfully in Update history.
6. Check whether new errors occur.

You can also inspect whether Windows recreated a Download directory under SoftwareDistribution.

Has the computer become faster?#

Return to Task Manager and Resource Monitor to compare disk activity against your observations from before the reset.

If update processing was repeatedly generating excessive I/O, performance may improve. If the machine is slow due to insufficient RAM, overheating or failing storage, clearing update files won't fix that.

Step 6 — Reclaim space by deleting the old cache#

Only after Windows Update has been verified working correctly should you consider removing the renamed folder.

The old content is here:

C:\Windows\SoftwareDistribution\Download.old

With more than two million files, deletion may take a long time. If the folder is large, ensure you have appropriate backups and that you are using the correct path.

Open Command Prompt as Administrator and, after carefully confirming the exact directory, run:

rmdir /s /q "%SystemRoot%\SoftwareDistribution\Download.old"

Warning: rmdir /s /q permanently removes the specified folder and all contents without asking for confirmation. Confirm that it points to the old, renamed cache directory—not C:\Windows\SoftwareDistribution or the new active Download folder.

Check free disk space afterwards:

Get-Volume -DriveLetter C |
  Select-Object DriveLetter, SizeRemaining, Size

Step 7 — What if Windows Update still doesn't work?#

Cache corruption is only one possible cause. If the original error persists, investigate further instead of deleting the cache repeatedly.

Check the service state#

Run elevated PowerShell:

Get-Service wuauserv, BITS

These services may be stopped when idle. A stopped status alone is not evidence of a problem; investigate whether they can start when needed.

Check servicing health#

Open Command Prompt as Administrator:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM finishes:

sfc /scannow

DISM can repair the Windows component store and SFC checks protected system files. They won't resolve every Windows Update fault.

Generate a Windows Update log#

Run PowerShell:

Get-WindowsUpdateLog

Windows normally generates a readable WindowsUpdate.log file on the desktop from collected traces. Review errors around the time of the failed update.

For deeper servicing diagnostics, inspect:

C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\dism.log

Consider a broader Windows Update reset only if needed#

Microsoft documents more extensive resets involving update metadata and catroot2. Those procedures are more disruptive than clearing the Download directory and may affect the local metadata used to display update history.

Use the official guidance for your Windows version rather than running unknown scripts from the internet.

Why might the cache keep growing?#

If the folder quickly grows abnormally after being reset, check for an unresolved problem such as:

• Repeated update download/install failures.
• A Windows Update retry loop.
• Damaged servicing components.
• Unavailable or unreliable update sources.
• Insufficient free storage.
• Interrupted installations.
• WSUS, Intune or Group Policy configuration issues.
• Filesystem or storage errors.

A cache that repeatedly balloons is a symptom worth investigating, not proof that Windows needs routine cache deletion.

Common questions#

Is it safe to delete files inside SoftwareDistribution?#

The download cache can generally be cleared as part of supported update troubleshooting, with the relevant services stopped and no installation in progress. The broader SoftwareDistribution folder also contains metadata. Avoid indiscriminate deletion.

Does clearing the Download cache uninstall updates?#

No. It does not uninstall Windows updates that have already completed installation, although Windows may need to download outstanding packages again.

Will I lose personal files?#

Ordinary personal documents are not stored in this Windows Update download-cache location. Still, verify the path before any recursive deletion.

Why does deleting millions of files take so long?#

Each deletion involves filesystem work and metadata updates. Deleting millions of small files can take much longer than deleting one file of the same total size.

Is there a “normal” file-count threshold?#

No fixed threshold defines a corrupt Windows Update cache. 2,176,966 files is unusual enough to justify investigation, especially when Windows Update is failing, but the count itself doesn't prove the cause.

Summary#

If Windows Update is broken and SoftwareDistribution\Download contains an excessive number of files:

1. Check the folder's file count and total size.
2. Look for sustained disk activity associated with Windows Update.
3. Record update failures and their error codes.
4. Run the Windows Update troubleshooter.
5. Stop the update services when no installation is in progress.
6. Rename Download to Download.old.
7. Restart services and let Windows rebuild the cache.
8. Verify the originally failing update now installs.
9. Remove the old cache only after successful verification.
10. Investigate repeated abnormal growth if the issue returns.

In the case I encountered, the download cache contained 2,176,966 files. That observation was a strong reason to investigate Windows Update, but confirming whether it caused poor performance would require actual disk and process measurements.

The goal is to identify and fix the underlying failure—not treat cache deletion as normal Windows maintenance.

References#

• Microsoft — Troubleshoot problems updating Windows
• Microsoft — Additional Windows Update troubleshooting resources
• Microsoft — Troubleshoot Windows Update error 0x80070570