I have lost count of how many times I have had to ask myself what Windows version I was running. The answer lives three keystrokes away, but the question gets asked for a reason: a piece of software wants to know, a support thread asks for your build number, or a Windows Update cycle is doing something strange and you need to figure out which feature release you are actually on. This is the post I wish I had bookmarked the first time I had to find out.
There are three different answers hiding under the same question. Microsoft calls them edition (Home, Pro, Enterprise, Education), version (the feature release label like 24H2 or 23H2), and OS build (the precise number that ends in something like 26100.x). Knowing which is which matters, because they answer different questions. A driver installer wants your architecture. A support tech wants your build number. A compatibility checker wants your edition.
I am going to walk through the three ways I use to pull all of this out of Windows, in the order I reach for them. None of them require admin rights and none of them need anything installed.
The fastest way: the winver dialog
The single fastest way is the one most people forget exists. Press Win+R, type winver, press Enter. A dialog opens with the Windows edition name at the top, the version label (like Windows 11), and the OS build number underneath.
I use this when I am on the phone with a relative, when I have just rebooted into a fresh box, or when I am in a hurry and need to paste a version number into a forum post. The dialog is small, it does not load any GUI shell, and the value is right there in the title bar of the popup.
There is one catch. The winver dialog shows the consumer-facing version label, like 23H2, but it does not surface the edition details the way Settings does. If I need to confirm whether I am on Pro or Home specifically, I have to fall back to one of the other methods. winver is the right tool when I need the version and build. It is the wrong tool when I need the edition.
For most troubleshooting, that is fine. In my experience, the version label and OS build number cover the great majority of the questions I get asked about Windows installations.
The most thorough way: System Information (msinfo32)
When I want everything in one place, I open System Information. The official name is msinfo32 and you can launch it from the Start menu or by typing msinfo32 in the Run dialog. The window that opens has a tree on the left and a key-value list on the right.
Under System Summary, the fields that matter for the version question are:
- OS Name. The major release and edition, in a format like
Microsoft Windows 11 Pro. This is the one field that tells you both pieces at once. - Version. The Windows internal version number, like
10.0.22631. This is not the consumer-facing label. If you need the 23H2-style label, usewinveror Settings. - OS Configuration and Build Type. Useful if you need to know whether you are on a workstation or domain-joined install.
- System Type.
x64-based PCfor 64-bit,x86-based PCfor 32-bit. This is the one field that tells you which architecture you are running.
System Information is also where you go when you need to confirm whether a specific hotfix or update is installed, when a support tech asks you to dig past the headline version number, or when you are filing a bug report and want everything captured in one screenshot.
I keep the System Information window open in the background when I am doing a multi-step troubleshooting session. It saves me the round-trip of running three separate tools.
The cleanest way for normal users: Settings
If I want the same information with a friendlier interface and zero commands, I open Settings. On Windows 10 or 11, the path is Start, Settings, System, About. The About page shows three sections that together cover the whole question.
Under Windows specifications, you will see:
- Edition. Windows 11 Pro, Windows 10 Home, whatever you are running.
- Version. The feature update label, like 24H2 or 23H2.
- OS build. The precise build number, with the revision number appended.
Just above that, under Device specifications, you will see System type, which tells you whether you are on x64 or x86.
Settings is the path Microsoft wants you to use and the path that survives across Windows releases. It does the same job as winver and msinfo32 for most users, and it has the advantage of being discoverable without knowing any commands.
If you are walking a non-technical user through a version check over the phone, Settings is almost always the right starting point. They can find it without a cheat sheet, and the values are spelled out in plain English.
A bonus: the command line
For the times when I am already in a terminal, I reach for systeminfo. Specifically:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
That returns the installed Windows name and the version/build number in a copyable text format. It is the same data as the System Information GUI, just rendered for a terminal. I use this when I am SSHed into a box (a real use case, not just a thought experiment), when I am scripting a fleet-wide inventory, or when I need to paste the output into a support ticket.
You can also launch winver or msinfo32 directly from the terminal by typing either command. Both open their respective windows instantly, which is useful when you are already in the Run dialog or a PowerShell prompt and want to skip the Start menu trip.
What the labels actually mean
The most common confusion I see is between the four labels. They look interchangeable but they answer different questions:
- Edition tells you which feature tier you are running. BitLocker and Group Policy are only on Pro, Enterprise, and Education. If a piece of software specifies a tier requirement, this is the field to check.
- Version is the feature update label, like 24H2 or 23H2. Windows 10 and 11 both use this half-year naming. This is what to check when troubleshooting update-related behavior or confirming you have a recent feature release.
- OS build is the precise build number with revision, like
26100.xor22631.x. This is what to send to support, because it identifies the exact state of your installation including cumulative updates. - System type is the architecture: x64 or x86. This matters when downloading drivers and software that have separate 32-bit and 64-bit packages.
A complete answer to the version question reads like this: Windows 11 Pro, version 24H2, OS build 26100.x, 64-bit operating system. That single line covers every question a piece of software or a support tech is likely to ask.
Trade-offs
Each of the three tools has a real downside that does not always show up in a how-to guide.
winver is fast but it is read-only and partial. If you need the edition label spelled out (Pro versus Home versus Enterprise), it does not give you that reliably. For a quick build number, it is the right tool. For anything else, move on.
System Information (msinfo32) gives you everything in one place but it loads a treeview GUI shell, which is slower to open and harder to navigate than Settings. If you are screen-sharing and trying to point at a single field, the layout is not as clean as the Settings About page.
Settings is the most discoverable but it is also the slowest path of the three, because it requires clicking through three menu levels. If you already know the shortcut, winver or msinfo32 is faster. Settings earns its keep when the user does not know the shortcut.
If I am doing this for myself, I reach for winver first. If I am walking someone else through it, I send them to Settings. If I need the full picture in one window, System Information is the right pick. None of the three are bad choices. They are different tools for different moments.
Bottom line
The Windows version question is not actually one question. It is four questions stacked on top of each other: edition, version, build, architecture. Knowing which one you actually need is half the answer. The other half is knowing which tool surfaces it cleanly.
For most users, Settings at System, About is enough. For most techs, winver plus a quick look at systeminfo covers it. If you can remember winver exists, you have a head start on most of the Windows troubleshooting questions that start with “what version are you on”.