How to Clean Windows ProgramData Package Cache (C:\ProgramData\Package Cache)
Location & Quick Verdict
C:\ProgramData\Package Cache
C:\ProgramData\Package Cache is used by the Windows WiX Burn bootstrapper to store cached .msi and .cab installer baselines for Microsoft Visual C++ Redistributables, .NET runtimes, Visual Studio, and third-party drivers. Over years of updates, dozens of superseded versions accumulate.
How Windows Servicing & Installer Packages Accumulate in Windows ProgramData Package Cache (C:\ProgramData\Package Cache)
Windows Component-Based Servicing (CBS), the Windows Update Agent (wuauserv), and WiX/Burn MSI bootstrapper engines stage compressed cabinet (.cab), express delta (.esd), and superseded side-by-side assemblies inside C:\ProgramData\Package Cache. Windows retains many of these payload packages so you can roll back recent cumulative updates or repair installed Visual C++ / .NET runtimes without internet access.
However, once cumulative updates are superseded by newer monthly rollups—or after MSI applications are uninstalled—gigabytes of orphaned payloads remain behind in C:\ProgramData\Package Cache. Following the verified cleanup procedure for Windows ProgramData Package Cache (C:\ProgramData\Package Cache) reclaims 3.5 GB – 22.0 GB while preserving active servicing manifests and currently registered uninstaller packages.
# Inspect current disk footprint of Windows ProgramData Package Cache (C:\ProgramData\Package Cache) (Read-Only)
$target = "C:\ProgramData\Package Cache"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
Measure-Object -Property Length -Sum |
Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
Manual Cleaning Instructions
- 1 Never select all folders inside C:\ProgramData\Package Cache and hit Delete—active applications rely on their registered GUID folder to run Modify/Repair/Uninstall.
- 2 Open Settings > Apps > Installed Apps first and uninstall any old SDKs or Visual Studio workloads you no longer need.
- 3 To safely clean only orphaned GUID folders whose parent product is already uninstalled, run SWEEPR Cleaner’s verified Package Cache orphan scanner.
Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.
Sub-Folders & Cache Locations Breakdown for Windows ProgramData Package Cache (C:\ProgramData\Package Cache)
Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside Windows ProgramData Package Cache (C:\ProgramData\Package Cache) are safe to purge and which files remain protected:
| Sub-Folder / Cache Location | Storage Role | Typical Footprint | Deletion Safety |
|---|---|---|---|
| C:\ProgramData\Package Cache | Superseded Component Packages & Update Staging Payloads | 3.5 GB – 22.0 GB | ⚠️ Use DISM / SWEEPR Orphan Rule |
| C:\Windows\SoftwareDistribution\Download | Downloaded Windows Update CAB/ESD Installation Packages | 2.0 GB – 16.0 GB | 🟢 100% Safe |
| C:\Windows\WinSxS\Temp\PendingDeletes | Orphaned Servicing Checkpoint Staging Files | 1.0 GB – 9.0 GB | 🟢 100% Safe via DISM |
| Active Windows 11 System32 Binaries & MSI Manifests | Live OS Kernel Files & Active Uninstaller Packages | Protected | 🔒 Protected — Never Touched |
Frequently Asked Questions
Is it safe to delete Windows ProgramData Package Cache (C:\ProgramData\Package Cache)?
Exercise caution: Do NOT blindly delete the entire C:\ProgramData\Package Cache folder in File Explorer—removing active Wix/Burn .msi caches can prevent Visual C++ Redistributables or Visual Studio from repairing or uninstalling.
How much storage space will cleaning Windows ProgramData Package Cache (C:\ProgramData\Package Cache) free up?
Users typically reclaim 3.5 GB – 22.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in C:\ProgramData\Package Cache.
Can I simply press Shift+Delete on Windows ProgramData Package Cache (C:\ProgramData\Package Cache) in File Explorer?
No—do not blindly delete the entire folder. Do NOT blindly delete the entire C:\ProgramData\Package Cache folder in File Explorer—removing active Wix/Burn .msi caches can prevent Visual C++ Redistributables or Visual Studio from repairing or uninstalling.
Where is Windows ProgramData Package Cache (C:\ProgramData\Package Cache) located on Windows 10 and Windows 11?
It is stored at C:\ProgramData\Package Cache. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.
Manual File Explorer vs. 1-Click SWEEPR Cleanup
| Feature | Manual Deletion | SWEEPR Cleaner |
|---|---|---|
| Locked File Handling | Fails on locked processes | Safe background release |
| Accidental Deletion Risk | Moderate (easy to delete wrong folder) | Zero (strict rules & hashes) |
| Safety Undo Rollback | None (Shift+Del is permanent) | 7-Day Automatic Rollback |
| Time Required | 10–20 minutes per app | < 60 seconds across 40+ areas |
Related Windows Cleanup Guides & Hidden Space Hogs
Clean Windows ProgramData Package Cache (C:\ProgramData\Package Cache) Automatically
SWEEPR Cleaner safely clears Windows ProgramData Package Cache (C:\ProgramData\Package Cache) along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.