What Windows Version Do I Have?
Checked in your browser the moment this page loads. Nothing is uploaded, and where your browser genuinely cannot tell, this page says so instead of guessing.
Checking…
You appear to be running
Check it yourself in five seconds
Whatever a website reports, the authoritative answer is on your own machine, and it is quicker to reach than most people expect. Use whichever row fits what you need.
| What you want | Do this | What you get |
|---|---|---|
| Version and build, fastest | Windows + R, type winver, Enter | Edition, feature update and full build number |
| Version plus hardware | Settings → System → About | The same, plus RAM, processor and 64-bit or 32-bit |
| The number only, scriptable | PowerShell: [System.Environment]::OSVersion.Version | The raw build number, useful in scripts |
| Everything, for support tickets | Command Prompt: systeminfo | A full report including install date and patch level |
winver is the one to remember. It has shipped with every version of Windows for thirty years, it needs no administrator rights, and it opens instantly.
Why your browser usually cannot tell Windows 10 from Windows 11
This surprises people, so it is worth explaining properly rather than hiding behind a confident-looking answer.
Every browser sends a User-Agent string describing itself and the operating system. For years that string carried the Windows version, and websites read it. Then browser makers froze it deliberately, as a privacy measure: the more precisely a browser describes the machine, the easier that machine is to fingerprint and track across sites. So Chrome, Edge and Firefox all still report Windows NT 10.0 today, on Windows 11 exactly as on Windows 10. There has never been a Windows 11 User-Agent string, and there is not going to be one.
The replacement is User-Agent Client Hints. Instead of broadcasting everything to everyone, the browser hands over specific details only when a page asks for them. One of those details is platformVersion, and Microsoft publishes the mapping: on Windows, a major version of 13 or above means Windows 11, 1 to 10 means Windows 10, and 0 means Windows 7, 8 or 8.1. That is what this page reads, and it is accurate.
The catch is support. Client Hints exist in Chromium browsers, which means Chrome, Edge and Opera can tell; Firefox and Safari cannot. On those browsers there is no signal at all, and any site that shows you a confident answer anyway is guessing from the frozen string, which means it tells every Windows 11 user they are on Windows 10. This page reports what it actually knows and stops there.
Two things no website can ever see
Even at its most capable, Client Hints reports Windows 11 as a single thing. It does not expose which feature update you are on, so nothing on the web can separate 23H2 from 24H2, 25H2 or 26H1. It also does not expose your edition, so Home and Pro are indistinguishable. Both are in winver.
Version, build and edition are three different things
These get used interchangeably and they mean quite different things, which matters when you are checking whether a fix applies to you.
| Term | Looks like | What it tells you |
|---|---|---|
| Edition | Home, Pro, Enterprise, Education | Which features you have, such as BitLocker or Group Policy |
| Version (feature update) | 24H2, 25H2, 26H1 | Which yearly release you are on. This sets your support dates |
| Build number | 26100.9445 | Before the dot, the feature update. After it, how many monthly patches you have installed |
So two machines can both say “Windows 11 24H2” and still differ: the one on 26100.9445 has this month's security fixes, the one on 26100.4061 does not. When a support article says a problem was fixed in a particular build, it is the number after the dot that decides whether you have the fix.
Is your version still getting security updates?
This is the part most version-checkers leave out, and it is usually the reason someone is checking. Once a version passes its end-of-servicing date it stops receiving security updates entirely — the machine keeps working and quietly stops being patched.
Find your build number's prefix in the first column. Dates are Microsoft's, from its Windows release health pages, and the countdown below is calculated fresh each time this page loads.
| Build starts with | Version | Latest build | Security updates until | Status |
|---|---|---|---|---|
28000 |
Windows 11 26H1 | 28000.2954 |
14 March 2028 | Supported |
26200 |
Windows 11 25H2 | 26200.9445 |
12 October 2027 | Supported |
26100 |
Windows 11 24H2 | 26100.9445 |
13 October 2026 | 34 days left |
22631 |
Windows 11 23H2 | 22631.7582 |
10 November 2026 | 62 days left |
19045 |
Windows 10 22H2 | 19045.7725 |
14 October 2025 | Ended 330 days ago |
Dates as published by Microsoft for the Home and Pro editions; Enterprise and Education releases are often serviced longer. Verified against Microsoft's Windows release health on 9 September 2026.
If your build number is behind and Windows Update will not move it forward, the failure usually surfaces as a numbered error rather than an explanation. Our Windows error code index maps the common ones to their actual cause, and KB5043080 is worth checking specifically, because it is a prerequisite that silently blocks later Windows 11 updates when it is missing.
If you are on Windows 10
Windows 10, version 22H2 reached end of servicing on 14 October 2025, so it no longer receives ordinary security updates. Microsoft has offered Extended Security Updates to some users; whether your device qualifies, and for how long, is set out on Microsoft's own Windows 10 support page rather than guessed at here. If your build starts 19045 and you are not enrolled in that programme, your machine is not being patched.
Questions
Why can this page not always tell Windows 10 from Windows 11?
Because browsers stopped reporting it. Both versions identify themselves as Windows NT 10.0 in the classic User-Agent string, and browser makers froze that value deliberately for privacy reasons. The only reliable signal is User-Agent Client Hints, which Chrome, Edge and Opera support but Firefox and Safari do not. On those browsers no website can tell the difference, so this page says so rather than guessing.
Can a website see which Windows 11 feature update I am on?
No. Client Hints reports Windows 11 as a single platform version and does not distinguish 23H2 from 24H2, 25H2 or 26H1. It cannot see your edition either, so no site can tell Home from Pro. winver takes about five seconds and gives you both exactly.
What is the difference between the version and the build number?
The version is the feature update, written as a year and a half, such as 24H2. The build number is the precise code, such as 26100.9445: the part before the dot identifies the feature update, the part after it counts the monthly patches installed since. Support dates are set by the version; the build tells you how current your patches are.
Is Windows 10 still getting security updates?
Windows 10, version 22H2 reached end of servicing on 14 October 2025, so it no longer receives ordinary security updates. Microsoft has offered Extended Security Updates to some users; check Microsoft's Windows 10 support page for whether your device qualifies and for how long.
Is anything about my computer sent to a server?
No. The check runs inside your browser and this page has no backend. Nothing about your device is transmitted, logged or stored.
It says Windows 11 but I am sure I have Windows 10. What now?
Trust winver over any website, including this one. Browser-reported values can be changed by privacy extensions, spoofing settings and some managed-device policies. Press Windows + R, type winver, and what that box says is what you are running.
Related tools
Browse all Sigma Wire tools - every free tool on the site, grouped by category.