Hello Samuel Parker,
This usually occurs because a Windows upgrade disrupts the components that generate the Reliability Monitor data rather than Reliability Monitor itself. The tool depends on the RAC (Reliability Analysis Component) infrastructure, specifically the RacTask scheduled task, WMI providers, and data stored under C:\ProgramData\Microsoft\RAC\, and if these components are disabled, corrupted, or not repopulated after the upgrade, the stability history appears blank or stops updating.
I would first verify that the scheduled tasks under Task Scheduler > Microsoft > Windows > RAC are present and running successfully, and confirm that the Task Scheduler and Windows Management Instrumentation (WMI) services are healthy. Also check whether the folder C:\ProgramData\Microsoft\RAC\PublishedData is being updated and whether Event Viewer is still recording application crashes and system errors, since Reliability Monitor relies on those sources to build its reports.
If Event Viewer continues to log failures but Reliability Monitor remains empty, the RAC database may have been reset or corrupted during the feature upgrade. In that case, rebuilding the WMI repository and allowing the RAC tasks to regenerate data is typically more effective than repairing Reliability Monitor itself. A complete in-place Windows upgrade can also intentionally reset historical stability data, so if only older records are missing but new events begin appearing after several days, that behavior is expected rather than indicative of a fault.
If my answer is useful for you, please hit Accept the answer for me please.
HL.