Reliability Monitor Data
Windows Reliability Monitor stores processed stability records under ProgramData in the RAC PublishedData cache, where the Reliability Analysis Component keeps XML and related published event summaries built from application crashes, Windows failures, updates, and hardware error reports. These files exist so the Reliability Monitor timeline and Stability Index can open quickly without reprocessing raw diagnostic sources every time. Kudu removes the cached PublishedData set so Windows can regenerate fresh reliability data, without touching user files, accounts, passwords, or system settings.
Why clean Reliability Monitor Data?
- Corrupted RAC published XML can make Reliability Monitor open with blank days or incomplete failure entries even though crashes actually occurred
- Stale published summaries after Windows updates or servicing changes can leave the Stability Index frozen on old values, so recent problems never appear in the graph
- An oversized PublishedData cache slows Reliability Monitor while it parses historical records, which shows up as a long delay before the timeline and event list load
- Mismatched cached reliability records can cause duplicate application failure entries, making one crash look like several separate incidents in the daily view
- Broken published data may trigger generic 'failed to load data' behavior in Reliability Monitor, preventing you from reviewing software installs, updates, and hardware errors
- Clearing outdated RAC cache forces Windows to rebuild the published timeline from current diagnostics, which often restores missing days, corrected dates, and accurate problem counts
Cache paths Kudu targets
Windows
%ProgramData%/Microsoft/RAC/PublishedData |
Common questions about Reliability Monitor Data
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.