Windows Package Manager Logs
Winget and the Microsoft App Installer package write diagnostic text logs and trace output into DiagOutputDir while resolving package sources, downloading installers, validating manifests, and running install, upgrade, import, and uninstall operations. These logs accumulate across repeated package actions and failed attempts, often leaving behind old session traces that are no longer useful once troubleshooting is finished. Kudu removes App Installer and Windows Package Manager diagnostic log files older than seven days, without touching installed apps, package sources, user settings, accounts, or credentials.
Why clean Windows Package Manager Logs?
- Repeated winget install and upgrade sessions leave behind verbose diagnostic logs, so the folder grows steadily and users notice LocalAppData consuming more disk space than expected
- Failed downloads, hash mismatches, and manifest parsing errors can generate multiple trace files for a single command, leaving a cluttered DiagOutputDir that makes current problems harder to spot
- Old App Installer logs preserve outdated error context from previous source or network issues, so when users open the folder for support they often chase the wrong failure details
- Verbose logging during scripted winget automation can create hundreds of timestamped files, and users notice slower manual log review and more time spent finding the latest run
- Historic traces from packages that were already fixed or removed provide little troubleshooting value after a few days, yet they continue occupying SSD space with no effect on installed software
- Keeping only recent logs reduces noise when diagnosing a fresh winget problem, so users are less likely to confuse an old installer failure with the command that just ran
Cache paths Kudu targets
Windows
%LocalAppData%/Packages/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe/LocalState/DiagOutputDir |
Common questions about Windows Package Manager Logs
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.