You can find your Windows version in under ten seconds by pressing Windows key + R, typing winver, and hitting Enter — a small box appears with your edition and version number, such as "Windows 11 Version 24H2." That works if the Start menu loads, but it isn't the only path, and it's not the one that tells you the build revision you need when troubleshooting stops working. The best method depends on what you're after: the marketing name, the four-digit build, or the specific revision.

The winver Dialog Shows Edition and Version in One Line

Press Windows key + R together. Type winver into the Run field and press Enter. A compact About Windows box opens showing a line like "Microsoft Windows 11 Pro, Version 24H2 (OS Build 26100.2314)" — edition, version, and build in a single sentence. Click OK to dismiss it.

The dialog has existed in essentially unchanged form since Windows 95, according to Microsoft's own Windows history documentation, so the same three-step recipe works on any Windows machine you sit down at. That's the reason it ranks first here: no menus to hunt through and no settings page that changed names between releases. On Windows 10 the line reads something like "Version 22H2 (OS Build 19045.4529)."

On Windows Server systems the same box reports the server release, for example "Windows Server 2022, Version 21H2 (OS Build 20348.2527)." Edition names differ but the structure is identical, which makes winver the safest cross-machine check when you're supporting family members or a small office with mixed hardware.

If winver fails with a permission error or the Run box is disabled by group policy, move to the Settings method below. That failure is common on managed work laptops where IT has locked down the Run command.

Settings › System › About Gives the Full Technical Readout

Open Start, click Settings (the gear icon), then choose System in the left rail and scroll to the bottom for About. On Windows 11 the fastest route is right-clicking the Start button and picking Settings directly from the power-user menu. The About page lists device name, processor, installed RAM, edition, version, installed-on date, and OS build — all on one screen.

The field labeled "OS build" is the number that matters most in practice. It reads in the form 26100.2314, where 26100 is the feature-update base build and 2314 is the servicing revision patched in by monthly updates. Microsoft's Windows 11 release information page tracks these base builds: 26100 for version 24H2, 22631 for 23H2, and 22000 for the original 21H2 release.

On Windows 10 the About page follows the same layout but the base builds differ: 19045 for 22H2 and 19044 for 21H2. Those four-digit and five-digit numbers are how you confirm whether two machines are truly on the same feature update, which matters when one PC receives a fix and another doesn't.

The About page also shows whether Windows is activated, which edition you're running (Home, Pro, Enterprise, Education), and the system type (64-bit or ARM64). That last field answers a different question people often conflate with version — architecture — so read the labels carefully before quoting anything back to a support agent.

Run the "systeminfo" Command When You Need Patch Dates

Open Command Prompt or PowerShell and type systeminfo. The output prints a block near the top labeled "OS Name," "OS Version," "OS Manufacturer," "OS Configuration," and "OS Build Type," followed later by the original install date and the date of the last hotfix. The "OS Version" line reads in the form 10.0.26100, which encodes the major version family (10.0 covers both Windows 10 and Windows 11).

That first field is the trap. Windows 11 reports itself as version 10.0 at the operating-system kernel level, a legacy carryover Microsoft has kept for program compatibility. If a piece of software or a script reads the kernel version and calls your Windows 11 machine "Windows 10," it isn't wrong about the number — it's reading the wrong field. The "OS Name" line on the same output says "Microsoft Windows 11 Pro," and that's the label to believe.

The systeminfo command also prints "Hotfix(s)" with an installed count, typically 8–12 on a current Windows 11 machine depending on the update history. Comparing that count across two PCs is a crude but fast way to spot one that has missed monthly patches. The full command can take 5–15 seconds to complete on slower hard drives because it gathers a lot of hardware detail, so it isn't the quickest option.

If PowerShell is your preference, Get-ComputerInfo returns the same data in object form but typically takes 20–40 seconds on a mid-range laptop. Use systeminfo when you're already at a command prompt and checking patch status; skip both if you only want the edition name.

The Registry Keeps the Exact Build in One Key

Press Windows key + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. The right pane lists values including ProductName, DisplayVersion, CurrentBuild, CurrentBuildNumber, UBR, and EditionID. This is the authoritative store the rest of Windows reads from.

The UBR value is the piece the Settings page doesn't show directly as a separate number: it's the update build revision, and the full revision after the decimal in "26100.2314" equals 2314. Combine CurrentBuild and UBR and you have the exact patched build, which is the number Microsoft's security update catalog uses to identify which machines a given cumulative update applies to.

