explained

Checking whether your Windows is still serviced — in 20 seconds

win + winver + one command checks build vs floor; policy rightsizing without ambiguity. The steady script for a question that changes meaning every October.

ProofTune Project··3 min read
Explained illustration Explained

The fast check

terminal / powershell
winver                                          # GUI: edition + build + expiry info when applicable
[System.Environment]::OSVersion.Version        # full version tuple in shell
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').DisplayVersion + ' ' +
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuildNumber

Compare the returned build against Microsoft's lifecycle page — never against folklore like “22H2 is the last” (that was true of Windows 10 only and one lifecycle).

How tooling should surface it

Dashboard-level: edition (from EditionID), build, architecture, plus the vendor's support-matrix verdict against this build — i.e., a rule evaluation, not a string comparison. The scan summary read from ProofTune's readiness card is exactly such a verdict: build, policy revision date, and outcome in one line. If your support question starts with a tool's OS read rather than with a guess about your OS, both sides save the long version.

ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.
ProofTune logo

See these exact settings inside the real tool

The browser replica runs the same strings and states as the installed app — click around before you ever install anything.