Apps
OneDrive Logs
OneDrive writes rolling diagnostic and installer logs under its per-user logs and setup\logs folders to record sync engine activity, file watcher events, HTTP requests, update attempts, and installer actions. These text-based trace files accumulate as the client retries uploads, reindexes folders, or installs updates, and older logs rarely help normal operation once new sessions have been recorded. Kudu removes OneDrive sync client and setup logs older than seven days, leaving synced files, account data, and OneDrive settings untouched.
Why clean OneDrive Logs?
- Repeated sync retries and connectivity errors can generate large ETL and text log sets, which show up as unexpected disk usage under LocalAppData even though your OneDrive files themselves are not growing
- Failed or looping updater activity keeps appending setup logs, so you may notice the OneDrive installer folder steadily expanding after update prompts or repeated background repair attempts
- Verbose tracing during folder reindexing or mass file changes leaves behind old session logs that are no longer needed, while users only notice that C: space keeps shrinking over time
- When troubleshooting is already complete, keeping months of historical sync traces makes it harder to find current errors and leaves stale diagnostic noise mixed with today’s events
- Endpoint backup, antivirus, and search indexing tools may repeatedly scan thousands of old OneDrive log files, which can show up as extra background disk activity on Windows
- Old setup and sync logs do not improve current file availability or sync state, so cleaning them reclaims space without affecting signed-in accounts, local files, or cloud content
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/Microsoft/OneDrive/logs |
%LocalAppData%/Microsoft/OneDrive/setup/logs |
Frequently asked
Common questions about OneDrive Logs
Related cleaners
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.