You can identify your Windows version by pressing Windows key + R, typing winver, and pressing Enter. A small dialog appears with the Windows release name, such as Windows 11 Pro, plus the version and build numbers. On Windows 11, Build 22000 is the original release, 22621 is version 22H2, and 22631 is version 23H2. This takes about five seconds and requires no downloads or admin rights.

That answer covers the common case. The rest of this guide explains what each number actually means, why the same build can behave differently on two machines, and how to tell an edition from a version from a build. It also covers the traps that make people think they have the wrong Windows when they do not.

What the winver dialog actually reports

Every Windows installation carries four labels, and they answer different questions. The product name (Windows 11) tells you the generational family. The edition (Home, Pro, Enterprise, Education, IoT Enterprise) tells you which feature set is licensed. The version number (22H2, 23H2) names the annual feature update that last changed major features. The build number identifies the exact binary.

The build is the ground truth. Microsoft builds each Windows release from a specific codebase, and the build number increments with every servicing change. Windows 10 version 22H2 ships as Build 19045. Windows 11 version 23H2 ships as Build 22631. When you update a single cumulative patch, the build's revision suffix rises, for example 22631.4317, but the base build stays put.

Why this matters: sales listings, driver pages, and support scripts often quote versions loosely. A vendor that says "supports Windows 11 22H2 and later" is making a promise about a build floor, not a name. If your winver shows Build 22621, you meet that floor. If it shows 22000, you are on the original Windows 11 release and may not qualify.

The ver command in Command Prompt prints the same base build more tersely. PowerShell's Get-ComputerInfo cmdlet returns a richer object, including WindowsProductName, WindowsVersion, OsBuildNumber, and OsHardwareAbstractionLayer. Get-ComputerInfo can take 10 to 30 seconds on older hardware because it queries the firmware layer.

Version, build, and edition: quantified context

The number of possible labels is smaller than it looks. Microsoft has shipped a limited set of feature-update versions, each mapped to one Windows 10 build family and one Windows 11 build family.

Label type Example value What it controls How often it changes
Product name Windows 11 Major UI and support lifecycle Every few years
Edition Windows 11 Pro Feature set and licensing limits Fixed at install or upgrade
Version 23H2 Annual feature update train Once per year
Base build 22631 Exact codebase and driver compatibility Per feature update
Revision 22631.4317 Cumulative security patch level Monthly or more
Architecture x64 Which binaries and drivers install Fixed at install

Most consumer machines in service run one of four configurations. Windows 10 Home or Pro on Build 19045 is the largest installed base. Windows 11 Home or Pro on Builds 22631 or 26100 covers most newer hardware. Enterprise and Education editions track the same builds but unlock policy features.

The revision suffix is where support status lives. Microsoft publishes the minimum revision that closes each month's Patch Tuesday vulnerabilities. A machine at 22631.3593 may be months behind. A machine at 22631.4317 is current as of its last update cycle. The suffix does not change the edition or the version, so it rarely appears in marketing, but it is the number that matters for security posture.

Reading the edition without opening Settings

Settings > System > About shows the edition in plain language under "Windows specifications." That path works on Windows 10 and 11. But Settings can be slow, restricted by policy, or unavailable in Safe Mode, so three alternates are worth knowing.

The first is the System Information tool, launched by running msinfo32. The System Summary pane lists OS Name, Version, and Build in the top rows, plus the System Type (x64-based PC or ARM64-based PC). That architecture line is the fastest way to confirm whether you have an ARM machine, which changes which installers and drivers apply.

The second is the registry path HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion. The values EditionID, ProductName, CurrentBuild, and UBR (update build revision) live there. UBR is the suffix that winver hides behind the decimal, so a machine reading UBR 4317 on base build 22631 is at 22631.4317.

The third is the command wmic os get Caption,Version,BuildNumber. Windows has deprecated WMIC, so on newer builds this may return an error. Prefer PowerShell: Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber. The Caption field embeds the edition name, which resolves ambiguity when two machines look identical on screen but differ in licensing.

Red flag: winver shows a build your organization's update rings do not list. A mismatched ring assignment can leave a device unpatched. Red flag: the edition reads "Windows 11 Home Single Language." That edition cannot join a domain and lacks some Pro management features. Red flag: ProductName says Windows 10 but the UI looks like Windows 11. That combination points to a half-finished upgrade or a mislabeled virtual machine. Red flag: the build revision has not moved in 60 days. Check Windows Update history before assuming the device is configured correctly. Red flag: System Type reads x86 on hardware that should be 64-bit. A 32-bit install caps RAM use and blocks many modern drivers.

The traps that make people think they have the wrong Windows

The most common error is confusing the OS build with the firmware or the application build. Microsoft Office has its own version numbers, and browsers have theirs. A user who sees "Version 128" in a browser may believe that is the Windows version. It is not.

