To see which Windows version you have, press Windows key + R, type winver, and press Enter. A dialog box opens showing your edition (such as Windows 11 Pro), version number (like 24H2), build number, and installation date. Alternatively, open Settings > System > About for the same details plus processor architecture and installed RAM. Both methods work identically on Windows 10 and Windows 11, and the entire check takes under ten seconds.

That quick answer covers almost every situation. But "version" means several different things in Windows, and the distinction matters when you install software, troubleshoot compatibility problems, or check whether your PC still receives security updates. The sections below explain what each number actually represents, why Microsoft reports it in multiple places, and which figure to trust for which decision.

What Windows version numbers actually represent

Windows reports its identity through four separate identifiers, and each one serves a different purpose in the operating system's architecture.

The product name is the marketing label: Windows 10 or Windows 11. Microsoft treats these as distinct operating systems, though they share a common kernel lineage and much of the same code base. Windows 11 shipped in October 2021 with stricter hardware requirements, including TPM 2.0 and Secure Boot, which is why some capable machines remain on Windows 10.

The version number is a four-digit year-half code, such as 22H2 or 24H2. The first two digits indicate the year, and H1 or H2 indicates the first or second half. Microsoft moved to this scheme with Windows 10's 1903 release and continued it in Windows 11.

The build number is the internal engineering identifier, formatted as a five-digit number followed by a period and a smaller revision, like 22631.4460. The large number identifies the development branch; the small number tracks cumulative patches applied to that branch. Two machines on the same named version can have different full build numbers if one has installed more updates.

The edition is the licensing tier: Home, Pro, Enterprise, Education, and so on. Edition determines which features are available, not which patches you receive.

The critical insight is that the product name alone tells you almost nothing about your machine's update status. A Windows 10 Pro machine and a Windows 11 Home machine could both display "version 23H2" while sitting on entirely different code bases with different support timelines. You need the build number to know precisely where you stand.

Reading the About page, line by line

The Settings > System > About screen presents roughly a dozen fields, most of which are irrelevant to version identification. Four matter.

Windows specifications lists the edition, version, installed on date, and OS build. The OS build is the field to record when you contact support or check update eligibility, because it uniquely identifies your patch level.

System type tells you whether Windows is 64-bit or 32-bit and whether it runs on x64 or ARM hardware. This matters increasingly in 2025 because ARM-based Windows machines run a different build track with its own compatibility considerations. A program that installs cleanly on x64 Windows might fail on ARM Windows even with the same version number.

The installed on date reflects when the current feature update was applied, not when Windows was first activated. A machine purchased in 2021 and upgraded to a newer feature release in 2024 will show the 2024 date.

Processor and installed RAM sit below the Windows specifications block. These fields are useful when checking whether your hardware meets the requirements for a future upgrade, though the eligibility check itself lives in PC Health Check rather than the About page.

The winver dialog, by contrast, shows only four fields: edition, version, OS build, and a copyright line. It is faster but less informative. For most users, winver answers the question; for troubleshooting, the About page gives more context.

Version, build, and edition: a comparison

The three identifiers get conflated constantly, and mixing them up leads to wrong conclusions about support status and software compatibility.

Identifier Example What it tells you Where to find it Changes when
Edition Windows 11 Pro Feature set and licensing tier Settings > About; winver Never, unless you upgrade the license
Version 24H2 Feature release cycle and support window Settings > About; winver Twice yearly, historically, now annually
Build 26100.2314 Exact patch level Settings > About; winver Every cumulative update, often monthly
Display version 24H2 Same as version, in release language winver; registry With each feature update
OS architecture 64-bit, ARM64 Which binaries and drivers will run Settings > About Never

A practical rule: quote the full build number (both parts) when reporting a problem. Quote the version when checking whether your release still receives security patches. Quote the edition when asking about a feature. Confusing these three is the most common version-related error in support forums.

One counterintuitive detail: the version number can go backward on paper while the build number goes forward. Windows 11 23H2 is build 22631, and Windows 11 24H2 is build 26100. But a machine on 23H2 with all patches applied could report a higher trailing build revision than a machine freshly installed with 24H2 and no updates. The leading number determines the branch; the trailing number determines patch recency. Read them together, never alone.

Timeline: how a Windows release evolves

Windows versions follow a predictable life cycle, and knowing where your build sits on that arc prevents wasted troubleshooting.

Stage Duration What happens User-visible signal
General availability Month 0 Feature update releases in waves Offered via Windows Update
Broad deployment Months 1–3 Rollout expands to all eligible devices Update becomes mandatory or recommended
Servicing 18–36 months Monthly cumulative patches Build revision increments
End of servicing warning 90 days before cutoff Update prompts intensify Notifications in Settings
End of servicing Specific date No more security patches No further builds issued
Extended security updates Up to 3 years, paid Critical patches only, enterprise focus Available through enrollment

The servicing duration varies by edition. Windows 10 Home and Pro releases historically received 18 months of support; Enterprise and Education received 30. Windows 11 simplified this, with Home and Pro getting 24 months and Enterprise and Education getting 36. Windows 10 version 22H2, the final release of that product line, ends standard support in October 2025, after which consumer devices receive no further security fixes.

