You have Windows 11 if your taskbar icons sit centered at the bottom of the screen and Settings shows a build number starting with 22 or 26. You have Windows 10 if the taskbar is left-aligned by default and the build starts with 19. The fastest check is to press Windows key + R, type winver, and press Enter; the dialog that opens names your version and build in one line.

That covers most people. But "which Windows do I have" has a second meaning that trips up millions of users every year: people running Windows 10 who believe they have Windows 11, people on an old build who think a feature update installed, and people who bought a machine advertised with one edition and received another. This guide explains how Windows versions actually work, why the version string is more layered than it looks, and how to read every number Microsoft throws at you.

How Windows version identity is layered

Windows does not have a single version number. It has at least five identifiers that can each be "the version" depending on who is asking. The marketing name (Windows 11) is what you see in ads. The release version (24H2) is what you see on the download page. The build number (26100) is what engineers and update servers use. The edition (Home, Pro, Enterprise) determines which features exist on your machine at all. The architecture (x64, ARM64) determines which software will even launch.

These layers move at different speeds, and that mismatch is the source of most confusion. The marketing name changes roughly every three years. The release version changes annually. The build number changes every Patch Tuesday, sometimes twice a month. The edition almost never changes after purchase. So a machine can be "Windows 11" for years while its build number advances by hundreds.

The practical consequence: when a support article or a download page asks for your version, you need to know which layer it wants. A driver page asking for "Windows 11 24H2" wants the release version, not the marketing name. An enterprise licensing portal asking for "Windows 11 Pro" wants the edition. A troubleshooting forum asking for "your build" wants the five-digit number. Giving the wrong layer is why so many support threads stall on the first reply.

Reading the version string correctly

The winver dialog is the authoritative source because it pulls directly from the registry keys that Windows itself uses. It shows four things: the marketing name, the release version, the build number, and the edition. The Settings app shows the same data under System > About, plus the OS build with the update revision appended in parentheses, like 26100.2314. That four-digit suffix after the dot is the update revision, not a separate version.

Here is what a typical Windows 11 Pro machine reports, and what each field means:

Field Example value What it tells you Who cares
Marketing name Windows 11 The product family Buyers, support scripts
Release version 24H2 The annual feature update Driver and app downloads
Build number 26100 The engineering baseline Update servers, IT tools
Update revision .2314 The monthly patch level Security audits
Edition Pro The feature tier Licensing, remote desktop, BitLocker
Architecture x64 The CPU instruction set Software installers

The comparison that matters most is between the release version and the build number, because people routinely conflate them. Windows 11 24H2 is build 26100. Windows 11 23H2 is build 22631. Windows 11 22H2 is build 22621. Windows 10 22H2 is build 19045. If someone tells you their build is 19045, they are on Windows 10, no matter what the sticker on their laptop says. This single mapping resolves most "which Windows do I have" disputes in one step.

A counterintuitive detail that surprises even experienced users: the build number can go backward after a major update on some hardware. A machine that rolls back from 24H2 to 23H2 after a failed feature update will show 22631 again, and Windows will report the rollback as a successful recovery, not a downgrade. The version history in Update History preserves the record, but the live version string will not. If you are auditing machines remotely, you cannot trust a single snapshot.

Why the taskbar and Start menu are unreliable signals

The most common heuristic, the centered taskbar, is a setting, not a version marker. Windows 11 ships with centered icons, but the alignment can be switched to left in Settings > Personalization > Taskbar in about four clicks. Millions of Windows 11 users run a left-aligned taskbar specifically because they prefer it. Conversely, third-party shells like ExplorerPatcher and StartAllBack can make Windows 11 look like Windows 10, and Stardock's Start11 can move the Windows 10 Start menu anywhere. Visual inspection fails on both ends.

The Start menu is a slightly better signal, but only slightly. Windows 11 removed live tiles, moved search to the top, and replaced the app list with a pinned grid. Windows 10 keeps live tiles on the right and an alphabetical list on the left. But the grid can be rearranged, and the tiles can be unpinned, so a heavily customized Windows 10 Start menu can resemble Windows 11's. The only visual cue that survives customization is the rounded corners on window frames, and even those are theme-dependent.

The reliable visual marker is the context menu. Right-click any file in File Explorer. Windows 11 shows a compact menu with icon-only cut, copy, rename, and delete, plus "Show more options" at the bottom. Windows 10 shows the full legacy menu with text labels. This difference is baked into the shell and cannot be toggled without a registry hack or third-party tool. It is the fastest visual check that survives most customization.

The edition question: why two Windows 11 machines behave differently

Two people can both correctly answer "Windows 11" and still have machines that behave completely differently, because edition gates features at the operating system level. The differences are not cosmetic. Windows 11 Home cannot join a domain, cannot use BitLocker drive encryption through the standard interface, and cannot host a Remote Desktop session. Windows 11 Pro adds all three plus Group Policy Editor and Hyper-V. Windows 11 Enterprise adds AppLocker, Windows To Go, and DirectAccess on top of Pro.

