Checking Windows uptime and system stability from the command line combines knowing how long the system has run with reviewing its reliability history. Windows 11 offers commands for uptime and a YYGACOR Login graphical reliability history for stability trends.

The Command

net statistics workstation | find "Statistics since"

What It Does

This shows the “Statistics since” line, reflecting roughly when the current session’s statistics began, which approximates the last boot. Piping `net statistics workstation` to `find` extracts that line. It gives a quick indication of how long the system has been running since it last started, relevant to uptime-related troubleshooting.

When You’d Use This

This is useful for troubleshooting, since knowing how long the system has run and reviewing its stability history helps identify patterns behind recurring problems. The Reliability Monitor in particular is valuable for spotting when issues began, showing a timeline of crashes and events that can reveal whether a recent change, update, or installation coincided with the onset of trouble.

Useful Variations

For precise uptime, subtract the boot time in PowerShell: `(Get-Date) – (Get-CimInstance Win32_OperatingSystem).LastBootUpTime`. For a visual stability history, the Reliability Monitor, opened via `perfmon /rel`, charts system stability and recent problems over time, complementing the raw uptime figure with a record of events.

If It Doesn’t Work

For precise uptime rather than the approximate “Statistics since” line, use the PowerShell calculation subtracting boot time from the current time. If the Reliability Monitor shows little history, the system may be relatively new or the history may have been cleared. Launch it with `perfmon /rel`, and use its timeline to correlate problems with events like updates or installations that appear on the same dates.

Good to Know

The Reliability Monitor, launched with `perfmon /rel`, is particularly useful for spotting patterns, showing a timeline of crashes, warnings, and installations that can reveal when problems began. Uptime alone tells you how long the system has run, while the reliability history gives context on how stably it has been running.

Putting It Together

The command shown may look dense at first, but it breaks down into clear parts once you have used it a few times. As part of keeping Windows healthy and automating upkeep, this command is part of the maintenance routine that resolves problems and prevents them. Combined with the related service and repair commands, it gives you direct control over the background machinery that keeps the system running well. Like anything in the terminal, the real value comes from trying it on your own system and adapting the variations above to what you actually need, so it is worth experimenting with in a safe, low-stakes situation before relying on it in a script or during troubleshooting. Keeping a note of the commands you find most useful, along with the variations that fit your workflow, turns scattered one-off tricks into a personal reference you can draw on whenever a similar task comes up again.