How Do I Know What Version of Windows I Have: Four Built-In Checks

You can find your Windows version in under five seconds by pressing Windows key + R, typing winver, and pressing Enter; the dialog that opens shows the edition and version number (for example, "Windows 11 Version 24H2"). Four other built-in tools report the same facts with more detail: Settings, System Information (msinfo32), Command Prompt (ver and systeminfo), and PowerShell (Get-ComputerInfo). Each reads related but not identical fields, which is why two of them can appear to disagree.

What a Windows version number actually encodes

A Windows "version" is not one number but a stack of four identifiers, and each answers a different question. The product name (Windows 10 or Windows 11) is marketing. The edition (Home, Pro, Enterprise, Education) describes the feature set your license unlocks. The version, written as a four-digit year and half-year code, names the annual feature update train. The OS build is the precise compiled release, and the display version is the friendly label Microsoft assigns to that build.

The build number is the deepest identifier and the one support engineers trust. Windows 10 builds are five digits beginning with 19 (such as 19045), while Windows 11 builds are five digits beginning with 22, 23, or 26 (such as 22631 or 26100). The registry stores the same facts in one place: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion, where values named CurrentBuild, UBR, DisplayVersion, and ProductName sit side by side.

Why does this matter? Because the marketing name and the build can diverge in ways that confuse people. Windows 11 24H2, for example, reports a build in the 26100 range, not 24-something. If you search the web for "24H2" you may see build numbers that look unrelated. The version label is the train; the build is the car.

A subtle but important detail: many utilities report the OS build but append a "UBR" (Update Build Revision) that counts cumulative updates since that build shipped. Build 19045.4046 means build 19045 plus revision 4046. Two machines on the same feature update can therefore show different full build strings and still be on the same version train.

The four reliable places to look, ranked by detail

Each method below surfaces the same underlying facts but packages them differently. Use the one that matches what you need to know.

The winver dialog is the fastest and shows product name, version, and build in one small window. It does not show the edition separately when the product name already includes it, and it omits the UBR. For a quick "what version of Windows do I have" answer, winver is enough.

Settings > System > About lists edition, version, installed-on date, OS build, and experience pack in a clean grid. It also shows the processor and installed RAM, which helps when you are comparing machines. This is the best screen to screenshot for a support ticket.

System Information (msinfo32) is the deepest built-in report. It shows OS name, version, build, system type (x64 or ARM64), BIOS version, and secure boot state. Support desks ask for msinfo32 exports because one file answers most compatibility questions.

Command-line tools suit scripts and remote checks. In Command Prompt, "ver" prints only the version line. "systeminfo" prints a fuller table including OS name, version, build, and install date, but it can take several seconds to gather. In PowerShell, Get-ComputerInfo returns a large object; filter it with Select-Object WindowsProductName, WindowsVersion, OsBuildNumber, OsHardwareAbstractionLayer to avoid drowning in output.

The comparison above makes the tradeoff explicit: the fastest tool gives the least detail, and the most detailed tool takes longer.

Quantified context: build numbers, support windows, and update cadence

Windows 10 and Windows 11 follow different servicing rhythms, and the build number reveals which train you are on. Windows 10 feature updates arrived roughly twice a year through 2019, then moved to one annual update, and Windows 10 reached end of support on October 14, 2025. Windows 11 has shipped annual feature updates since 2021, with version labels such as 21H2, 22H2, 23H2, and 24H2.

Microsoft supports each Windows 11 Home and Pro feature update for 24 months from release; Enterprise and Education editions get 36 months. That means a machine on an older feature update can lose security patches while still "working," which is the single most common reason a version check matters. If Settings shows a version older than the current train, the machine may be receiving no security updates at all.

The UBR increments with each cumulative update, often monthly. A build like 22631.4317 tells you two things: the feature train (23H2, build 22631) and roughly how many cumulative updates have landed since. A very low revision on an old train is a red flag for a machine that has not patched in months.

Install date is another useful number. A machine that reports an install date within the last few weeks but an old build number may have been reset without updates, or imaged from stale media. Comparing install date to build revision catches that mismatch quickly.

