You can find which Windows version you have by opening Settings > System > About on Windows 11 or Windows 10, or by running the command winver from the Run dialog. The About page shows the edition, version number, and OS build. On Windows 10, the version number is a four-digit year code like 22H2; on Windows 11, it is a two-digit code like 24H2, and the build number differs between the two operating systems.

That answer covers most machines still receiving updates. The rest of this explainer covers why those three fields exist, why the marketing name is the least useful one, and how to read the numbers the way support technicians do.

The three identity layers of a Windows installation

Every Windows install carries three separate identifiers, and conflating them is the root of most version confusion.

The product name is the family label: Windows 10 or Windows 11. It is the coarsest layer and changes only once per major release cycle. Microsoft moved from Windows 10 to Windows 11 in October 2021, and as of the most recent reporting there is no announced successor family.

The version number is the twice-yearly feature update identifier. For Windows 10 it takes the form of a two-digit year plus a release-half code, so 22H2 means the second half of 2022. For Windows 11 Microsoft simplified it to a two-digit year, so 23H2 and 24H2 mark the annual feature update. This layer tells you which feature set the machine received and whether it is still inside the servicing window.

The OS build number is the finest layer and the one that actually matters for patching. It is a five-digit number, such as 22631 or 26100, that increments with every cumulative update. Two machines on the same product name and version number can be weeks apart in security posture if their build numbers differ. Support engineers ask for the build first because it uniquely pins the machine to a specific patch level.

Underneath all three sits the kernel version, historically reported as 10.0.x. Windows 11 still reports a kernel major version of 10.0, which is why some tools mislabel Windows 11 as Windows 10. That quirk is a legacy of how Microsoft versioned the NT kernel and is not an error in your install.

Why the marketing name is the weakest signal

The product name is the field most users check and the least informative. It tells you the generation but nothing about currency, security, or hardware compatibility.

Feature updates are delivered as enablement packages in recent releases. That means the bits for a new version often arrive in a monthly cumulative update before the version is switched on. The switch happens when a configuration flag flips, not when a large download lands. Two machines on identical hardware can therefore sit on different version numbers despite receiving the same patches.

Microsoft's servicing model ties version number to support lifetime. Each Windows 11 feature version receives security updates for a defined window, historically 24 months for Home and Pro and 36 months for Enterprise and Education. Once a version exits that window, the build stops advancing and the machine silently falls out of security coverage even though nothing on screen changes. The product name still reads Windows 11. That gap between the label and the actual patch state is the single most common version-reading mistake.

A counterintuitive detail: a machine can show a newer version number than its neighbor and still be less secure. If the older-numbered machine is on the current build with the latest cumulative update and the newer-numbered one missed the last two patches, the build number, not the version number, decides which is safer.

Reading the numbers in Settings and About

The Settings path differs slightly between families but lands on the same data.

On Windows 11, open Settings > System > About. The window lists device specifications at the top and Windows specifications below. You will see Edition, Version, Installed on, and OS build. The OS build line often includes the full build with a dot suffix, such as 22631.4317, where the digits after the dot are the revision.

On Windows 10, the path is Settings > System > About, with the same Windows specifications block. The Version field here is the four-character code, and the OS build is the five-digit number plus revision.

The winver dialog is faster and works on both families. Press Windows key plus R, type winver, and press Enter. A small dialog reports the product name, version, build, and edition. It is the command most support desks ask for because it cannot be confused with hardware specs.

For scripting, Get-ComputerInfo in PowerShell returns structured fields including WindowsProductName, WindowsVersion, and OsBuildNumber. This is useful when you need to inventory several machines at once.

Comparison of version-checking methods

Method What it shows Best for Speed Scriptable
Settings > System > About Product, version, build, edition Everyday confirmation Moderate No
winver dialog Product, version, build, edition Quick support triage Fast No
PowerShell Get-ComputerInfo Structured version and build fields Fleet inventory Moderate Yes
Command prompt ver Kernel and build string Legacy tools, logs Fast Yes
System Information (msinfo32) Full system and OS detail Deep diagnostics Slow No
Windows Update history Recent patch levels Confirming update state Moderate No

The table makes the tradeoff clear. The Settings page is friendliest, winver is fastest, and PowerShell is the only option that scales to many machines without manual reading.