That end date is the single most consequential piece of information tied to your version number. A Windows 10 22H2 build in September 2025 is current; the same build in November 2025 is unpatched and exposed to every subsequent vulnerability. The build number alone cannot tell you this. You need to know the release's servicing calendar, which Microsoft publishes per version.

Why "latest version" is not a single answer

The newest available version depends on four variables, and Microsoft's rollout process means your neighbor, your colleague, and you may all be on different builds despite clicking the same Check for updates button.

Hardware eligibility. Windows 11 requires a compatible 64-bit CPU, 4 GB of RAM, 64 GB of storage, UEFI firmware with Secure Boot, and TPM version 2.0. A machine failing any of these stays on Windows 10, which means the newest version that machine can run is capped regardless of what Microsoft releases.

Rollout throttling. Microsoft ships feature updates in phases, initially to a small percentage of devices and expanding only as telemetry shows acceptable failure rates. A fully eligible machine may not see the newest version for weeks after its release.

Edition and management. Enterprise devices managed by IT departments often sit on a deliberate delay, with administrators holding updates until internal testing completes. Consumer devices on the same version number may be months ahead in patch level.

Deferral settings. Windows 10 Pro and higher, plus all Windows 11 editions, expose update pause and deferral controls. A paused device reports the version it last installed, not the version Microsoft has released.

The practical consequence is that "latest" is a moving target with no single correct answer. What you can check is whether your build falls within the currently serviced window for your release. If it does, you are current in the only sense that matters for security.

Practical steps: get the number and act on it

Step one: open winver and record both the version and the full build number, including the period and trailing digits. Write it down; you will need it twice.

Step two: check Windows Update (Settings > Windows Update). If a feature update is offered, your current build is at least one version behind the newest available to your hardware. Installing it moves you to a newer servicing track.

Step three: compare your version against Microsoft's published end-of-servicing list for your edition. If your version is within 90 days of its end date, plan the upgrade now rather than when patches stop.

Step four: verify architecture. On ARM devices, confirm the ARM64 architecture in Settings > About before installing software that lists only x64 support.

Step five: if Update shows "You're up to date" but your version is several releases old, check deferral settings and the PC Health Check app. A passing eligibility check plus an up-to-date status plus an old version usually indicates a deferral or a blocked rollout, not a broken machine.

Step six: to check the build through a script, run the command ver in Command Prompt for the abbreviated build, or use PowerShell's Get-ComputerInfo for a full structured dump. Both provide the same identifiers as the GUI.

Red flags that warrant action rather than waiting:

Version is within 60 days of its end-of-servicing date and no upgrade is offered. Build trailing revision has not changed in over 60 days despite active use. Windows Update reports an error code instead of a status. PC Health Check flags ineligibility for Windows 11 on hardware you believe qualifies. Version and build disagree with each other relative to Microsoft's published mapping table.

Edge cases and what they mean

Virtual machines report the same fields as physical machines but can carry frozen builds indefinitely. A VM snapshot taken in 2022 and restored today shows a 2022 build, and it will not update until it runs long enough to contact Microsoft's servers. Organizations maintaining long-lived VMs must patch them explicitly.

Windows Server shares build numbers with client Windows in some releases but follows a separate servicing calendar and separate edition naming. Version numbers that look identical between Server and client editions do not share support timelines.

Windows Insider builds report a version number plus a Canary, Dev, Beta, or Release Preview channel designation. These are pre-release and should never be assumed current for security purposes. The build number is real, but the servicing model is experimental.

Machines with sysprep images or OEM recovery partitions sometimes display a version reflecting the factory image rather than the current state, if the update history has been reset. Checking the actual build tells the truth the version label may not.

Misconceptions worth correcting

The most persistent misconception is that the version number tells you how up to date Windows is. It does not. A 23H2 build with yesterday's cumulative update is more current than a 24H2 build three months behind on patches. Version indicates the feature track; only the build's trailing revision indicates patch recency.

A second misconception treats Windows 10 and Windows 11 as interchangeable in support terms. They are not. Windows 11 releases receive 24 months of servicing for Home and Pro; Windows 10's final release ends consumer support in October 2025 and receives nothing after that for non-enterprise devices. The product name, not the version suffix, determines the timeline.

A third holds that the update history page in Settings shows everything installed. It shows feature updates and some cumulative updates but not every patch, and resetting update history for troubleshooting wipes the record without changing the actual build. The build number is the ground truth; the history is a convenience log.

The professional caveat: Microsoft's own documentation maps version numbers to builds, but OEM recovery media and enterprise imaging tools sometimes produce builds that do not appear in that public mapping. When a build cannot be found in Microsoft's release health dashboard, treat the mapping as uncertain and rely on winver plus Microsoft's release information page rather than third-party version tables, which frequently lag or contain transcription errors. In managed environments, defer to your IT department's inventory system, since it likely tracks the fleet using the same identifiers Microsoft uses for support.

Finally, no version check can tell you whether a specific piece of software will work. Compatibility depends on edition, architecture, and individual patches, not just the version label. When a vendor lists "Windows 11 supported," verify the build range and architecture before assuming your machine qualifies.