Microsoft Edge Update Logs
Microsoft Edge's updater writes rotating Omaha/Google Update-style text logs under ProgramData to record scheduled checks, installer handoffs, service activity, update detection results, and error codes for machine-wide updates. These settled log files accumulate after successful installs, failed retries, and background maintenance runs, but they are not needed for browsing, profiles, saved passwords, or Edge settings. Kudu removes older inactive EdgeUpdate log files while preserving logs modified within the last day so current update activity and troubleshooting data remain available.
Why clean Microsoft Edge Update Logs?
- Repeated scheduled update checks and retry loops leave behind many historical EdgeUpdate log files, and users usually notice the folder growing even though Edge itself seems to be updating normally
- Failed install attempts can generate verbose per-run logs with HRESULTs, command lines, and download status entries, which adds avoidable disk use after the problem has already passed
- Machine-wide updater activity for Stable, Beta, WebView2, and related components can pile up into multiple old log sets, making ProgramData unexpectedly large when inspected in disk analyzers
- Old settled logs make it harder to find the current failure in support cases because recent updater errors are buried among weeks or months of successful background check entries
- Privacy-conscious users may prefer removing historical updater traces because the logs can record timestamps, version numbers, install paths, and service actions even though they do not contain accounts or passwords
- Preserving only logs modified in the last day keeps active troubleshooting intact while clearing stale records from completed update sessions that no longer affect how Edge runs
Cache paths Kudu targets
Windows
%ProgramData%/Microsoft/EdgeUpdate/Log |
Common questions about Microsoft Edge Update 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.