The second trap is Windows as a service. Windows 10 and 11 receive feature updates through the same channel as security patches, so a machine's version can change overnight without user action. A user who checked in March may be on 22H2 and by November on 23H2, with no visible sign beyond a restart prompt. The build confirms what actually landed.

The third trap is the ARM question. A Windows on ARM device reports the same product name and edition as an Intel machine. Only System Type or the PROCESSOR_ARCHITECTURE environment variable reveals the difference. This matters because emulated x64 apps run with a performance penalty, and some drivers simply do not exist for ARM. A user who installs an x64 driver on an ARM machine and sees it fail may blame Windows, not the architecture.

The fourth trap is edition virtualization. Windows 11 Pro can host Hyper-V and Windows Sandbox, which run guest Windows installations. A user inside a sandbox sees a full Windows desktop but is not looking at their host build. Remote desktop sessions and virtual machines show the guest's winver, not the physical machine's.

A professional caveat: Microsoft's own documentation sometimes lists a build as "Windows 11, version 24H2" while the winver dialog shows only "24H2" without the word "version." That is a labeling difference, not a mismatch. Scripts that string-match on the full phrase will fail against winver output.

The plain-language version: check the build number, not the marketing name, and check it on the machine you actually use, not a remote session or a virtual copy.

When the labels disagree: timelines and thresholds

Feature updates roll out on a schedule, and knowing that schedule helps you interpret stale or surprising numbers. Microsoft ships one annual feature update in the fall, then services it with monthly cumulative updates. The timeline below reflects that cadence.

Time point What happens Build signal to expect
Fall release Annual feature update ships New base build, e.g., 22631
Month 1 after release First cumulative patch Suffix rises, base unchanged
Months 2-12 Monthly cumulative patches Suffix rises monthly
~18-24 months after release Support window narrows for Home/Pro Older base builds stop receiving patches
Two years after release Microsoft ends servicing for that family No further patches on that build
End of device support Hardware may not meet next Windows Winver shows an unsupported build

The thresholds matter because "which Windows do I have" and "is my Windows supported" are different questions with the same answer source. A machine on Build 22621 may be fully supported or out of support depending on the calendar and the edition. Enterprise and Education editions receive longer servicing windows than Home and Pro, so two identically labeled machines can have different support end dates.

Build floors also appear in driver and app requirements. Some GPU drivers publish a minimum build, for example 22621 or later, because a graphics API or security mitigation landed in that build. A user below the floor sees an installer refuse to run with a vague error. The winver build tells you whether the error is real or the installer is being conservative.

For hardware compatibility, Microsoft publishes official minimum system requirements for Windows 11, including TPM 2.0 and a supported processor list. You can verify TPM status with tpm.msc and processor support against Microsoft's published list. These checks are not part of identifying your build, but they explain why an upgrade path may be blocked even when the version number looks upgradeable.

Practical actions: a five-minute identification and verification routine

Work through these steps in order. Each is fast and each answers a distinct sub-question.

Run winver and write down the product name, edition, version, and full build including the suffix. Open Settings > System > About and confirm the same details, then check System Type for x64 or ARM64. Run Get-CimInstance Win32_OperatingSystem in PowerShell to confirm the Caption string and BuildNumber. Check tpm.msc only if you plan to install or upgrade Windows 11, because TPM status affects eligibility, not identification. Record the build suffix against Microsoft's current Patch Tuesday minimum for your edition and version, then compare to Windows Update history. If the device is managed, compare your recorded build to the update ring assigned in your organization's management console.

For threshold reconciliation: the suffix you read is the authoritative patching level, the base build is the authoritative feature level, and the product name plus edition is the authoritative licensing level. If any two disagree with your expectations, the more specific number wins. The build beats the name, and the suffix beats the base build.

These steps also catch the subtle case of a machine that reports a Pro caption but behaves like Home. That pattern can indicate a licensing state problem rather than a version problem, and the fix is a license activation check, not a reinstall.

Limits of identification and what the numbers cannot tell you

The build number will not tell you how fast the machine runs, whether its drivers are current, or whether the user experience is degraded by background policy. Those are separate diagnoses with separate tools. A user who asks "which Windows do I have" because something feels wrong should treat the build as a starting point, not an answer.

The numbers also cannot resolve licensing ambiguity beyond what the Caption string reports. Volume-licensed enterprise installs may use a KMS or subscription activation model whose status is visible only through slmgr.vbs /dlv or an admin console. The winver dialog shows the effective edition but not the activation channel.

Finally, build mappings change with servicing. A build you identified as current in one month may be one revision behind the next. Recheck winver after any significant update or before filing a support request, because support scripts almost always ask for the exact build first. The five-second check is the cheapest evidence you can supply.

This article is general educational information about identifying Windows versions, editions, and build numbers. It is not a diagnosis, configuration approval, or licensing opinion, and it does not guarantee that any build is supported or secure for your environment. For managed devices, compliance decisions, or immediate security concerns, consult your organization's IT administrator or a qualified local professional.