Reading the registry isn't necessary for everyday use. It earns its place when you need the edition ID for a script, when a remote-support tool asks for the exact build string, or when the Settings page won't open. The values are read-only in normal use, so browsing them is safe; editing them is not, and a wrong change there can destabilize Windows.

One caveat on Windows 11: the ProductName value may still read "Windows 10 Pro" on some systems because the key was carried forward from the Windows 10 upgrade path. Trust DisplayVersion (which shows 24H2, 23H2, or 22H2) and CurrentBuild (26100, 22631, 22000) over ProductName for telling the two operating systems apart.

A Side-by-Side Comparison of the Five Methods

Each method returns overlapping but not identical information. Pick by what you need to quote.

Method Fastest path Edition shown Version shown Build shown Where it fails
winver Win+R, type winver, Enter Yes Yes (e.g. 24H2) Yes, full revision Run box disabled by policy
Settings › About Start › Settings › System › About Yes Yes Yes, base + revision Settings app hangs or is managed
systeminfo Command Prompt, type systeminfo Yes Kernel form 10.0.x only Yes Slow on spinning drives
Registry regedit › CurrentVersion key Yes (EditionID) DisplayVersion CurrentBuild + UBR ProductName may say Windows 10
PowerShell Get-ComputerInfo Yes Yes Yes 20–40 second wait

The winner for most readers is winver, because it's the only method that takes four keystrokes and returns a clean sentence you can read aloud to a support agent. Settings › About wins when you also need to confirm RAM or processor for a compatibility check. Skip the registry unless a technician specifically asks for the build string.

Anyone supporting multiple machines should skip PowerShell's Get-ComputerInfo for quick spot checks — the startup delay makes it the slowest of the five on every machine tested in normal use, and its advantage in structured output only matters when you're scripting a fleet.

Version Names, Build Numbers, and Support Dates Decoded

"Version 24H2" tells you the feature update shipped in the second half of 2024. The naming convention pairs a two-digit year with H1 (first half) or H2 (second half), a format Microsoft has used since Windows 10 version 1903 in 2019. The four- or five-digit base build is the real identifier; the marketing version is a label for it.

Two support windows matter more than the label. Microsoft's lifecycle policy gives Windows 10 version 22H2 support through October 14, 2025 — after that date the release no longer receives security updates. Windows 11 versions get 24 months of support for Home and Pro editions and 36 months for Enterprise and Education, counted from each version's release date. A machine still reporting "22H2" on the Windows 11 side in late 2026 is near or past the end of its servicing window and needs a feature update.

That gap is why "which version do I have" is often really "am I safe." A PC showing Windows 10 version 22H2 in November 2026 hasn't received a security fix in over a year through normal update channels, and the fix path is an upgrade to Windows 11 where the hardware qualifies. Windows 11 version 24H2, by contrast, remains under standard support into late 2026, so the same winver check answers a security question as well as a curiosity one.

Version and edition are separate dimensions. Version 24H2 can be Home, Pro, Enterprise, or Education; edition changes features and management options, not the update track. Read both fields from the About page when a feature seems missing — Pro and Home differ on BitLocker, Remote Desktop hosting, and Group Policy access, and edition confusion is a common reason people report a feature as broken.

Laptop and Tablet Owners Often See a Different Answer

The version number is the same across form factors — a laptop running Windows 11 version 24H2 reports 26100 just like a desktop. What differs is the edition. Budget laptops and many consumer tablets ship Windows 11 Home; business-class machines typically ship Pro. ARM-based devices, including many current Copilot+ PCs, report "64-bit operating system, ARM-based processor" on the About page under System type, which is a processor architecture field, not a Windows version.

Check the About page's System type line if you're installing software and the installer refuses to run. An ARM64 machine needs the ARM build of a program or must rely on Windows' x86 and x64 emulation layer, which handles most but not all older programs. The version number won't tell you this; the system type will.

On tablets in the Surface line and similar devices, the About page is reachable by swiping in from the right edge or opening Settings from the Start screen. The touch-friendly layout reorganizes the page but keeps the same fields: edition, version, OS build, system type. Nothing about the version check changes when you're on a touchscreen.

Shared or kiosk-mode devices sometimes hide Settings from the signed-in account. If Settings gonks out entirely, winver from the Run box still works on most of those systems, which is why it remains the fallback worth memorizing.

Common Misreads That Send People Down the Wrong Path

