Check your Windows version, edition and build number

"Which Windows is this?" comes up all the time: when an app lists its requirements, when you pick the right update, or when support asks for details. The answer has three parts: the version (for example Windows Server 2022), the edition (Standard, Datacenter, Pro) and the build number, which shows how up to date the system is. This guide shows three quick ways to find them.

Before you start

• Sign in to your server over Remote Desktop at 203.0.113.10:3389, with the details from your VPS provider's control panel.
• No admin rights are needed for any command in this guide.

Version, edition and build explained

• Version or product: the Windows family, such as Windows Server 2019, 2022 or 2025, or Windows 10 or 11 on an Admin RDP desktop.
• Edition: the feature level, such as Standard or Datacenter on a server, or Pro on a desktop.
• Feature release: desktop Windows also has a release name such as 22H2 or 24H2.
• Build number: written as 20348.2849, for example. The first part (20348) identifies the Windows release. The part after the dot, called the update build revision (UBR), goes up with each monthly cumulative update.

Common base builds you may see:

• Windows Server 2019: 17763
• Windows Server 2022: 20348
• Windows Server 2025: 26100
• Windows 10 22H2: 19045
• Windows 11 24H2: 26100

Method 1: winver

The fastest way, with a window you can screenshot:

1. Press Win + R.
2. Type winver and press Enter.

The About Windows box shows the product name, the version (on desktops) and a line such as OS Build 20348.2849. Click OK to close it.

Method 2: systeminfo

systeminfo works in Command Prompt and PowerShell and prints a full summary. To show only the lines you need:

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

Example output:

OS Name:                   Microsoft Windows Server 2022 Standard
OS Version:                10.0.20348 N/A Build 20348
System Type:               x64-based PC

OS Name gives the product and edition together. System Type tells you the architecture, which you need when you download updates or installers. The full systeminfo output also lists the install date, last boot time, memory and installed hotfixes.

Note that OS Version shows only the base build, not the revision after the dot.

Method 3: PowerShell

Get-ComputerInfo returns detailed data. Pick the useful properties:

Get-ComputerInfo -Property OsName, OsVersion, OsBuildNumber, OsArchitecture, WindowsEditionId

It can take a few seconds to run.

To get the full build number including the revision, read it from the registry:

$cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
"$($cv.CurrentBuild).$($cv.UBR)  $($cv.EditionID)  $($cv.DisplayVersion)"

Example output:

20348.2849  ServerStandard  21H2

Why the build number matters

• Updates: Microsoft lists the build each cumulative update brings you to. Comparing your build with that list tells you whether the latest update is installed. See Install a Windows update manually from the Update Catalog.
• App support: many apps state a minimum Windows version or build. Some trading platforms,.NET runtimes and drivers will not install on older builds.
• Troubleshooting: a known bug often affects only certain builds. Knowing yours tells you whether a fix applies.
• Support tickets: including the edition and full build in a support ticket saves a round of questions.

Check it works

Run winver and the PowerShell registry command. The base build and the revision should match in both. If you just installed updates and the revision has not changed, the server may still need a restart.

Troubleshooting

• Get-ComputerInfo is slow or shows blank fields: some properties need WMI data that takes time to collect. Use systeminfo or the registry command instead.
• Build revision did not change after updating: restart the server, then check again. Cumulative updates finish installing during the reboot.
• Product shows "Evaluation": the edition is an evaluation copy. Check activation with slmgr /dlv and contact support if you expected a full licence.
• Windows 11 shows as Windows 10 in a script: read CurrentBuild instead of ProductName. Builds 22000 and above are Windows 11.

Next steps

• Keep the build current: Windows Update and server maintenance.
• Choosing a version for a new server: Choose a Windows Server version.