System
.NET Usage Logs (32-bit)
Windows stores .NET Usage Logs (32-bit) under the CLR_v4.0_32 runtime to record which 32-bit managed assemblies and native images were loaded, along with timestamps and usage metadata used by the .NET optimization and servicing pipeline. These small per-application log files accumulate as 32-bit .NET apps are launched, updated, moved, or removed, and old entries can linger long after the related program is gone. Kudu removes obsolete usage log files from the 32-bit CLR UsageLogs folder without touching applications, user documents, account data, or runtime settings.
Why clean .NET Usage Logs (32-bit)?
- Entries for uninstalled or relocated 32-bit .NET apps keep accumulating in UsageLogs, so you notice the folder growing even though those programs are no longer on the PC
- Stale assembly and native image usage records can mislead .NET optimization tasks after app updates, which shows up as an unusually slow first launch while the runtime regenerates optimized images
- Corrupted usage log files can interfere with ngen and servicing heuristics, leading to repeated background optimization activity and extra disk churn visible in Task Scheduler or Resource Monitor
- Old usage metadata from previous versions leaves behind references to assemblies that no longer exist, so startup diagnostics may mention missing paths even though the app itself was already replaced
- Systems with many retired 32-bit .NET utilities collect thousands of tiny log files, which creates needless filesystem clutter and makes profile backups or scans take longer than expected
- The logs are only runtime usage history, not application data, so cleaning them reclaims space and resets stale optimization hints without deleting saved work, settings, passwords, or accounts
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/Microsoft/CLR_v4.0_32/UsageLogs |
Frequently asked
Common questions about .NET Usage Logs (32-bit)
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.