Edge cases that make the answer ambiguous

Several situations produce answers that look contradictory, and knowing them prevents wasted troubleshooting.

Windows 11 reports its product name as "Windows 11" in Settings and winver, but some legacy tools and registry keys still return "Windows 10" because the underlying product architecture was not renamed. If a script prints "Windows 10" on a clearly Windows 11 machine, the script is reading the registry ProductName value, which Microsoft left unchanged for compatibility. Trust the build number over the product name string.

Windows Server shares build numbers with client Windows, so a build beginning with 26100 could be either Windows 11 24H2 or Windows Server 2025. Check the edition field, not just the build.

Virtual machines and cloud desktops can report a different build than the host because they run their own image. A VM created from a year-old template will show that year's build until it updates.

Insider Preview builds carry a "Dev," "Beta," or "Release Preview" channel label and build numbers ahead of the public train. These are not the same as the retail version even when the number looks similar.

Red flag: Settings shows a version older than the current supported train, meaning security updates may have stopped. Red flag: The registry ProductName says "Windows 10" but winver says "Windows 11"; this is a compatibility string, not a fault. Red flag: Install date is recent but the build revision is very low, suggesting stale installation media. Red flag: A VM or cloud desktop shows an older build than the physical host; update the image, not the host. Red flag: An Insider channel label appears on a machine you did not enroll; check who enabled it.

Misconceptions about version, edition, and build

Three confusions account for most wrong answers. The first is treating edition and version as the same thing. Edition (Home, Pro, Enterprise) describes features and licensing; version (24H2 and so on) describes the update train. You can run Pro on an old version or Home on the newest one.

The second is assuming the build number is the version number. Build 22631 is the compiled release; version 23H2 is the label. Searching for "22631" returns precise results, while searching for the marketing version returns broader ones. Use the build when you need exact compatibility data.

The third is reading a single field and stopping. A support script that checks only ProductName will misidentify Windows 11 as Windows 10. A check that reads only the build will miss the edition. The reliable answer combines product name, edition, version, and build.

A counterintuitive professional caveat: Microsoft sometimes changes the display version label without changing the underlying build architecture, and cumulative updates can push the UBR into the thousands. Two machines that both say "24H2" can be dozens of cumulative updates apart. The version label tells you the train; the full build string tells you how current that train is.

Practical steps to check, record, and act

The sequence below gets you a trustworthy answer and the next action in under two minutes.

Press Windows key + R, type winver, press Enter. Note the product name, version, and build exactly as shown. Open Settings > System > About. Record edition, version, OS build, and install date. Screenshot this screen. If you need compatibility detail, run msinfo32 and note system type (x64 or ARM64) and secure boot state. For scripts, run "systeminfo | findstr /B /C:"OS Name" /C:"OS Version"" in Command Prompt, or filter Get-ComputerInfo in PowerShell. Compare the version against Microsoft's current supported trains. If it is older than the current Windows 11 feature update, run Windows Update until no updates remain. If the build revision is far behind after updating, check whether the device is blocked by policy or hardware requirements.

Threshold guidance: if the version label is more than one annual feature update behind, treat security patching as at risk and update before deploying new software. If the full build string has not changed in 60 days on a machine that should be patching monthly, investigate update failures. These are heuristics, not official rules, and Microsoft's lifecycle pages are the authoritative source for support dates (Microsoft Windows lifecycle documentation).

Limits of what a version check can tell you

A version check confirms the OS train and build, but it cannot confirm that security updates are actually applying, that the license is genuine, or that the hardware meets future requirements. Windows 11 hardware requirements (TPM 2.0, Secure Boot, a supported CPU generation) are separate from the version number and are checked by PC Health Check, not by winver.

The fields also drift between tools because each reads a different registry location or API. That is expected behavior, not a fault. When two tools disagree, prefer the build number and the edition together, and treat any single field as partial evidence.

Finally, version numbers change with updates, so a value recorded today may be stale within weeks. Re-check after major updates or when troubleshooting compatibility. The mechanism is stable; the numbers are not.