The edition is fixed at activation and cannot be changed by an update. A Windows 11 Home machine that installs every cumulative update for a decade will still be Home. Upgrading Home to Pro requires a new product key or a Microsoft Store purchase, and the upgrade happens in place without reinstalling. This is why a user who "has Windows 11" but cannot find BitLocker is not confused about their version; they are correct about the version and wrong about the edition.

The edition also determines the support lifecycle, which is where the stakes rise. Windows 11 Home and Pro receive 24 months of servicing from each release version's launch, while Enterprise and Education receive 36 months. Windows 10 22H2, the final Windows 10 release, reaches end of support on October 14, 2025 for all consumer editions; Enterprise and Education can buy Extended Security Updates for up to three additional years at escalating annual cost. Knowing your edition is therefore not academic. It determines the date your security patches stop.

What the numbers do not tell you

A correct version identification does not tell you whether your machine is eligible for the next feature update, whether your hardware meets the Windows 11 requirements, or whether your PC is actually receiving updates. Those are separate questions with separate tools. The PC Health Check app answers the hardware eligibility question directly. Windows Update answers the patching question. Neither is embedded in the version string.

The most common misconception is that a machine running Windows 11 is automatically up to date. Feature updates can be paused for up to five weeks in Settings, and on metered connections Windows will defer large downloads indefinitely without a clear warning. A Windows 11 22H2 machine that has never been offered 24H2 is not broken; it is likely blocked by a safeguard hold, a compatibility issue Microsoft has flagged for that specific hardware configuration, or a paused update setting the user forgot. The version string tells you where you are, not why you are there.

A second misconception concerns "Windows 11 ready" stickers and retailer listings. These indicate hardware eligibility at the time of manufacture, not the installed operating system. A laptop sold in 2022 with a Windows 11 ready badge may have shipped with Windows 10 and never been upgraded. The badge is a hardware claim about TPM 2.0, Secure Boot capability, and CPU generation. It is not a statement about what is installed. Always check winver, not the sticker.

Red flags worth acting on:

The winver build number is below 19045 and the machine is described as Windows 10. You are on an unsupported build and missing years of security patches. The edition reads "Windows 10 S" or "Windows 11 in S mode." S mode blocks non-Store apps and is a common source of "my software won't install" reports. The build number jumped backward after an update. A rollback occurred and the underlying update failure has not been fixed. The architecture reads ARM64 but the user is trying to install x64 drivers. Most x64 software runs under emulation, but kernel drivers do not. The release version is more than two annual cycles behind the current one. The machine is likely blocked by a safeguard hold that requires manual intervention.

How to confirm your version in under a minute

The following sequence takes about 45 seconds and produces everything a support agent, a driver page, or an IT ticket will ask for.

Press Windows key + R, type winver, press Enter. Note the version, build, and edition exactly as shown. Open Settings > System > About. Note the OS build with the revision suffix and the system type (x64 or ARM64). Open Settings > Windows Update > Update history. Confirm the most recent successful cumulative update date. If you need the release version explicitly, cross-reference the build number against Microsoft's Windows release health page, which maps every build to its release version. If you are evaluating an upgrade, run the PC Health Check app to confirm hardware eligibility before changing anything.

The threshold that matters for most readers is the Windows 10 end-of-support date of October 14, 2025. If winver reports a build in the 1904x range, you are on Windows 10 and that date applies to you. If it reports a build in the 22000, 22621, 22631, or 26100 range, you are on Windows 11 and the relevant date is 24 or 36 months from your release version's launch, depending on edition. Reconcile those two clocks before assuming you have time.

Limits of version identification

Version strings are necessary but not sufficient for security and compatibility decisions. They do not reflect firmware version, driver versions, installed application versions, or configuration state, any of which can determine whether a specific vulnerability applies to your machine. They also do not reflect whether a machine is domain-managed, in which case update policy is controlled centrally and the local Settings app may be misleading about what will actually install.

The build number is also not a reliable proxy for patch level on machines that have been offline. A machine that has not connected to Windows Update in six months will report the same build as one patched yesterday, with a lower revision suffix. Only the revision suffix and the update history distinguish them. For any security-sensitive audit, check the revision suffix, not the build alone.

Finally, version identification cannot tell you whether an upgrade is advisable for your specific hardware. Feature updates occasionally introduce driver regressions on specific chipsets, and Microsoft's safeguard holds exist precisely because the version string alone cannot predict which machines will fail. If a feature update is being held back on your machine, that is a signal about your hardware configuration, not a bug in the identification process.

This article provides general educational information about Windows version identification and is not a diagnosis of any specific system problem, a licensing opinion, or a guarantee of update availability or support outcomes. Support lifecycles, edition features, and safeguard holds change over time and vary by region and licensing agreement. For decisions about upgrading, licensing, or securing a specific machine, consult Microsoft's official documentation or a qualified IT professional.