Check edition, version, and build at a glance
To know what version of Windows 10 you are using, you need three pieces of information: the edition (such as Home or Pro), the version number (feature update released roughly twice a year), and the OS build (a more specific internal number tied to updates and fixes). Each identifier answers a different question and helps support, troubleshooting, or compatibility checks. Use the methods below to find all three reliably.
Why edition, version, and build matter
Edition affects included apps and feature availability; version indicates major updates like 21H2 or 22H2; build is a finer revision used by support tools and developers. Together they give a complete picture of what you are running.
- Edition: Home, Pro, Education, Enterprise; feature and policy differences.
- Version: Feature update identifier such as 21H2 or 22H2.
- Build: Internal number like 19044.xxx used for debugging and support.
Match your method to your access and needs
Pick the approach that suits your current access and comfort level. Simple graphical paths are fastest on a working desktop; running commands from PowerShell or Command Prompt is precise and quick for scripts or remote checks; System Information offers a concise report; and Verifying file properties helps when only Explorer is available.
- Working desktop: Settings or System icon in Control Panel.
- Admin scripts or remote checks: PowerShell and systeminfo commands.
- Quick summary without opening Settings: System dialog (winver).
- Low-level verification: File properties of system binaries.
Method 1: Use Windows Settings
This is the most straightforward, user-friendly route on a working Windows 10 desktop.
- Open Settings (Win+I).
- Go to System > About.
- Under Device specifications, note System type. Under Windows specifications, check Edition, Version, and OS build.
Edition will show Home or Pro (and sometimes Education or Enterprise). Version will display a label like 21H2. OS build is a numeric value such as 19044.
Method 2: Use winver to see edition and build quickly
A fast graphical command to confirm edition and OS build without opening multiple panels.
- Press Win+R, type winver, and press Enter.
- In the dialog that appears, you will see the edition and OS build number.
This does not show the semi-annual channel label used in Version (such as 21H2) in all builds, so follow up with Settings or SystemInfo if you need that detail.
Method 3: Use System Information (msinfo32)
System Information aggregates key identifiers in a concise report useful for support or documentation.
- Press Win+R, type msinfo32, and press Enter.
- In the System Summary, check Operating System Name for edition and System Type for architecture.
- Look at OS Version for build number, often shown as a full string including the version label.
Method 4: Use Command Prompt or PowerShell
Command-line queries are helpful for scripting, remote sessions, or when the GUI is not available.
Using systeminfo
Open Command Prompt and run systeminfo. The output includes OS Name (edition), OS Version (version and build), and System Type. Example lines you will see: OS Name: Microsoft Windows 10 Pro, OS Version: 10.0.19044 N/A Build 19044.
Using PowerShell
Open PowerShell and run Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber. This returns the edition, version, and build in a clear format. For a direct registry read, you can also query (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentVersion and (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').ReleaseId.
How to interpret the version label (e.g., 21H2, 22H2)
Windows 10 semi-annual channel releases carry a year and half designation. The first two digits are the year; the letters indicate the half (H1 or H2). For example, 21H2 means the feature update released in the second half of 2021. Version alone does not indicate whether you are on the latest update; you also need the build number to see if you include the most recent security and cumulative fixes.
If you are on an LTSB or LTSI branch, identifiers differ and are typically managed by organizations; those versions may not use the H1/H2 naming. For general users on public releases, focusing on edition, version label, and build covers most needs.
What to do if your build is lower than expected
Builds can lag because updates are delivered over time, and some organizations pause feature updates. If your build seems behind, check for updates: Settings > Update & Security > Windows Update > Check for updates. Ensure Automatic updates is enabled if you want to stay current. For Pro users, you can defer feature updates and use Windows Update for Business policies; these settings can delay build receipt without changing your edition or version label.
When to rely on each identifier
Different scenarios call for specific identifiers. Use the table below to decide which to prioritize.
| Identifier | Best used for | Caveats |
|---|---|---|
| Edition (Home, Pro) | Knowing included features and policies | Does not indicate update level or build |
| Version label (21H2, 22H2) | Identifying feature update channel | Does not reveal cumulative fixes applied |
| Build number (19044.xxx) | Precise update level, support, compatibility | Changes frequently; must be checked after updates |
Extra checks when standard reads are unclear
If winver, Settings, and systeminfo seem inconsistent, verify from file properties. Locate the file C:\Windows\System32\kernel32.dll (or explorer.exe), right-click it, choose Properties, then the Details tab. The File version and Product version fields often align with the build reported by support tools. Compare these values with the OS build shown in Settings to ensure no display or policy discrepancy is affecting your readings.
Summary checklist you can use now
- Open Settings > System > About to see Edition, Version, and OS build together.
- Press Win+R, type winver, and press Enter for edition and build at a glance.
- Run systeminfo in Command Prompt or PowerShell to capture edition, version, and build in one output.
- Use the table to choose the right identifier for your task: feature support, app compatibility, or update tracking.
- If unsure, cross-check with kernel32.dll file properties when GUI reports look inconsistent.
With these steps, you can reliably determine your Windows 10 edition, version label, and build number—enabling accurate support, compatibility checks, and informed update decisions over time.