Electron Runtime Cache
Electron-based apps on Windows often download and keep Electron runtime ZIP archives and extracted runtime distributions under the shared Electron cache in LocalAppData so they can launch, install, or update without fetching the same binaries again. That cache can accumulate versioned runtime packages, partial downloads, and stale extracted files from older app builds or interrupted updates, consuming significant disk space and sometimes confusing bootstrap installers that expect a clean runtime state. Kudu removes these cached Electron runtime archives and extracted runtime files without touching the apps themselves, your accounts, saved projects, settings, or passwords.
Why clean Electron Runtime Cache?
- Interrupted runtime downloads leave partial Electron archives behind, and the next app update may fail with repeated download loops or checksum errors
- Old extracted Electron distributions pile up across app versions, causing unexpectedly large LocalAppData usage even after the apps themselves were updated
- A stale shared runtime cache can make Electron app installers reuse the wrong runtime build, showing launch failures or immediate crashes after an update
- Corrupted cached runtime files can trigger bootstrap errors such as missing DLL messages, white startup windows, or apps that close right after opening
- When the cache contains multiple obsolete Electron versions, repair installs and first launches can take longer while the updater scans and retries bad runtime folders
- Cleaning forces a fresh runtime download, which often fixes apps stuck on 'preparing' or 'installing' because the cached Electron package no longer matches the current release metadata
Cache paths Kudu targets
Windows
%LocalAppData%/electron/Cache |
Common questions about Electron Runtime 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.