Apps

Chocolatey Logs

Chocolatey writes rolling package-management logs under %ProgramData%\chocolatey\logs while it resolves package metadata, downloads nupkg files, runs install and uninstall scripts, and records PowerShell and NuGet output. These plain-text log files accumulate across every upgrade, failed install, and background maintenance run, often preserving verbose traces, stack traces, and retry details long after they are useful. Kudu removes Chocolatey log files older than one week, while leaving installed packages, backups, configuration, binaries, accounts, and saved credentials untouched.

Why clean Chocolatey Logs?

  • Repeated install and upgrade attempts leave behind large verbose .log files, so the Chocolatey logs folder keeps growing and users notice unexpected disk usage in ProgramData
  • Failed package installs can write long retry loops and stack traces, producing oversized logs that make storage cleanup tools report Chocolatey as using far more space than expected
  • Keeping months of historical logs makes it harder to find the current failure in choco output, so troubleshooting turns into searching through many similarly named old files
  • Old logs often contain command lines, repository URLs, package arguments, and environment details, so removing stale copies reduces leftover diagnostic clutter without affecting installed software
  • On systems with frequent automation runs, every scheduled upgrade appends another set of transcript files, and administrators notice backup jobs and profile scans taking longer because ProgramData contains thousands of old log entries
  • Very large text logs can open slowly in editors and log viewers, so checking a recent package failure feels sluggish until obsolete history is cleared out
What gets cleaned

Cache paths Kudu targets

Windows

%ProgramData%/chocolatey/logs
Frequently asked

Common questions about Chocolatey Logs

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.