Microsoft Edge Update Logs
Microsoft Edge’s updater writes rotating diagnostic log files under the system-wide EdgeUpdate Log folder whenever it checks for new versions, downloads packages, verifies signatures, installs updates, or repairs the browser. Those text logs accumulate details such as service startup traces, scheduled task runs, network request results, MSI installer output, and update error codes, but they are not required for Edge itself to run. Kudu removes only settled updater log files that are no longer active, while preserving logs modified in the last day so current update activity, browser data, settings, accounts, and passwords are left alone.
Why clean Microsoft Edge Update Logs?
- Repeated background update checks and failed install retries leave behind old EdgeUpdate and installer logs, so the Log folder keeps growing even though the browser appears to work normally
- Verbose updater traces from download, signature verification, and repair attempts can consume surprising space in ProgramData, which users usually notice only when searching for what is filling the system drive
- After an update problem is already resolved, stale historical logs keep dozens of past error codes and stack traces that no longer help but still clutter diagnostics and backups
- Large piles of settled log files make it harder to spot the current update failure in Event Viewer-style troubleshooting because the newest useful entries are buried among obsolete runs
- Machines that frequently wake, sleep, or reconnect to different networks can generate many updater check logs, leading to constant low-value disk churn and a steadily expanding log directory
- Keeping only recent active logs reduces noise without affecting Edge updates, so users avoid deleting the very files needed for a live troubleshooting session while still reclaiming space
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.