How to Configure Windows Server 2016 Reliability Monitor
Reliability Monitor is a built-in diagnostic tool in Windows Server 2016 that presents a chronological stability index and a timeline of system events, software changes, and failures. Unlike Event Viewer, which displays raw event data, Reliability Monitor correlates events over time and assigns a Stability Index score from 1 to 10, where 10 is perfectly stable. This makes it easy to identify at a glance when a server began experiencing problems and to correlate those problems with specific software installations, updates, or hardware errors that occurred around the same time.
This guide explains how to access Reliability Monitor, interpret its data, use it for root-cause analysis, and extract its data programmatically with PowerShell.
Opening Reliability Monitor
Reliability Monitor is not available in Server Manager’s Tools menu by default. Open it by running the following command in a PowerShell or Run dialog:
perfmon /relAlternatively, open Control Panel, navigate to System and Security, then Security and Maintenance, and click View reliability history. The tool may take a few seconds to load while it processes the event history database.
Understanding the Stability Index Chart
The main area of Reliability Monitor shows a chart with dates along the horizontal axis and the Stability Index on the vertical axis. The chart spans up to one year of history by default, and you can switch between the Day view and Week view using the buttons at the top.
Below the chart, a table shows events organized into five rows: Application failures, Windows failures, Miscellaneous failures, Warnings, and Information. Each cell in the table corresponds to a day or week column, and icons indicate what type of events occurred. A red X icon indicates a failure. A yellow exclamation mark indicates a warning. A blue lowercase i indicates an informational event such as a software install or update.
Click any column in the chart to see the detailed events for that period in the lower pane. Click any event in the lower pane to see its full description, the faulting application or module name, and the exception code.
Root-Cause Analysis with Reliability Monitor
The most powerful use of Reliability Monitor is correlating failures with changes. Suppose the Stability Index drops sharply on a particular date. Click that date on the chart and look at what happened across all rows:
If the Information row shows a software installation or update was applied on the same day the failures began, that change is the most likely cause. If an Application failure appears alongside a Windows failure, the application crash may be triggering secondary operating system errors. If failures are consistent with no corresponding changes, look for hardware errors in the Windows failures row, which captures Stop errors (blue screens) and memory dump events.
The View technical details link in the event description opens additional information including the faulting module name and the exception type, which can be searched online for known bugs or fixes.
Step 1: Check for Application Crashes
Application failures in Reliability Monitor correspond to Application Error events (Event ID 1000) in the Application event log. Cross-reference Reliability Monitor’s crash entries with Event Viewer to see the full stack trace and exception details. From PowerShell:
Get-WinEvent -FilterHashtable @{ LogName='Application'; Id=1000 } -MaxEvents 20 | Select-Object TimeCreated, Message | Format-ListStep 2: Check for Windows Failures
Windows failures include Stop errors (blue screens), service crashes, and Windows Error Reporting events. View Stop error events from the System log:
Get-WinEvent -FilterHashtable @{ LogName='System'; Id=6008 } | Select-Object TimeCreated, MessageEvent ID 6008 is logged during startup when the previous shutdown was unexpected. If this event appears repeatedly, the server is crashing or losing power.
Step 3: Review Software Install and Uninstall Events
Informational events in Reliability Monitor that show software installations correspond to entries in the Windows Application log with source MsiInstaller (Event IDs 11707, 11724). Query them:
Get-WinEvent -FilterHashtable @{ LogName='Application'; ProviderName='MsiInstaller'; Id=11707 } | Select-Object TimeCreated, MessageStep 4: Extract Reliability Data with PowerShell
The Reliability Monitor data is stored in the Windows Reliability Analysis Component database. You can query reliability events directly through WMI:
Get-CimInstance -Namespace rootcimv2 -ClassName Win32_ReliabilityStabilityMetrics | Select-Object StartMeasurementDate, EndMeasurementDate, SystemStabilityIndex | Sort-Object StartMeasurementDate -Descending | Select-Object -First 14This returns the daily Stability Index for the last 14 days, which can be incorporated into a monitoring script or dashboard.
Query individual reliability records (failure events):
Get-CimInstance -Namespace rootcimv2 -ClassName Win32_ReliabilityRecords | Where-Object { $_.SourceName -eq 'Application Hang' } | Select-Object TimeGenerated, ProductName, Message | Sort-Object TimeGenerated -DescendingStep 5: Save Reliability History Report
Reliability Monitor can generate an HTML report summarizing the stability history. Click Save a reliability history in the Actions section of the Reliability Monitor window. The report is saved as an HTML file that can be shared with vendors or support teams for offline analysis.
Practical Use Cases
Reliability Monitor is particularly useful after a patch Tuesday or a scheduled maintenance window to confirm that all systems remained stable after updates were applied. It is also the first tool to open when a user reports that an application started crashing recently, since the timeline makes it immediately apparent whether the crash started with a recent update or was already occurring before the reported date.
For chronic instability, export the reliability data over several months and look for patterns — if failures cluster on specific days of the week or around specific scheduled tasks, the correlation reveals the triggering event. Reliability Monitor on Windows Server 2016, used alongside Event Viewer and Performance Monitor, gives administrators a complete picture of server health over time.
