The fastest way to find out which Windows version you have is to run the command winver in the Run dialog (press Windows key + R, type winver, press Enter). A small window opens showing your exact edition and version number, such as Windows 11 Pro, version 24H2, build 26100. If you prefer not to type, open Settings > System > About, where the same edition, version, and build number appear together.
Where Version Identity Actually Lives
Windows stores its identity in the registry and reports it through several different numbers, which is why the answer seems inconsistent depending on where you look. The product name (Windows 10 or Windows 11) comes from a branding string. The version number (like 22H2 or 24H2) is a calendar-style feature-update label. The build number is the true engineering identity, and it increments with every compiled release.
The winver dialog and the Settings About page both read from the same underlying registry keys, so they always agree. Third-party "system info" tools sometimes read a different key and can show a stale or misleading label. Microsoft's own tools remain the reference standard for identity.
The reason multiple numbers coexist is compatibility. Software installers often check the build number, not the product name, because build ranges map cleanly to supported feature sets. A program that says "requires Windows 10 build 19041 or later" is actually checking a numeric threshold, not a marketing label. The plain-language takeaway: the build number is the number that matters for software compatibility.
Build Numbers, Feature Updates, and What Changed
Windows 10 launched in July 2015 with build 10240. Windows 11 launched in October 2021 with build 22000. Each subsequent feature update raises the build number by a known increment, and Microsoft publishes the mapping. Windows 11 24H2 corresponds to build 26100. Windows 10 22H2 corresponds to build 19045.
Service packs and monthly cumulative updates also bump the build, though usually only the revision suffix (for example, 19045.3803). The base build stays stable across a feature cycle. This distinction matters: two machines on "Windows 10 22H2" can have different revision numbers depending on how recently each installed updates.
The build number is the most reliable single identifier because it encodes both the release train and the update level. If you know the build, you can look up the exact support status and end-of-servicing date from Microsoft's lifecycle documentation. Feature labels like "22H2" are convenient but ambiguous across product lines.
Edition Differences That Change Behavior
Edition (Home, Pro, Enterprise, Education) is a separate axis from version and build. Two machines can share build 26100 but run different editions with materially different capabilities. Edition determines whether you get BitLocker, Remote Desktop host, Group Policy Editor, Hyper-V, and domain join.
| Edition | Typical user | Key gated features | Rough retail path |
|---|---|---|---|
| Home | Consumer | No BitLocker management, no Group Policy | Preinstalled on most laptops |
| Pro | Small business, power user | BitLocker, Remote Desktop, Hyper-V | Retail upgrade license |
| Enterprise | Large organizations | Advanced management, AppLocker | Volume licensing only |
| Education | Schools | Enterprise features, school tools | Academic licensing |
| Pro for Workstations | High-end hardware | ReFS, persistent memory support | Specialized OEM |
The edition string appears in winver and in Settings > System > About. A common confusion: a laptop sold as "Windows 11" may be Home edition, and the buyer discovers only later that Remote Desktop hosting is unavailable. Check the edition before assuming a feature exists.
The Counterintuitive Part: "Windows 11" Can Report as Windows 10
Some diagnostic tools and older installers report Windows 11 as "Windows 10" because Windows 11 kept the internal major version number at 10.0. The build number distinguishes them: anything at or above 22000 is Windows 11, while 19045 and below is Windows 10. This design choice preserved compatibility, but it confuses anyone reading raw version strings.
A professional caveat follows from this. When a vendor's system-requirements page says "Windows 10 or later," it may not have been updated for Windows 11 semantics, and when a tool reports "Windows 10.0.26100," that is genuinely Windows 11. Trust the build number over the product-name string in any diagnostic output.
Red Flags and Misleading Signals
A "Windows 11 ready" sticker on the box does not mean Windows 11 is installed; it means the hardware passed the compatibility check. The desktop wallpaper and Start menu layout are cosmetic and prove nothing about version. A third-party "version checker" website that asks you to download an executable is a common malware vector; use only built-in tools. An "Activate Windows" watermark indicates licensing status, not version, and does not tell you which edition you run. A build number far below the current baseline usually means updates are paused or blocked, not that the machine is a different product.
Practical Steps to Confirm and Record Your Version
First, open Run (Windows key + R), type winver, and read the four lines: edition, version, build, and revision. Second, cross-check in Settings > System > About, where the same values appear with the OS build and installed-on date. Third, note the build number and look it up against Microsoft's Windows release health page to confirm support status and the next servicing deadline.
For a machine you administer, save the output of systeminfo to a text file; it includes OS name, version, build, and installation date in one block. For fleets, the Get-ComputerInfo PowerShell command returns edition, version, and build as structured fields, which is far more reliable than parsing screenshots. If you are preparing to install software with a stated minimum build, compare the documented threshold against your build number directly rather than against the product name.
Limits of What a Version Check Tells You
Version and build identify the operating system release, but they say nothing about patch completeness beyond the revision suffix, nothing about driver health, and nothing about whether the machine meets a specific application's requirements. A current build can still fail a compatibility check because of missing runtimes or hardware. The About page also does not reveal whether the license is retail, OEM, or volume, which affects transfer rights and support entitlements. Use the version check as a starting point, then verify the specific requirement you actually care about against the vendor's documentation rather than assuming the label settles it.