How to Check Your Windows 10 Version

Quick answer: how to see your Windows 10 version right now

To check your Windows 10 version and build number quickly, open Settings > System > About. The edition (such as Windows 10 Home or Windows 10 Pro) and the OS build are listed under Device specifications and Windows specifications. Alternatively, press Win+R, type winver, and press Enter to open the About window, which shows the edition and build number. These two pieces of information together identify the exact version of Windows 10 your device is running.

Why knowing your Windows 10 version matters

The Windows 10 version (for example, 21H2 or 22H2) and the OS build number tell you which feature update you have installed and how up to date your device is with security and quality fixes. This information affects compatibility with apps and drivers, eligibility for new features, and the ability to receive future updates. It is also commonly requested for troubleshooting, support, and enterprise deployment planning.

What the version and build number actually mean

Windows 10 uses codenames such as 21H2 and 22H2 to refer to feature updates released roughly once per year. Each feature update has a base build number, and later builds increment as quality updates and security patches are delivered. The edition indicates the feature set and supported scenarios (Home, Pro, Education, Enterprise). Knowing both the edition and the exact build number provides a precise snapshot of your system state.

Edition names and their intent

• Windows 10 Home: consumer-focused features and tight integration with Microsoft account and cloud services
• Windows 10 Pro: additional business and IT management capabilities such as domain join, BitLocker, and group policy
• Windows 10 Education and Enterprise: specialized tools for institutions and large organizations with additional management and deployment options

How builds are numbered and tracked

The build number is a seven-digit number (for example, 19044). The first four digits indicate the release branch (such as 1904x for the 20H2 release), while later digits reflect cumulative updates. Comparing your build number to the official build list for a given release helps confirm whether you are on the latest available build for your channel (Dev, Beta, or Stable).

Method 1: Use Settings to check Windows 10 version and build

This method works from the Start menu and is applicable to all supported Windows 10 devices.

1. Open Start and select Settings (or press Win+I).
2. Go to System > About.
3. Under Device specifications, confirm the System type (32-bit or 64-bit) and Processor.
4. Under Windows specifications, review the Edition and the OS build.

The combination of Edition and OS build tells you exactly which version and build of Windows 10 you are running.

Method 2: Use winver to check version and build quickly

The winver command opens a compact dialog that shows the edition and build number without opening the full Settings pane.

1. Press Win+R to open Run.
2. Type winver and press Enter or select OK.
3. In the About Windows window, you will see the edition and the build number.

This method is fast and useful when you only need to confirm the version and build without navigating deeper into Settings.

Method 3: Check version with Command Prompt and PowerShell

For scripting, remote checks, or copying results, use Command Prompt or PowerShell.

Command Prompt and PowerShell using systeminfo

Open Command Prompt or PowerShell and run:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

This prints the OS name and version line, including the build number.

PowerShell using Get-ComputerInfo

Run in PowerShell:

Get-ComputerInfo | select CsWindowsProductName, OsBuildNumber

This returns the product name (edition) and the build number in a concise format.

Optional: Check your update history to verify which build you are on

Reviewing installed updates helps correlate the build number with the cumulative updates applied to your system.

1. Open Settings > Windows Update > Update history.
2. Look for the latest Quality Update or Feature Update entry to see the date and associated build context.

While update history is not always exhaustive, it can confirm when a particular build was installed and whether recent quality updates have been applied.

Build numbers, features, and approximate release timeline (reference)

The table below links notable Windows 10 feature updates to their typical release periods and example build numbers. Builds will vary depending on the channel (Stable, Beta, Dev) and cumulative updates applied after the feature release.

Checking update channels and expected build ranges

Windows 10 delivery channels determine how soon you receive new builds. The Stable (Release) channel receives updates weeks after Beta and Dev. If you are on the Stable channel, your build will typically be a few weeks behind Dev and may lag behind the latest public build numbers until cumulative updates are pushed out.

Dev and Beta channels

• Dev channel (formerly Fast ring): receives pre-release builds, build numbers may jump ahead and include experimental features.
• Beta channel (formerly Slow ring): receives near-release quality builds, build numbers are closer to the next stable release.
• Stable channel: receives updates after thorough testing, build numbers are generally behind Dev and Beta but widely deployed.

What to do if your build is outdated

If you are concerned about being behind, check for updates first, then consider whether moving to a different delivery channel is appropriate for your device. Channels can be changed, but this can introduce instability and is generally best avoided on primary devices unless you are testing features.

1. Open Settings > Windows Update > Advanced options > Choose how updates are delivered.
2. Switch channels with care and anticipate potentially more frequent update cycles and occasional issues on pre-release rings.

Checking version on a domain-joined or enterprise-managed device

In managed environments, policies and update rings can affect which build and edition your device reports. Admins may restrict update channels or defer feature updates. Use the same Settings > About paths or ask your IT support for the intended configuration if results differ from expectations.

Troubleshooting: winver or Settings shows a different build than expected

If winver or Settings shows a build that seems inconsistent with your update history, it may be due to cumulative updates incrementing the build, a pending restart, or being on a different channel than intended. Check Windows Update settings, review the Delivery Optimization and Windows Update logs if needed, and confirm the active update ring. As a baseline, compare your edition and build number to the official build list for your channel.

Common terms and glossary

OS build

The seven-digit number that identifies the exact cumulative state of Windows 10 at a point in time.

Feature update

A major semi-annual update that adds new features and a new base build (e.g., 21H2, 22H2).

Cumulative update

Regular quality and security rollups that increment the build number without changing the feature update designation.

Delivery channel

The ring that determines how quickly you receive updates: Dev, Beta, or Stable.

Practical checklist for support and documentation

• Record both the edition and the OS build number when logging support requests.
• Verify update channels before changing rings or installing manual updates.
• For enterprise deployments, track the baseline build number alongside the image and applied updates.
• Periodically check for updates and confirm you are on the expected delivery channel for your environment.

Summary

You can check your Windows 10 version by opening Settings > System > About to read the edition and OS build, by pressing Win+R and running winver, or by using Command Prompt or PowerShell commands such as systeminfo or Get-ComputerInfo. The edition tells you the feature set, and the OS build identifies how up to date your device is with cumulative updates. Knowing these two values helps with troubleshooting, compatibility checks, and planning updates across devices.