How versions and builds drift apart over time

Version and build move on different clocks, and understanding those clocks explains most apparent contradictions.

A feature update changes the version number once or twice a year. A cumulative update changes the build revision roughly monthly, aligned with Patch Tuesday. The build's leading digits change only when the feature version changes, so the revision suffix is what advances week to week.

This produces a predictable timeline for a single machine.

Stage What changes Typical cadence What you see
Feature update install Version number and leading build digits 1-2 times per year New version code, e.g., 24H2
Monthly cumulative update Build revision suffix Monthly Build climbs, e.g., .4317 to .4480
Enablement package flip Version number only With a cumulative update Version changes, build digits already present
Servicing window exit Nothing visible After 24-36 months Updates stop, build freezes
Out-of-support state Nothing visible Ongoing Security risk with no on-screen signal

The row that surprises people is the enablement flip. Because the underlying files ship earlier, the version number can change without a large download, and the build digits may already have been present for weeks. The row that matters most is the servicing exit, because it produces no visible change at all.

Edge cases that break the simple answer

Several legitimate configurations make the version number misleading or unreadable.

Windows Server and Windows LTSC builds share kernel and build numbering with consumer Windows but follow different servicing timelines. An LTSC install may sit on an old version number for years by design and still be fully supported. Reading its version against a consumer support table produces a false alarm.

Windows in S mode reports the same version and build but restricts which apps can run, so the version answer alone does not describe the machine's capabilities. Likewise, an edition like Pro for Workstations or Enterprise changes the servicing window without changing the version string.

Virtual machines and cloud desktops can run a Windows image that is frozen at a specific build by the host's update policy. The guest reports that build honestly, but the version number may lag the physical fleet by months.

Preview builds from the Windows Insider channels carry version numbers ahead of general availability. A machine on a preview build is not on a released version, and comparing its number to a public support table is invalid.

Red-flag warnings to watch for:

A version number that has not changed while build revisions have also frozen suggests the update service is failing silently. A Windows 11 label paired with a kernel report of 10.0 is normal, not a sign of a mislabeled Windows 10 install. An LTSC or Server build compared against consumer support dates will look unsupported when it is not. A preview build number ahead of the public release is expected and does not indicate a corrupted install.

Practical actions to confirm and act on your version

Start with the fastest check, then move to the layer that answers your actual question.

Press Windows key plus R, type winver, and note the product name, version, and build. This takes seconds and settles the basic question.

If you need patch currency, open Settings > Windows Update and compare the installed build revision to the latest published cumulative update for your version. A revision more than one monthly cycle behind signals a stalled update path.

If you need to know whether your version is still supported, check the version against Microsoft's published servicing timeline for your edition. Home and Pro typically receive 24 months; Enterprise and Education typically receive 36 months. Reconcile the two thresholds explicitly: a Home machine on a version older than 24 months is out of support even though the product name looks current.

If you manage several machines, run Get-ComputerInfo across the fleet and sort by build revision. Machines clustered at an old revision are the ones to investigate first.

If a machine is out of support, the practical fix is to move to the current version through Windows Update or an in-place upgrade. The version number will then advance and the build will resume climbing.

What the version number cannot tell you

The version answer has firm limits, and knowing them prevents overconfidence.

It cannot confirm that updates are actually installing. A machine can sit on a current version with a stale build because the update service is broken, and the version field will look healthy.

It cannot describe hardware compatibility. A Windows 11 version number says nothing about whether the device meets the processor, TPM, or secure boot requirements that Microsoft enforces for that family.

It cannot substitute for a security assessment. Build revision narrows the patch level but does not inventory third-party software, configuration drift, or account posture.

It cannot resolve edition-specific servicing. As noted, LTSC, Server, and preview builds follow different rules, and a version string read without the edition is incomplete.

The most defensible reading combines three fields: product name for the family, version number for the feature set and support window, and build revision for patch currency. Read alone, any one of them misleads. Read together, they pin the machine precisely.

That is also why the one-line answer at the top of this article points to the About page rather than the product name alone. The page shows all three fields side by side, and the build number beneath the version is the field that answers the question most people are actually asking when they search for which Windows version they have.