Scoop Cache
Scoop keeps a download cache in ~/scoop/cache containing installer archives, portable app ZIPs, MSI and EXE packages, checksum-sidecar files, and partially downloaded temporary files so repeated installs and updates do not fetch the same payload again. Those cached downloads can become outdated, truncated, or no longer match the current manifest hash after a bucket update, which leads to checksum failures and repeated retry loops during install or update. Kudu removes Scoop’s cached installer files and incomplete downloads without touching installed apps, user data, bucket configuration, or account details.
Why clean Scoop Cache?
- A bucket manifest update changes the expected SHA256, but an older cached ZIP or EXE is still reused, causing "hash check failed" errors during scoop install or scoop update
- Interrupted downloads leave partial archives in the cache, and Scoop may repeatedly hit extraction failures or report a corrupt package on the next install attempt
- Large portable app packages and old installer revisions accumulate in ~/scoop/cache, filling the system drive until you notice low disk space warnings or failed updates
- An upstream vendor replaces a file at the same URL, and the stale cached copy no longer matches what Scoop expects, so installs keep failing until the old payload is removed
- Cache entries for apps you already upgraded are no longer needed, yet they continue consuming gigabytes of space with no visible benefit except slower manual cleanup later
- Repeated retries against a bad cached installer can make it look like the network or bucket is broken, when the real symptom is that Scoop instantly reuses the same invalid local file instead of downloading a fresh one
Cache paths Kudu targets
Windows
~/scoop/cache |
Common questions about Scoop Cache
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.