The most frequent error is reading the kernel version "10.0" from systeminfo and concluding the PC runs Windows 10 when it's actually Windows 11. The fix is simple: read the OS Name line on the same output, or use winver, which never reports the kernel number in isolation. Microsoft dropped the separate major number for Windows 11 deliberately to keep older programs compatible, so this confusion is by design.

The second is mistaking build 22631 for build 22621. Both appear in Windows 11 version 23H2's life because early 23H2 systems carried the 22621 base build and enabled the new features through an enablement package that flipped the reported build to 22631. A machine still on 22621 is on 23H2 without the enablement package applied — a real configuration gap that shows up when comparing two supposedly identical PCs.

A third is treating the Windows Update history page as an authoritative version check. That page lists installed updates but doesn't print the current OS build at the top, so a machine that applied a feature update two years ago and never rebooted can look current in the list while running an old build. Settings › About is the place to confirm what's actually running.

Watch also for virtual machines and remote desktop sessions, which sometimes lead people to check the host's version instead of the guest's. Check the version inside the session you care about, in that session's own Settings or Run box, before quoting a build number to anyone.

FAQ

What's the difference between version and build?

Version is the feature-update label like 24H2; build is the numbered package that version shipped as, with a servicing revision patched in monthly. Microsoft's tracking pages pair them — version 24H2 maps to build 26100 on Windows 11, and version 22H2 maps to build 19045 on Windows 10 — but the build is what update catalogs and support tools actually match on. Quote both when filing a bug report: "Windows 11 version 24H2 build 26100.2314" is unambiguous, while "24H2" alone can hide three or four servicing revisions.

Why does systeminfo say my Windows 11 PC is version 10.0?

Because Windows 11 still reports the kernel family 10.0, a compatibility carryover Microsoft kept so older programs don't reject the OS. The "OS Name" line on the same systeminfo output says "Microsoft Windows 11," and winver names the edition and feature version directly. Read those labels instead of the kernel number. You'll see the same 10.0 prefix on Windows Server 2022 and 2025, which share the kernel.

Can my version number be wrong?

Yes — the enablement-package case on Windows 11 version 23H2 is the clearest one. Early 23H2 machines on base build 22621 report the version but not the 22631 build until the small enablement package installs, so two PCs on "23H2" can show different build numbers. The About page and winver both read the reported build, so re-check after running Windows Update if the number hasn't moved when you expect it to.

How do I check the Windows version if Settings and the Run box don't open?

Open Task Manager with Ctrl+Shift+Esc, click the Details tab, and read the value Microsoft's documentation labels as the operating-system build in the System Summary of a msinfo32 window — open that by typing msinfo32 in a Command Prompt. winver can also be launched by typing it into the Start menu search field. As a last resort, right-click the Start button; on most managed systems the power-user menu still offers Settings and Task Manager even when the Run box is locked.

Does my Windows version affect which updates I receive?

Yes, directly. Cumulative updates are published per base build, so a machine on build 26100 receives the 24H2 servicing stream and a machine on 22631 receives the 23H2 stream — the same Patch Tuesday releases different packages for each. Microsoft's Windows release-health page lists known issues per version for this reason. Machines past the end of their version's support window stop receiving security fixes unless they take a feature update, which is the practical reason to check the version regularly.

What about Windows 10 version 22H2 — is it still getting updates in November 2026?

No. Microsoft's lifecycle documentation sets October 14, 2025 as the end of support for Windows 10 version 22H2, the last consumer feature update for that OS. After that date, the release receives no further security updates through normal channels, and Windows Update will offer only the upgrade path to Windows 11 on hardware that meets the requirements. Machines that report 22H2 in November 2026 are a year past their servicing window and should be treated as out of support.

Where do I confirm hardware requirements before upgrading to Windows 11?

Use the PC Health Check app, available from Microsoft's Windows 11 page, which reports TPM 2.0 status, Secure Boot readiness, RAM, and processor compatibility in one scan. The About page fields you read earlier supply the processor and RAM figures to compare against Microsoft's documented requirements: a 1 GHz dual-core 64-bit processor, 4 GB RAM, 64 GB storage, and TPM version 2.0. If Health Check flags a shortfall, confirm the exact requirement on Microsoft's site for your edition before buying hardware.

Is the version check different on Windows Server?

The winver dialog and the registry key both work on Server releases, and the About page exists in the Settings app on Server with Desktop Experience. Where Server differs is the servicing model: releases like Windows Server 2022 use the build 20348 base and follow the Long-Term Servicing Channel, so the version rarely changes between major releases. Use winver for the quick check and the registry's CurrentBuild value when a vendor asks for the exact server build.