The fastest way to find out is Windows+R, type winver, press Enter — a small dialog opens showing your edition and version number, and on Windows 11 the build number too. That's the answer for almost everyone reading this. The method never changed across Windows 7, 8.1, 10, and 11: the same three-word command works on all four. What changed is what the dialog shows you. Windows 7 reported no build number in that box; Windows 11 reports a five-digit build, which now matters because Microsoft ties feature updates to build numbers, and several popular games and drivers in 2025–2026 refuse to launch below specific ones.
If the Run box is blocked by policy — common on work laptops — the Settings app reaches the same information in about four clicks. And if you're on a machine you can't log into normally, there's a method that needs no login at all.
One boundary up front: "version" means two different things to two different people. IT staff mean the build number (e.g., 26100). Everyone else means "Windows 11" or "Windows 10." This article gives you both, plus how to tell which one is actually installed.
Reading the winver Dialog: Every Field It Shows and Which One Matters
Press Windows+R, type winver, hit Enter. A dialog titled "About Windows" appears with a logo, a product name, a version line, and — on Windows 10 and 11 — an OS build line. On Windows 11 24H2 the version reads 24H2 and the build reads something like 26100.1742. The number before the dot is the build family; the number after is the patch revision.
The single most useful field is the build, because edition names lie by omission. Windows 10 and Windows 11 can both be "Pro," and the build is what tells you whether you're on 22H2 (Windows 10's final feature update, released October 2022) or a Windows 11 release. Microsoft's lifecycle documentation is organized by build, and support end dates attach to builds, not to the word "Pro."
On Windows 7 the dialog shows a version like 6.1 (Build 7601: Service Pack 1). That 6.1 is the internal kernel version — Windows 7 is NT 6.1, Windows 8.1 is NT 6.3, Windows 10 and 11 both report NT 10.0. Don't let the 10.0 on a Windows 11 machine confuse you; Microsoft kept the kernel version at 10.0 for compatibility and distinguishes the products by build number instead. Windows 11 starts at build 22000.
The dialog also carries the edition name ("Windows 11 Pro," "Windows 10 Home") and, on older systems, the registered owner and service pack. Copy the build number down before calling support — it's the first thing any technician asks for and the one thing you can't guess from the sticker on the case.
Four Built-In Checks Compared: Run Command, Settings, System Information, and Command Prompt
| Method | Exact path | What it reports | Works when Settings is blocked | Time |
|---|---|---|---|---|
| winver | Windows+R → winver | Edition, version, build | Yes | ~5 seconds |
| Settings | Settings → System → About | Edition, version, build, processor, RAM | No | ~15 seconds |
| System Information | Windows+R → msinfo32 | Build, BIOS version, OS name, install date | Yes | ~10 seconds |
| Command Prompt | cmd → ver or systeminfo | Build string; systeminfo adds hotfix list | Yes | ~20 seconds |
Each route reaches the same underlying data, but they fail differently. Settings is the friendliest and the most locked-down — managed devices often gray out the About page or hide Settings entirely behind a policy. msinfo32 gives you the BIOS version and original install date, which winver never shows and which matter when you're diagnosing why an update keeps failing (an outdated BIOS is a documented cause of Windows 11 upgrade blocks).
systeminfo at the command prompt is the slowest of the four, taking ten to thirty seconds as it enumerates hotfixes, but it's the only one that lists installed updates — handy when a support agent asks whether a specific cumulative update landed.
If you want a one-line answer with no clicking, ver in Command Prompt returns something like "Microsoft Windows [Version 10.0.26100.1742]." That string contains everything: kernel version, build, and revision. Paste it into a search engine and you'll land on the exact release notes.
Windows 11 vs Windows 10: Telling Them Apart When the Name Is Hidden
Microsoft removed the product name from several places people look first. The desktop wallpaper doesn't say it. The Start menu doesn't say it. winver on Windows 11 shows "Windows 11" in the logo area but the text line above the build can be easy to skim past. The most reliable tell is the build number: anything 22000 or higher is Windows 11; 19041 through 19045 is Windows 10.
A second tell sits in Settings → System → About, where Windows 11 lists "System type" as x64-based or ARM-based and Windows 10 uses nearly identical wording — so that field won't help. Look instead at the version line: Windows 11 releases are named 21H2, 22H2, 23H2, and 24H2, while Windows 10 ended at 22H2. If you see 22H2, check the build: Windows 10 22H2 is build 19045, Windows 11 22H2 is build 22621. Same label, different product.
Why does the distinction matter beyond curiosity? Windows 10 reached end of support on October 14, 2025, per Microsoft's lifecycle page. A machine still reporting build 19045 after that date receives no security patches unless it's enrolled in Microsoft's Extended Security Updates program, which Microsoft sells to consumers on a yearly basis. That's the practical consequence of the check: a Windows 10 result in late 2026 is a decision point, not a trivia answer.
If the About page shows "Windows 10" but the build is 22000-something, the label is stale or the machine was upgraded in place and the registry string didn't refresh. Trust the build number over the name every time.
Checking the Version Without Logging In: The Lock Screen and Recovery Route
When a PC won't boot to the desktop, or you're handed a machine with no password, the version is still discoverable. On the Windows sign-in screen, click the power icon in the corner, hold Shift, and click Restart. The machine reboots into the Windows Recovery Environment — a blue menu — where you choose Troubleshoot, then Command Prompt. Type ver there. It reports the build of the installed OS, not a stripped-down recovery image, so the answer is accurate.
This route has a real limitation: on some corporate machines, the recovery environment is disabled by policy or requires a BitLocker recovery key before the command prompt appears. If you're prompted for a 48-digit key, you're not getting past it without the key — that's the failure case, and it's more common than people expect on laptops with device encryption switched on by default.
A gentler no-login option exists on the sign-in screen itself: the bottom-right corner of some Windows 10 and 11 builds displays the OS build in small text. It's inconsistent across builds and disappears on touch-first layouts, so treat it as a bonus, not a method.
For a machine that boots but whose owner has forgotten which release it's on, the System Information route (msinfo32) works from a standard user account without admin rights and shows the OS name, version, and build on its first screen. No elevation prompt appears, which makes it the quietest way to check a shared or loaner computer.
The Build Number Decoder: Mapping Five Digits to a Windows Release
Windows 10 and 11 builds fall into recognizable families, and knowing the family saves a search. Windows 10's final build family is 19041–19045, all labeled 2004 through 22H2 depending on the minor revision. Windows 11's families step upward with each annual release: 22000 for the original 21H2, 22621 for 22H2, 22631 for 23H2, and 26100 for 24H2.
The revision after the dot is the patch level. Microsoft ships cumulative updates on the second Tuesday of each month — Patch Tuesday — and each one bumps the revision. A machine at 26100.1742 and one at 26100.2033 are both Windows 11 24H2, one a few patches apart. When a vendor's support page says "requires build 26100.2033 or later," the revision is the number that decides whether you qualify.
This is where the check pays off in practice. Anti-cheat systems for several multiplayer titles began enforcing minimum builds in 2024 and 2025, and graphics drivers from both major GPU vendors list minimum OS builds in their release notes. A machine that hasn't taken updates in eighteen months can be several hundred revisions behind, and the symptom is a game that crashes on launch with a generic error rather than a message saying "update Windows."
Feature updates, as distinct from cumulative patches, arrive roughly annually and change the build family. Microsoft's Windows release health page tracks known issues per build, so the five-digit number is the key to that documentation. If you're troubleshooting anything unusual, quote the full build with revision when you search — the family alone often returns results for the wrong release.
Settings App Paths by Release: Where the About Page Moved Between Windows 10 and 11
The Settings layout changed between releases, and instructions written for one version send people to a page that doesn't exist in the other. On Windows 11, the path is Settings → System → About, and the version and build sit under "Windows specifications" near the bottom. On Windows 10, the same information lives at Settings → System → About as well, but the left-hand navigation has a different shape and "About" is the last item in the System list.
Windows 8.1 has no modern Settings app in the Windows 11 sense — it has PC settings, a touch-oriented panel — and the About information there is thin. The reliable route on 8.1 is winver or the classic System control panel, reached by pressing Windows+Pause/Break or right-clicking This PC and choosing Properties. Windows 7 uses the same Control Panel route; there's no Settings app at all.
On Windows 11, one extra wrinkle: the About page shows "Installed on" as a date, which is the date of the last feature update, not the original purchase date. People read it as an age indicator and conclude a two-year-old laptop is new. The original install date is visible in msinfo32 under "Original Install Date," which is the field to trust for warranty conversations.
If the Settings app won't open at all — a known failure when the Settings package is corrupted — msinfo32 and winver still work, which is the argument for knowing more than one route. Microsoft's own support documentation lists winver as the primary method for this reason.
Using Version Info to Decide on an Upgrade, an Update, or Nothing
The check exists to drive a decision, so here's the decision tree. Build 19045 (Windows 10 22H2) after October 14, 2025: you're past end of support. Either upgrade to Windows 11 if the hardware qualifies, buy Extended Security Updates from Microsoft, or accept an unpatched machine. Microsoft's PC Health Check app reports whether the hardware meets Windows 11's requirements — TPM 2.0, Secure Boot capability, a supported CPU — and it's the authoritative test, not a blog list.
Build 22000 or 22621: you're on an out-of-support Windows 11 release. Windows 11 releases get 24 months of support for Home and Pro, so 21H2 and 22H2 are both past their end dates by late 2026. The fix is running Windows Update until the build family moves to 22631 or 26100.
Build 22631 or 26100: you're current. Nothing to do beyond normal monthly patching.
A fourth case deserves attention: builds in the 19041–19044 range. Those are Windows 10 releases older than 22H2, and they stopped receiving updates earlier than 19045 did. A machine sitting there has likely had Windows Update disabled by a third-party "optimizer" tool, which is a common cause of a PC freezing on an old build for years. Re-enabling the Windows Update service and letting it run usually resolves it, though a jump of several feature updates can take an hour or more on older hardware.
When the Check Fails: Wrong Results, Blocked Tools, and Virtual Machines
Three failure cases produce a wrong or missing answer. First, a virtual machine reports the guest OS, not the host — if you run Windows in Parallels, VMware, or Hyper-V, winver inside the VM tells you nothing about the machine you're physically sitting at. Check the host separately.
Second, Remote Desktop sessions report the remote machine's version, which is correct but easy to misread when you're troubleshooting "your" computer. If the build doesn't match what you expected, confirm you're not in an RDP window.
Third, some managed devices redirect or disable winver through Group Policy, and the Run box itself can be removed. In that case, the Command Prompt route (systeminfo) or msinfo32 usually survives, because blocking all three is rare. If every route is blocked, the device management console — Intune, for example — records the OS build for every enrolled machine, and that's the number your IT department will quote back to you.
One more edge: Windows Subsystem for Linux users sometimes run uname and get a Linux kernel string, then wonder why it doesn't match. That's the Linux kernel inside WSL, not Windows. winver on the Windows side remains the answer.
FAQ
Does the winver command work on Windows 7?
Yes, and it's the same three-word command. On Windows 7 the dialog shows a version line such as 6.1 (Build 7601: Service Pack 1) and no five-digit build family, because Microsoft didn't start using those build numbers until Windows 10. The dialog also displays the service pack, which Windows 10 and 11 dropped entirely.
Why does my PC say Windows 10 when I thought I had Windows 11?
Check the build number, not the name. Builds 22000 and higher are Windows 11; 19045 and below are Windows 10. A machine can display a stale product name after an in-place upgrade, and some third-party tools report the kernel version (10.0) as the product version, which is misleading. winver and Settings → System → About are the authoritative sources.
Can I check the Windows version without administrator rights?
Yes. winver, msinfo32, and Settings → System → About all work from a standard user account without an elevation prompt. The command systeminfo also runs without admin rights, though it takes longer. Only some recovery-environment routes require a BitLocker key or admin credentials.
What's the difference between a version and a build number?
The version is the marketing name — 22H2, 23H2, 24H2 — and the build is the five-digit engineering number, such as 26100. Feature updates change the build family roughly once a year; monthly cumulative updates change only the revision after the decimal point. Support end dates attach to the build family.
How do I know if my Windows 10 is still supported?
Windows 10 reached end of support on October 14, 2025, according to Microsoft's lifecycle page. If your build is 19045 and the date is past that, you're unpatched unless enrolled in Extended Security Updates. Microsoft sells that program to consumers by the year, and enrollment requires a Microsoft account.
Does the build number affect which games and drivers will run?
It can. Several anti-cheat systems and GPU driver installers list minimum builds in their release notes, and a machine that's skipped a year of updates can fall below them. The symptom is usually a crash or a refused install with a generic error, not a message naming the build. Updating Windows resolves it.
Can I find the version from the BIOS or a sticker on the PC?
No. The case sticker or BIOS screen shows hardware details, not the installed OS. The only exception is a Windows OEM license sticker, which names the edition the machine shipped with — that's what it originally had, not what's installed now. Always check the running system.