Apps
Scoop Cache
Downloaded installers and package archives from Scoop are stored under ~/scoop/cache so repeated installs, updates, and bucket operations do not need to fetch the same files again. This cache typically contains versioned ZIP files, EXE and MSI installers, 7z archives, and partial downloads kept after package extraction or failed transfers. Kudu removes these cached installer files so broken or outdated downloads do not keep being reused, without touching installed apps, manifests, buckets, accounts, or settings.
Why clean Scoop Cache?
- A truncated ZIP or EXE left from an interrupted download causes repeated checksum mismatches or extraction errors when you run scoop install or scoop update
- Old installer archives accumulate across package upgrades and leave the cache consuming multiple gigabytes, which shows up as unexpectedly low free space on the system drive
- A cached package file from a superseded manifest can be reused until Scoop fetches it again, leading to install failures that mention hash verification or an invalid archive
- Partially downloaded files in ~/scoop/cache make the same app fail over and over with network or decompression errors because Scoop keeps encountering the bad local copy
- Large cached MSI and 7z installers slow down antivirus scans and file indexing, which users notice as brief pauses when opening the cache folder or running package commands
- Cleaning the cache forces a fresh download of current installer media, which often resolves stubborn update loops where Scoop keeps failing on one package while installed apps themselves remain unchanged
What gets cleaned
Cache paths Kudu targets
Windows
~/scoop/cache |
Frequently asked
Common questions about Scoop Cache
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.