You can identify your Windows version in under ten seconds by opening Settings > System > About, or by pressing Windows key + R, typing winver, and pressing Enter; the second method shows the version number, edition, and build in a single dialog. Either route works on Windows 10 and Windows 11, the two versions Microsoft currently supports for most consumer hardware. The harder question is not finding the label but interpreting it, because the marketing name, the version number, the build number, and the edition each answer a different question.
What the four identifiers actually measure
Every Windows installation carries four separate identity fields, and conflating them is the root of most confusion. The product name (Windows 11 Home, Windows 10 Pro) tells you which feature set and licensing tier you own. The version number (such as 23H2 or 24H2) marks the annual feature-update release train. The build number (for example 22631 or 26100) is the exact compiled codebase, incrementing with every cumulative and security patch. The edition determines which capabilities are unlocked, from BitLocker encryption to Group Policy. Windows 11 24H2, for instance, ships on build 26100, while the final Windows 10 release, 22H2, sits on build 19045.
The reason these fields diverge is Microsoft's servicing model. Feature updates arrive roughly once a year and reset the version label. Monthly quality updates change only the build's revision suffix, not the version. Editions are licensed independently of both, so a machine can stay on the same build for years while its edition never changes. The winver dialog stitches all of this together because Microsoft knows support decisions depend on the combination, not any single field. Two PCs on identical builds can receive different features if their editions differ.
How Windows stamps and reports its identity
The build number is the authoritative fingerprint because Microsoft's update servers key eligibility to it. When Windows Update contacts Microsoft, the machine transmits its build and revision, and the server returns only patches approved for that exact codebase. This is why a machine one build behind can miss a security fix that a neighbor receives. The registry stores the same data under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion, in values named CurrentBuild, UBR (update build revision), DisplayVersion, and ProductName. The UBR is the piece winver leaves out on some screens, yet it distinguishes two machines that share a base build.
The mechanism matters because version strings are occasionally cosmetic. Microsoft has shipped builds whose DisplayVersion lagged the actual feature content, and preview builds carry labels like "Insider Preview" that will never match a retail string. Checking the registry directly surfaces the raw values. Running the command systeminfo in a terminal prints the full version, build, and installation date in one block. A plain-language way to think about it: the product name is the car model, the build is the serial number, and the edition is the trim package.
Quantified context: release cadence and support clocks
Support windows differ sharply by version, and the numbers explain why Microsoft pushes upgrades. Windows 10 reached end of support on October 14, 2025, after roughly a decade of servicing. Windows 11 releases 23H2 and 24H2 each carry 24 months of support on Home and Pro, and 36 months on Enterprise and Education. The final Windows 10 build, 19045, stopped receiving security patches on that October date. Windows 11 24H2 arrived in late 2024 on build 26100 and remains the current baseline through its support term.
| Release | Version label | Representative build | Support length (Home/Pro) | Status note |
|---|---|---|---|---|
| Windows 10 | 22H2 | 19045 | Ended Oct 14, 2025 | No new security patches |
| Windows 11 | 23H2 | 22631 | 24 months | Nearing or past end of support |
| Windows 11 | 24H2 | 26100 | 24 months | Current baseline |
| Windows 11 | 25H2 | 26200-family | 24 months | Newer feature train |
| Windows Server | varies | distinct builds | Longer, edition-based | Not a consumer edition |
The support clock is the practical stake. A machine reporting build 19045 in 2025 is not merely "old"; it stopped receiving the patches that close known vulnerabilities. Build numbers above 22000 indicate Windows 11, while builds in the 19000s indicate Windows 10, a rough but reliable split. Knowing which band you fall into tells you whether updates are still arriving at all.
Timeline: how a single install changes over its life
| Stage | What changes | What you would see |
|---|---|---|
| Clean install | Base build set | winver shows new version, low UBR |
| Monthly patch | UBR increments | Build suffix climbs, version unchanged |
| Feature update | Version and build reset | New label such as 24H2, higher base build |
| Edition upgrade | ProductName changes | Pro features unlock, build untouched |
| End of support | Patches stop | Build frozen, no further UBR growth |
| In-place repair | Build may reset | Version preserved, UBR can drop |
Edge cases that trip up version checks
Several situations produce misleading readings. A machine managed by an organization may run Windows 11 Enterprise on a build the public never sees, because the organization controls its own update ring. Virtual machines and Windows Sandbox instances report the host's build but often run a stripped edition. Windows on ARM devices carry the same version labels as x64 machines yet use a different processor architecture, visible only in System Information. Insider Preview builds show labels that will never appear on retail hardware, and their build numbers can run ahead of the stable channel. A refurbished PC may show a valid product name while its license is unactivated, which Settings flags separately from the version.
One counterintuitive detail: the edition string can outlive the hardware it was sold with. Retail Windows licenses transfer between machines, but OEM licenses are tied to the original device. A version check that returns "Windows 11 Pro" says nothing about whether that license is genuine or transferable. Microsoft's activation status, shown on the same About page, is the field that settles licensing questions.
Misconceptions worth correcting
The most common error is treating "Windows 11" as a single fixed thing. In reality it is a rolling family whose member builds differ in security posture and feature availability. A second misconception is that a higher number always means newer; preview builds can carry numbers above retail while lacking finalized features. A third is assuming the version number equals the feature update name, when the two are related but separately tracked. People also mistake the edition for the version, then wonder why a "Pro" machine lacks a feature that requires a newer build. Finally, many assume a machine is current because it booted without errors, when a stalled update can leave the build frozen for months without obvious symptoms.
Professional caveat: help-desk staff routinely ask for the build and UBR together, not the version name, because a version label alone cannot distinguish a patched machine from an unpatched one. If you report your version to support, include the full build string with its revision.
A build frozen for months with no UBR growth signals stalled updates. An unactivated license can disable personalization and some updates. "Insider Preview" in the version string means unstable, unsupported code. A version matching a supported release still needs current patches to be safe. Edition mismatches explain missing features better than version numbers do.
Practical steps to check and act
Start with winver for a quick read of version, build, and edition. Open Settings > System > About for the same data plus activation status and processor architecture. Run systeminfo in a terminal when you need installation date and full build in text form. Check the registry values CurrentBuild and UBR when winver truncates the revision. Compare your build against the support table above to judge whether patches still arrive.
For decisions: if your build sits in the 19045 band, Windows 10 support has ended and you should plan an upgrade or accept unpatched risk. If your build lags the current Windows 11 baseline by more than one feature release, run Windows Update and confirm updates complete. If activation reads "not activated," resolve licensing before troubleshooting features. Record your full build and UBR before contacting support so the first reply is useful. These thresholds reconcile cleanly: version tells the release train, build tells patch level, UBR tells the exact patch, and edition tells capability. Use all four together rather than any one alone.
Limits of what a version check can tell you
A version check cannot verify license authenticity beyond the activation flag, cannot detect hardware that will fail a future upgrade's requirements, and cannot confirm that installed updates actually applied if the update cache is corrupt. It also says nothing about driver compatibility or third-party software that may block an upgrade. Build numbers are reissued across channels, so a number alone does not prove a machine is on the stable release. And because Microsoft adjusts support dates and release schedules over time, always confirm the current end-of-support date against Microsoft's official lifecycle pages rather than a cached table. This article is general educational information about reading Windows version data, not a guarantee of support status or upgrade eligibility; for licensing, compliance, or enterprise deployment decisions, consult a qualified IT professional or Microsoft's official documentation.