You can identify your Windows version in under ten seconds: press Win+R, type winver, and hit Enter. The dialog that appears names the edition (Home, Pro) and the version (Windows 11 or Windows 10), plus the build number that pins down the exact release. That build number is the part most people miss, and it's the one that decides whether your PC still receives security updates β Windows 10 support ended on October 14, 2025, so a Windows 10 build now means you're either on a paid Extended Security Updates plan or running unprotected.
The Ten-Second Check That Settles It
The Run dialog is the fastest honest answer, and it works identically on Windows 7, 8.1, 10, and 11. Hold the Windows key and tap R, type winver with no spaces, and press Enter. A small "About Windows" box appears with the edition, version, and build in four lines of text.
Read the build number carefully. Windows 11 24H2 reports build 26100, Windows 11 23H2 reports 22631, Windows 11 22H2 reports 22621, and Windows 10 22H2 reports 19045. Those five-digit prefixes are how Microsoft's release health dashboard tracks problems, so they matter when you're troubleshooting a specific bug.
The dialog also shows the "OS Build" with a dot suffix, such as 26100.2314. Everything after the dot is the cumulative update revision, not a different version β a machine on 26100.2314 and one on 26100.1742 are both Windows 11 24H2, just patched to different months. This trips up people comparing notes in forums.
If winver returns nothing or the dialog won't open, you're likely on a locked-down work machine where Group Policy hides it. Skip to the Settings method below, which is harder to disable. And if you're on Windows 7 or 8.1, winver still works but you'll see no version branding beyond the number β both have been out of support since January 2020 and January 2023 respectively.
Settings Shows Edition and Build in One Panel
Open Settings with Win+I, then go to System > About on Windows 11, or System > About on Windows 10 as well. The "Device specifications" block lists processor, installed RAM, and system type; the "Windows specifications" block beneath it gives edition, version, installed date, OS build, and experience pack.
The version line here uses the marketing format β "24H2" rather than "26100" β while the OS build line gives you the number. Cross-reference them: if Settings says version 24H2 and build 26100, you're consistent. If Settings says 23H2 but the build reads 22631.4391, that's the October 2024 patch level for that release, still supported until November 2025 for Home and Pro.
On Windows 10, this same panel is where you'll see the end-of-support messaging Microsoft began rolling into Settings in 2024. If your Windows 10 PC shows a banner about support ending, that panel confirms you're on 22H2, the final feature update for that OS. Any Windows 10 build below 19045 is older than 22H2 and should be updated before you do anything else.
One quirk worth knowing: on Windows 11, "Experience" here refers to the cumulative servicing stack, and a mismatch between the version and build lines sometimes appears right after a feature update when a reboot is pending. If they don't agree, restart and check again. The panel is authoritative once the machine has settled.
System Information Gives the Full Hardware-and-OS Record
Press Win+R, type msinfo32, and Enter. The System Information window opens with "System Summary" selected and lists OS Name, Version, Build Number, System Manufacturer, System Model, BIOS version, and processor in a single scrollable list. This is the view IT departments screenshot when filing tickets.
The OS Version field here reads like 10.0.26100 β the 10.0 prefix is a legacy artifact Microsoft has carried since Windows 10 and never bumped, even on Windows 11. Don't read that as "Windows 10." The Build Number line is the real identifier, and it matches what winver shows.
msinfo32 is the only built-in tool that pairs the OS build with the BIOS and hardware revision in one screen, which is why it's the right pick when you're checking compatibility for a Windows 11 upgrade. Windows 11 requires TPM 2.0, UEFI with Secure Boot capability, and a supported CPU; the System Summary won't show TPM directly, but the BIOS mode line tells you UEFI versus Legacy, and the processor line lets you check against Microsoft's published CPU list.
Launching msinfo32 takes a few seconds longer than winver, and on older spinning-disk machines it can take ten or more. On a machine where msinfo32 hangs at "Collecting information," the WMI repository is usually damaged β that's a separate repair, not a version identification problem. Use winver as the fallback in that case.
Command Prompt and PowerShell Output You Can Copy
Open Command Prompt and run ver. It returns a single line like Microsoft Windows [Version 10.0.26100.2314] β the same legacy 10.0 prefix, same dot-suffix revision. It's the fastest text output available if you need to paste the result into a chat or ticket.
For more detail, run systeminfo in Command Prompt. Among roughly two dozen lines, you get "OS Name: Microsoft Windows 11 Pro," "OS Version: 10.0.26100 N/A Build 26100," and "OS Build Type." The command takes five to fifteen seconds because it queries hardware as well. PowerShell's Get-ComputerInfo returns the same data as an object, with WindowsProductName and WindowsVersion properties, and it's the right choice if you're scripting an inventory across several machines.
The catch with systeminfo is localization β on a non-English Windows install, the field labels are translated, so a script that greps for "OS Name" breaks. Get-ComputerInfo property names stay in English regardless of display language, which is why administrators prefer it. On Windows 10 and 11, Get-ComputerInfo is available in Windows PowerShell 5.1 by default; it doesn't exist in PowerShell 7 without the Microsoft.PowerShell.Management compatibility module loaded.
If you only need the build number in a script, [System.Environment]::OSVersion.Version.Build returns the integer directly. That's the cleanest programmatic path, and it avoids parsing any human-readable string.
The Build Number Table That Decides Support
| Reported version | Build number | Release date | Support status as of November 2026 |
|---|---|---|---|
| Windows 11 25H2 | 26200 | September 2025 | Supported (mainstream) |
| Windows 11 24H2 | 26100 | October 2024 | Supported |
| Windows 11 23H2 | 22631 | October 2023 | Home/Pro ended November 2025; Enterprise/Edu supported |
| Windows 11 22H2 | 22621 | September 2022 | Ended October 2024 |
| Windows 11 21H2 | 22000 | October 2021 | Ended October 2023 |
| Windows 10 22H2 | 19045 | October 2022 | Ended October 14, 2025; ESU available |
| Windows 10 21H2 | 19044 | November 2021 | Ended June 2023 |
| Windows 8.1 | 9600 | October 2013 | Ended January 2023 |
| Windows 7 | 7601 (SP1) | February 2011 | Ended January 2020 |
Microsoft publishes these build numbers on its Windows release health pages and in the WinRE release information docs, and the support dates come from the company's lifecycle pages. The table's value is that it converts a five-digit number into a support verdict in one step.
Notice the 23H2 split. Windows 11 23H2 Home and Pro reached end of servicing in November 2025, but Enterprise and Education editions of the same build stay supported longer under Microsoft's separate lifecycle for commercial SKUs. Two machines reporting build 22631 can have completely different patch status depending on edition β which is why the winver dialog shows edition alongside build.
Windows 10 22H2 is the row that matters most right now. Consumer support ended October 14, 2025, and Microsoft's Consumer Extended Security Updates program offers enrolled machines security patches through October 2026 β one year, not the three-year ESU window business customers can buy. If your Windows 10 PC reports 19045 and you haven't enrolled, you're receiving no security updates as of this writing.
Version Numbers and Build Numbers Are Different Things
Microsoft's version numbering has three layers that people collapse into one, and the confusion causes real mistakes. The marketing version is what you see in ads: Windows 11, or the year-half format like 24H2 meaning the second half of 2024. The internal version is the 10.0 prefix that never changes. The build number is the five-digit code that identifies the specific release.
Windows 11 didn't bump the internal version to 11.0. Microsoft kept 10.0 for compatibility, because thousands of installers, drivers, and enterprise applications check the version string and would break on an unexpected major number. So a Windows 11 24H2 machine truthfully reports "Version 10.0.26100" while being unambiguously Windows 11. This is the single most common source of "wait, am I on 10 or 11?" confusion.
The winver dialog resolves it cleanly because it prints "Windows 11" as a header above the version line. If you're reading raw output from ver or systeminfo without that header, check the build: anything at 22000 or above is Windows 11, and 19045 or below is Windows 10 or earlier. That threshold is a hard line, not a heuristic.
Feature updates change the build number's first five digits; cumulative updates change only the digits after the dot. So 26100.2314 to 26100.2605 is a monthly patch, while 22631 to 26100 is a feature upgrade. Knowing which you're looking at tells you whether a reboot-and-wait will fix a problem or whether you need to run Windows Update's "Check for updates" to pull a new release.
Why the Edition Line Matters More Than You Think
Editions aren't cosmetic. Windows 11 Home lacks BitLocker management, Group Policy Editor, Hyper-V, and Remote Desktop hosting β all present in Pro. Windows 11 Pro adds those, and Enterprise and Education add more on top. If a tutorial tells you to open gpedit.msc and the command isn't found, you're almost certainly on Home, and the winver dialog would have told you that immediately.
The edition also governs your support timeline, as the 23H2 row above shows. And it governs upgrade paths: Windows 10 Home can upgrade to Windows 11 Home for free on qualifying hardware, and Windows 10 Pro to Windows 11 Pro, but you can't cross from Home to Pro without buying a license. Microsoft's upgrade offer for qualifying Windows 10 PCs was still live as of late 2025, though the company has changed its end date more than once β confirm the current window on Microsoft's Windows 11 upgrade page rather than trusting a blog post.
winver shows edition in plain language ("Windows 11 Pro," "Windows 10 Home"). Settings shows the same. For the technically precise SKU name, run DISM /Online /Get-CurrentEdition in an elevated Command Prompt β it returns strings like Professional or CoreSingleLanguage, which is what license compliance tools check.
ARM, IoT, and Server Builds Break the Pattern
Not every Windows install follows the consumer numbering. Windows on ARM β running on Qualcomm Snapdragon laptops like the Surface Laptop 7 or Copilot+ PCs β reports the same version and build numbers as x64 Windows 11, so winver looks identical. The difference shows up in Settings > System > About under "System type," which reads "64-bit operating system, ARM-based processor" instead of "x64-based processor." That distinction determines which installers you can run, since x64 emulation works but some drivers and anti-cheat systems don't.
Windows Server has its own builds entirely: Server 2025 reports build 26100 like Windows 11 24H2 (they share a codebase), Server 2022 reports 20348, and Server 2019 reports 17763. On a Server machine, winver shows "Windows Server 2025" as the header, so the build-sharing doesn't cause confusion in practice β but if you're reading a build number out of a log without the header, 26100 could mean either.
Windows IoT Enterprise and LTSC (Long-Term Servicing Channel) builds also share version numbers with their consumer counterparts but carry ten-year support instead of the standard 18-to-36-month lifecycle. A machine reporting Windows 11 Enterprise LTSC 2024 on build 26100 will still be patched in 2034. This is why you should read the full edition string, not just the build, when planning upgrades across a fleet.
Giving Someone Your Version Info Without Screenshots
When you're on a support call or forum thread, the fastest clean report is one line: edition, version, build. For example, "Windows 11 Pro 24H2, build 26100.2314." That's everything a support agent needs, and it's all visible in a single winver dialog.
If they ask for more, msinfo32 has a File > Save option that exports the entire System Summary to a text file. That's cleaner than a photo of a screen and includes BIOS version, baseboard model, and memory configuration that often matter for driver issues. The file is plain text and small enough to paste entirely.
Avoid sending phone screenshots of the Settings page when a text paste will do β the build number is often cut off or blurry, and support threads stall on "what's the last five digits?" Copying from winver or systeminfo eliminates that round trip. On a machine where you can't paste, type the four key values: edition, version, OS build, and system type.
One privacy note: systeminfo also prints the Windows product ID and the registered owner name. Strip those before posting publicly. The OS Name, OS Version, and OS Build lines are the only ones a stranger needs.
FAQ
Does Windows 11 still report version 10.0?
Yes, and it will keep doing so. Microsoft retained the 10.0 internal version prefix on Windows 11 for application compatibility, so ver, systeminfo, and msinfo32 all report something like 10.0.26100 on a Windows 11 24H2 machine. The winver dialog header is the reliable place to see "Windows 11" spelled out. If you're parsing version strings in a script, treat build 22000 and above as Windows 11.
What's the difference between 24H2 and build 26100?
24H2 is the marketing name for the feature update released in the second half of 2024; 26100 is the build number that release carries. They describe the same release at two levels of precision. Monthly patches don't change either β they only move the digits after the dot, as in 26100.2314. A new feature update would change both, to something like 25H2 and build 26200.
I'm on Windows 10 22H2 β am I still getting updates?
Only if you enrolled in Microsoft's Consumer Extended Security Updates program, which provides security patches through October 2026 for a fee or, in some regions, free under conditions Microsoft has published. Standard support for Windows 10 22H2 ended October 14, 2025. Check Settings > Windows Update for the ESU enrollment prompt; if it isn't there, your region or account type may not qualify, and Microsoft's lifecycle page is the authority.
Can I find the version without any tools or commands?
Yes. Open Settings with Win+I and go to System > About. The "Windows specifications" section lists edition, version, and OS build in plain text, no typing required. It's slower than winver by a few clicks but harder for administrators to disable, which makes it the fallback on locked-down machines.
Why does my build number end in a different four digits than my friend's?
Everything after the dot is the cumulative update revision, not a separate version. Machines on the same feature release but patched in different months will show different suffixes, like 26100.2314 versus 26100.2605. Run Windows Update to bring yours current; the suffix should converge after the next Patch Tuesday.
Does the build number tell me if my PC can upgrade to Windows 11?
No β build number identifies your current OS, not your hardware eligibility. Windows 11 requires TPM 2.0, UEFI Secure Boot, 4 GB RAM, 64 GB storage, and a supported CPU, all of which you check separately. Run Microsoft's PC Health Check app for the official verdict, and use msinfo32 to read BIOS mode and processor model if the checker gives an ambiguous result.
What about Windows 8.1 and 7 β does winver still work there?
winver runs on both and reports build 9600 for Windows 8.1 and 7601 for Windows 7 SP1. Neither OS has received security updates since January 2023 and January 2020 respectively, so the version check is mostly academic β a machine on either build is running without patches. If you find one in service, the finding is the problem, not the version.
Can two machines with the same build have different support dates?
Yes, when editions differ. Windows 11 23H2 Home and Pro ended servicing in November 2025, but Enterprise and Education editions of build 22631 remain supported under Microsoft's commercial lifecycle. Always report edition alongside build when comparing support status, since the build alone doesn't determine it.