How to Delete Windows Update Cache (and Why It Matters)

Windows quietly stores update files in a hidden folder on your system drive. Most of the time, this is harmless. But over months or years, that cache can grow to several gigabytes — slowing down disk-intensive tasks, causing update errors, or simply eating into storage you'd rather use elsewhere. Clearing it is one of the more reliable fixes when Windows Update gets stuck, fails repeatedly, or shows confusing error codes.

Here's exactly how it works, what you're actually deleting, and what to weigh before you do it.

What Is the Windows Update Cache?

When Windows downloads an update, it stores the installation files in a folder called SoftwareDistribution, located at:

C:WindowsSoftwareDistributionDownload 

This folder acts as a staging area. Once an update installs successfully, those downloaded files should become unnecessary. But Windows doesn't always clean them up automatically — especially if an update failed partway through, was superseded by a newer patch, or if automatic cleanup hasn't run in a while.

The cache can also include files inside:

• C:WindowsSoftwareDistributionDataStore — the update history and database
• C:WindowsTemp — temporary files generated during installation

These are not system files. Deleting them doesn't uninstall updates that are already applied. It only removes the downloaded installer packages.

How to Delete the Windows Update Cache 🗂️

There are two reliable methods. Both require administrator access.

Method 1: Manual Deletion via Services

This is the most thorough approach. You need to stop the Windows Update service before deleting the files — otherwise Windows will lock them and block deletion.

1. Press Win + R, type services.msc, and hit Enter
2. Scroll to Windows Update, right-click it, and select Stop
3. Also stop Background Intelligent Transfer Service (BITS) the same way
4. Open File Explorer and navigate to C:WindowsSoftwareDistributionDownload
5. Select all files (Ctrl + A) and delete them
6. Optionally, clear C:WindowsSoftwareDistributionDataStore as well (this resets your update history display)
7. Go back to Services, restart both Windows Update and BITS

After restarting the services, Windows will rebuild the update database and re-download any pending updates from scratch.

Method 2: Using Disk Cleanup

For a less manual approach, the built-in Disk Cleanup tool handles some of this automatically:

1. Search for Disk Cleanup in the Start menu and open it
2. Select your C: drive and click OK
3. Click Clean up system files (this requires admin rights and rescans)
4. Check Windows Update Cleanup and any other categories you want
5. Click OK and confirm

The Windows Update Cleanup option removes old update packages that have already been superseded — files that were used to install previous versions of components. This is safe to delete and often accounts for the largest chunk of reclaimed space.

Method 3: Command Prompt (For Scripting or Remote Access)

If you prefer the command line or need to automate this on multiple machines:

net stop wuauserv net stop bits rd /s /q C:WindowsSoftwareDistributionDownload net start wuauserv net start bits 

Run this in an elevated Command Prompt (right-click → Run as administrator).

What Changes After You Clear the Cache

One thing worth noting: deleting the cache does not remove installed updates. Your system stays patched. The difference is purely in what files are staged locally for future use.

When This Fix Actually Helps — and When It Doesn't

Clearing the cache tends to resolve:

• Stuck updates that hang at a specific percentage
• Error codes like 0x80070002, 0x80248007, or 0x8024402c
• "Windows Update cannot currently check for updates" messages
• Disk space that seems unaccountably high on your C: drive

It's less likely to help if the underlying issue is a corrupted system file, a network or DNS problem, or a Windows component store issue (which requires DISM /Online /Cleanup-Image /RestoreHealth to address separately).

Factors That Affect Your Results 🔧

Not every machine responds to this the same way:

• Available disk space: If your C: drive is nearly full, re-downloading updates after clearing the cache could create a new problem temporarily
• Windows version: Windows 10 and Windows 11 both use the SoftwareDistribution folder, but the size and content of the cache varies depending on your update history and which feature updates have been staged
• Managed vs. personal devices: On corporate or enterprise machines managed through WSUS or Intune, clearing the local cache may interact with policy-controlled update behavior
• Update deferrals: If you've deferred updates through Settings or Group Policy, clearing the cache doesn't change that schedule — it just removes what was already downloaded

The SoftwareDistribution folder will rebuild itself after you restart the Windows Update service. How large it grows again depends on which updates are pending, your Windows edition, and whether feature updates are queued.

Whether clearing the cache is the right next step — or whether something deeper is causing your update problems — depends on the specific errors you're seeing and how your system is configured.