You can find your Windows version in under 30 seconds: press Windows key + R, type winver, and press Enter. The dialog that opens shows your Windows edition (Home, Pro, Enterprise) and a version number plus build number, such as "Version 24H2 (OS Build 26100.2033)." For most people the build number is the real answer, because two machines can both read "Windows 11" yet sit months apart in update status and support eligibility.

That 30-second answer is the easy part. The hard part is understanding what those numbers mean, why Microsoft uses at least four overlapping version schemes, and when the label on your system actually changes what Microsoft will do for you. This explainer goes one level deeper than the Settings screen. It covers the mechanisms behind Windows versioning, the quantified lifecycle context, the edge cases that fool experienced users, and the practical thresholds that determine whether your PC gets security patches next Patch Tuesday.

The four-layer version stack Microsoft actually maintains

Windows exposes four different pieces of version information, and they serve different purposes. The first layer is the marketing name, like Windows 10 or Windows 11. The second layer is the release designation, such as 22H2 or 24H2, where 22 means the calendar year 2022 and H2 means the second half of that year. The third layer is the major build number, like 19045 for Windows 10 22H2 or 26100 for Windows 11 24H2. The fourth layer is the cumulative update revision, usually appended to the build as a decimal or with a KB article number.

The mechanism matters because each layer updates on a different cadence. The marketing name changes roughly every three to six years. The release designation changes once or twice per year for Windows 11, and the major build number changes with it. The cumulative revision changes monthly, sometimes more often for out-of-band patches. When a user asks "which version of Windows do I have," they are usually asking about layers one or two. But when Microsoft asks "are you supported," it is reading layer three. A plain-language way to remember it: the name is the brand, the release is the year, the build is the fingerprint, and the revision is the freshness date.

The reason Windows uses this stacked scheme instead of one clean number is architectural. Since Windows 10, Microsoft moved to a "Windows as a service" model in which the kernel, servicing stack, and feature set are deployed as either enablement packages or full builds on a shared servicing branch. An enablement package is a small download that flips on features already present in the installed build. A full build upgrade replaces core system files. This distinction explains why two Windows 11 machines on the same release can show builds that differ by hundreds of digits: one received an enablement package, the other a full deployment.

Windows 11 adds a wrinkle Windows 10 never had: a hardware compatibility gate. The TPM 2.0 requirement and the supported CPU list mean that a machine can be fully up to date on Windows 10 and still be ineligible for Windows 11. The build number tells you what the OS is doing. The hardware check tells you whether future builds are even an option. Both matter when you are trying to answer which version you have and whether you should keep it.

Quantified context: how long each version lives and what that costs you

Microsoft publishes a lifecycle for every Windows release, and the lifecycle is where the answer to "which version do I have" gains real consequences. For Windows 10, the original release reached end of support on October 14, 2025. That is a hard cutoff: no further security updates for Home, Pro, or Enterprise under standard terms. Extended Security Updates exist for organizations, but they are priced per device and are not a consumer path. For most readers, an unsupported Windows 10 machine in 2025 means monthly patches stopped arriving.

Windows 11 follows a shorter lifecycle. Home and Pro editions receive 24 months of support per release. Enterprise and Education editions receive 36 months. So Windows 11 24H2, released in October 2024, is supported on Home and Pro through roughly October 2026, and on Enterprise and Education through roughly October 2027. The two-year versus three-year split is one of the most misunderstood facts in Windows versioning: identical build numbers on Pro and Enterprise machines will stop receiving updates in different months.

Servicing cadence is monthly, tied to Patch Tuesday, which is the second Tuesday of each month. Out-of-band updates are rare but not zero; Microsoft has shipped emergency patches in the same week as a zero-day disclosure. Cumulative update revision numbers reflect this. A machine that reads "OS Build 26100.2033" is one Patch Tuesday behind "26100.2161," and that gap can matter for a critical vulnerability.

For Windows 10, the practical threshold is that patches stopped in October 2025 unless you upgraded, replaced hardware, or enrolled in a paid program. For Windows 11 Home and Pro, a machine older than about 20 months in its release cycle is closer to the end than most users assume. A machine on 23H2 rather than 24H2 may still be supported, but only until its own two-year window closes. These numbers are the reason the phrase "which version do I have" deserves a precise answer rather than a brand name.

Edge cases: when the obvious answer is wrong

The first edge case is that winver shows the version, but the Settings app shows the release designation in a different format. On Windows 10, Settings > System > About reports the version number with a leading "10.0," such as 10.0.19045. On Windows 11, the same screen reports 10.0.26100. The "10.0" prefix persists across both systems because the kernel version string never changed. A user who reads "10.0" and concludes "Windows 10" has misread a kernel prefix, not the marketing version.

The second edge case is the enablement package illusion. On Windows 10, a machine can receive a small enablement package that bumps the build number from 19044 to 19045 without a full reinstall. On Windows 11, the same mechanism sometimes delivers the new release designation in a single reboot. This means the "about" screen can show a new release while the underlying servicing branch is older than the label suggests. The safest check is the build number, not the release designation.

The third edge case is enterprise and education devices managed by an IT department. A managed machine can be pinned to a specific build via group policy and fall behind the public baseline while still reporting a current-looking release. A device with a valid-looking "Windows 11 24H2" label can be 12 to 18 months behind on patches because the update deferral policy prevents installation. The label is accurate, the freshness is not.

The fourth edge case is the Windows Insider Program. Insider builds carry a build number that belongs to a future release and are not on the standard servicing branch. An insider machine can look like "Windows 11 version 25H2" months before that release reaches the public. It is a legitimate Windows version, but it is not a supported production build and should not be compared to a public release when troubleshooting.

The fifth edge case is the differences between OEM-licensed and retail-licensed machines. OEM Windows installations sometimes carry an edition string with an "OEM" suffix, and the OS may not activate after a hardware change. This does not change the version or build number, but it changes support eligibility and the practical question of whether upgrading is possible.

Red-flag warnings

A build number that has not advanced in more than 35 days on a machine connected to the internet usually means updates are broken, paused, or deferred. "Windows 10.0" on the About screen does not mean Windows 10. It is the kernel version prefix shared by both Windows 10 and 11. A release designation that looks current combined with a build number more than six months old points to a paused update or a policy-pinned device. Insider builds carry build numbers outside the public release sequence and should never be treated as equivalent to a production release.