<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Noxkeys Tech Notes]]></title><description><![CDATA[Noxkeys Tech Notes]]></description><link>https://noxkeys.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Thu, 12 Nov 2026 08:15:16 GMT</lastBuildDate><atom:link href="https://noxkeys.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to Activate Windows 11: Every Method Explained]]></title><description><![CDATA[Activate Windows 11 with a product key, digital licence, slmgr or the Activation troubleshooter. Step-by-step methods plus fixes for common errors.]]></description><link>https://noxkeys.hashnode.dev/how-to-activate-windows-11</link><guid isPermaLink="true">https://noxkeys.hashnode.dev/how-to-activate-windows-11</guid><category><![CDATA[Windows]]></category><category><![CDATA[windows 11]]></category><category><![CDATA[Powershell]]></category><category><![CDATA[sysadmin]]></category><category><![CDATA[Tutorial]]></category><dc:creator><![CDATA[Bennett Page]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:15:52 GMT</pubDate><content:encoded><![CDATA[<blockquote>
<p><strong>In short:</strong> Go to <strong>Settings → System → Activation → Change product key</strong>, enter your 25-character key and click <strong>Activate</strong>. If you reinstalled Windows on a PC that was already activated, you usually don't need a key at all: the <strong>digital licence</strong> activates it automatically once you're online. From the command line, it's <code>slmgr /ipk &lt;key&gt;</code> followed by <code>slmgr /ato</code>. After a motherboard change, use the <strong>Activation troubleshooter</strong> while signed in to your Microsoft account.</p>
</blockquote>
<h2>Contents</h2>
<ol>
<li><a href="#heading-first-check-if-windows-11-is-already-activated">First, check if Windows 11 is already activated</a></li>
<li><a href="#heading-method-1-enter-a-product-key-in-settings">Method 1: Enter a product key in Settings</a></li>
<li><a href="#heading-method-2-enter-the-key-during-installation">Method 2: Enter the key during installation</a></li>
<li><a href="#heading-method-3-digital-licence-automatic-activation">Method 3: Digital licence (automatic activation)</a></li>
<li><a href="#heading-method-4-command-line-with-slmgr">Method 4: Command line with slmgr</a></li>
<li><a href="#heading-method-5-activation-troubleshooter-after-a-hardware-change">Method 5: Activation troubleshooter after a hardware change</a></li>
<li><a href="#heading-method-6-upgrade-from-an-activated-windows-10">Method 6: Upgrade from an activated Windows 10</a></li>
<li><a href="#heading-method-7-oem-key-in-the-firmware">Method 7: OEM key in the firmware</a></li>
<li><a href="#heading-method-8-business-activation-mak-kms-active-directory">Method 8: Business activation (MAK, KMS, Active Directory)</a></li>
<li><a href="#heading-which-method-should-you-use">Which method should you use?</a></li>
<li><a href="#heading-what-happens-if-you-dont-activate">What happens if you don't activate?</a></li>
<li><a href="#heading-why-you-should-avoid-free-activators">Why you should avoid "free activators"</a></li>
<li><a href="#heading-faq">FAQ</a></li>
</ol>
<hr />
<h2>First, check if Windows 11 is already activated</h2>
<p>Many PCs are activated without you doing anything. Check first:</p>
<ol>
<li>Open <strong>Settings</strong> (<code>Win + I</code>).</li>
<li>Go to <strong>System → Activation</strong>.</li>
<li>Look at <strong>Activation state</strong>.</li>
</ol>
<table>
<thead>
<tr>
<th>What it says</th>
<th>Meaning</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Active</strong>, "Windows is activated with a digital license linked to your Microsoft account"</td>
<td>Best case. It reactivates itself after reinstalls and is easier to recover after hardware changes</td>
</tr>
<tr>
<td><strong>Active</strong>, "Windows is activated with a digital license"</td>
<td>Activated, but not linked to an account yet (see Method 3)</td>
</tr>
<tr>
<td><strong>Active</strong>, "Windows is activated using your organization's activation service"</td>
<td>Company PC on KMS. Normal at work</td>
</tr>
<tr>
<td><strong>Not active</strong> + an error code</td>
<td>Needs activating. Pick a method below</td>
</tr>
</tbody></table>
<p>From the command line:</p>
<pre><code class="language-cmd">slmgr /xpr
</code></pre>
<p><em>"The machine is permanently activated"</em> means you're done.</p>
<hr />
<h2>Method 1: Enter a product key in Settings</h2>
<p>The standard way, and the one most people need.</p>
<ol>
<li><strong>Settings → System → Activation</strong>.</li>
<li>Next to <strong>Change product key</strong>, click <strong>Change</strong>.</li>
<li>Enter the <strong>25-character key</strong> (<code>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</code>).</li>
<li>Click <strong>Next</strong>, then <strong>Activate</strong>.</li>
</ol>
<p>Make sure you're connected to the internet. Activation usually takes a few seconds.</p>
<p><strong>The key must match your edition.</strong> A <strong>Pro</strong> key won't activate <strong>Home</strong>, and a Home key won't activate Pro. There's one exception that works in your favour: entering a <strong>Pro key on Home</strong> upgrades the PC to Pro in place, with no reinstall. Windows installs the extra Pro features, restarts, and activates.</p>
<blockquote>
<p><strong>Where's my key?</strong> It's in your purchase confirmation email, on the product card, or on a sticker for older PCs. Keys are often entered by copy-paste, so watch for extra spaces at the start or end.</p>
</blockquote>
<hr />
<h2>Method 2: Enter the key during installation</h2>
<p>When you clean install Windows 11 from a USB drive, setup asks for a product key:</p>
<ul>
<li><strong>Have a key?</strong> Enter it. Setup then installs the matching edition automatically.</li>
<li><strong>Don't have it handy?</strong> Click <strong>"I don't have a product key"</strong>. You'll be asked to pick an edition. <strong>Choose the edition you're licensed for</strong> (Home or Pro), then activate later with Method 1 or 3.</li>
</ul>
<blockquote>
<p><strong>Watch out:</strong> choosing the wrong edition here is the most common cause of activation errors after a reinstall (<code>0xC004F210</code>, <code>0xC004F212</code>, <code>0x803F7001</code>).</p>
</blockquote>
<hr />
<h2>Method 3: Digital licence (automatic activation)</h2>
<p>A <strong>digital licence</strong> means Microsoft's activation servers remember your PC's hardware. When you reinstall the <strong>same edition</strong> on the <strong>same PC</strong>, Windows activates itself once it's online, with no key needed.</p>
<p>You have a digital licence if your PC:</p>
<ul>
<li>came with Windows 11 or Windows 10 pre-installed, or</li>
<li>was upgraded for free from an activated Windows 10, or</li>
<li>was activated with a genuine retail key at any point.</li>
</ul>
<h3>Link it to your Microsoft account (do this now)</h3>
<p>Linking makes activation much easier to recover after a hardware change:</p>
<ol>
<li><strong>Settings → Accounts → Your info</strong>.</li>
<li>Click <strong>Sign in with a Microsoft account instead</strong> (if you use a local account).</li>
<li>Go back to <strong>Settings → System → Activation</strong>. It should now say <em>"…digital license linked to your Microsoft account"</em>.</li>
</ol>
<hr />
<h2>Method 4: Command line with slmgr</h2>
<p>Useful for remote sessions, scripts, or when the Settings page won't cooperate. Open <strong>Command Prompt</strong> or <strong>Terminal as administrator</strong>:</p>
<pre><code class="language-cmd">:: 1. Install the product key
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

:: 2. Activate online
slmgr /ato

:: 3. Confirm
slmgr /xpr
</code></pre>
<p>Each command shows a pop-up. To see the output in the console instead (handy over SSH or remote PowerShell):</p>
<pre><code class="language-cmd">cscript //nologo %windir%\system32\slmgr.vbs /ato
</code></pre>
<p><strong>Replacing a wrong key first</strong> (for example, a leftover KMS client key):</p>
<pre><code class="language-cmd">slmgr /upk
slmgr /cpky
slmgr /ckms
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
</code></pre>
<p>PowerShell can activate in one line too:</p>
<pre><code class="language-powershell">$svc = Get-CimInstance SoftwareLicensingService
Invoke-CimMethod -InputObject $svc -MethodName InstallProductKey -Arguments @{ ProductKey = 'XXXXX-XXXXX-XXXXX-XXXXX-XXXXX' }
Invoke-CimMethod -InputObject $svc -MethodName RefreshLicenseStatus
</code></pre>
<hr />
<h2>Method 5: Activation troubleshooter after a hardware change</h2>
<p>Replaced the <strong>motherboard</strong>? Windows sees it as a new PC and may show <code>0xC004F211</code> or <code>0x803F7001</code>.</p>
<ol>
<li>Sign in with the <strong>same Microsoft account</strong> your licence is linked to.</li>
<li><strong>Settings → System → Activation → Troubleshoot</strong>.</li>
<li>Choose <strong>"I changed hardware on this device recently"</strong>.</li>
<li>Sign in if asked, select <strong>"This is the device I'm using right now"</strong> from the list, and click <strong>Activate</strong>.</li>
</ol>
<table>
<thead>
<tr>
<th>Licence type</th>
<th>Works after motherboard change?</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Retail</strong> (bought separately)</td>
<td>Yes, through the troubleshooter</td>
</tr>
<tr>
<td><strong>OEM</strong> (came with the PC)</td>
<td>Usually no. It's tied to the original motherboard</td>
</tr>
<tr>
<td><strong>Volume</strong> (work PC)</td>
<td>Ask your IT team</td>
</tr>
</tbody></table>
<p>Not sure which type you have? Run <code>slmgr /dli</code>. The <strong>Description</strong> line shows <code>RETAIL</code>, <code>OEM</code> or <code>VOLUME</code>.</p>
<hr />
<h2>Method 6: Upgrade from an activated Windows 10</h2>
<p>If Windows 10 on your PC is genuinely activated and the hardware meets the Windows 11 requirements, upgrading keeps the activation:</p>
<ul>
<li><strong>Windows 10 Home</strong> becomes <strong>Windows 11 Home</strong></li>
<li><strong>Windows 10 Pro</strong> becomes <strong>Windows 11 Pro</strong></li>
</ul>
<p>Go to <strong>Settings → Update &amp; Security → Windows Update</strong> on Windows 10 and accept the Windows 11 upgrade, or run Microsoft's Installation Assistant. No key is needed. The licence converts to a digital licence for Windows 11.</p>
<blockquote>
<p>Still on Windows 10? Microsoft extended free consumer security updates (ESU) to <strong>12 October 2027</strong>, so there's time, but the upgrade itself costs nothing if your PC qualifies.</p>
</blockquote>
<hr />
<h2>Method 7: OEM key in the firmware</h2>
<p>Most laptops and branded desktops have a Windows key <strong>stored in the UEFI firmware</strong>. Windows reads it automatically during setup and activates, as long as you install the <strong>matching edition</strong>.</p>
<p>Check what's stored:</p>
<pre><code class="language-powershell">Get-CimInstance SoftwareLicensingService |
  Select-Object OA3xOriginalProductKey, OA3xOriginalProductKeyDescription
</code></pre>
<ul>
<li><code>Core</code> in the description means the key is for <strong>Home</strong>.</li>
<li><code>Professional</code> means it's for <strong>Pro</strong>.</li>
</ul>
<p>If the firmware key is <strong>Home</strong> but you want Pro, install Home first (so it activates), then upgrade with a Pro key using Method 1.</p>
<hr />
<h2>Method 8: Business activation (MAK, KMS, Active Directory)</h2>
<p>For organisations with Microsoft volume licensing:</p>
<table>
<thead>
<tr>
<th>Method</th>
<th>How it works</th>
<th>Typical use</th>
</tr>
</thead>
<tbody><tr>
<td><strong>MAK</strong> (Multiple Activation Key)</td>
<td>Each PC activates once online against Microsoft, which counts down the key's limit</td>
<td>Small fleets, PCs that are often offline</td>
</tr>
<tr>
<td><strong>KMS</strong> (Key Management Service)</td>
<td>PCs activate against the company's own KMS server and renew every 180 days</td>
<td>Larger networks (25+ client PCs)</td>
</tr>
<tr>
<td><strong>Active Directory-Based Activation</strong></td>
<td>PCs activate automatically when joined to the domain</td>
<td>Domain environments</td>
</tr>
<tr>
<td><strong>Subscription activation</strong></td>
<td>Pro steps up to Enterprise automatically with a qualifying Microsoft 365 licence</td>
<td>Microsoft 365 E3/E5 organisations</td>
</tr>
</tbody></table>
<p>Work laptops showing <em>"activated using your organization's activation service"</em> are on KMS or AD-based activation. Connect to the office network or VPN now and then to keep them activated.</p>
<hr />
<h2>Which method should you use?</h2>
<table>
<thead>
<tr>
<th>Your situation</th>
<th>Use</th>
</tr>
</thead>
<tbody><tr>
<td>New PC with Windows pre-installed</td>
<td>Nothing. It's already activated (OEM)</td>
</tr>
<tr>
<td>Bought a Windows 11 key</td>
<td><strong>Method 1</strong> (Settings)</td>
</tr>
<tr>
<td>Clean install on a previously activated PC</td>
<td><strong>Method 3</strong> (digital licence, automatic)</td>
</tr>
<tr>
<td>Clean install with a key in hand</td>
<td><strong>Method 2</strong> (during setup)</td>
</tr>
<tr>
<td>Remote or scripted setup</td>
<td><strong>Method 4</strong> (<code>slmgr</code>)</td>
</tr>
<tr>
<td>Replaced the motherboard</td>
<td><strong>Method 5</strong> (troubleshooter)</td>
</tr>
<tr>
<td>Upgrading from Windows 10</td>
<td><strong>Method 6</strong></td>
</tr>
<tr>
<td>Want Pro on a Home PC</td>
<td><strong>Method 1</strong> with a Pro key (in-place upgrade)</td>
</tr>
<tr>
<td>Company fleet</td>
<td><strong>Method 8</strong></td>
</tr>
</tbody></table>
<hr />
<h2>What happens if you don't activate?</h2>
<p>Windows 11 keeps working, but:</p>
<ul>
<li>An <strong>"Activate Windows"</strong> watermark appears in the bottom-right corner.</li>
<li><strong>Personalisation is locked</strong>: wallpaper, colours, themes, lock screen and taskbar settings.</li>
<li>Reminders show up in Settings and notifications.</li>
<li>You're not licensed to use it under Microsoft's terms.</li>
</ul>
<p>Security updates still install, so an unactivated PC isn't cut off. But for a PC you actually use, activation is the right call.</p>
<hr />
<h2>Why you should avoid "free activators"</h2>
<p>Scripts and tools that promise free activation usually work by:</p>
<ul>
<li>installing a <strong>KMS client key</strong> and pointing your PC at an <strong>unknown KMS server</strong>, or</li>
<li>patching system files.</li>
</ul>
<p>The problems:</p>
<ul>
<li><strong>Security risk:</strong> many contain malware, and you're giving an unknown script admin rights.</li>
<li><strong>It's unlicensed:</strong> the PC isn't legally activated.</li>
<li><strong>It breaks later:</strong> expect <code>0xC004F074</code> errors, a returning watermark, or problems after major updates.</li>
</ul>
<p>Check whether a PC has been "activated" this way:</p>
<pre><code class="language-cmd">slmgr /dlv
</code></pre>
<p>If you see <code>VOLUME_KMSCLIENT</code> and a <strong>KMS machine name</strong> you don't recognise on a home PC, clean it up with <code>slmgr /upk</code>, <code>slmgr /cpky</code>, <code>slmgr /ckms</code>, then activate properly with Method 1.</p>
<hr />
<h2>Activation failed? Quick fixes</h2>
<table>
<thead>
<tr>
<th>Error</th>
<th>Likely cause</th>
<th>Fix</th>
</tr>
</thead>
<tbody><tr>
<td><code>0xC004F074</code></td>
<td>KMS key installed, no KMS server</td>
<td>Replace it with a retail/OEM key (Method 4)</td>
</tr>
<tr>
<td><code>0xC004C003</code></td>
<td>Key blocked or invalid</td>
<td>Use a different, genuine key</td>
</tr>
<tr>
<td><code>0xC004F210</code> / <code>0xC004F212</code></td>
<td>Key doesn't match edition</td>
<td>Install the matching edition, or use a Pro key on Home to upgrade</td>
</tr>
<tr>
<td><code>0x803F7001</code></td>
<td>No valid licence found</td>
<td>Digital licence missing: enter a key or use the troubleshooter</td>
</tr>
<tr>
<td><code>0xC004F211</code></td>
<td>Hardware changed</td>
<td>Method 5</td>
</tr>
<tr>
<td><code>0x80072F8F</code></td>
<td>Clock wrong / connection blocked</td>
<td>Fix date and time, then retry</td>
</tr>
</tbody></table>
<p>The full list of codes and fixes is in <a href="https://dev.to/stevegass/windows-activation-error-codes-complete-list-with-fixes-2026-22n2">Windows Activation Error Codes: Complete List With Fixes</a>, or paste any code into the free <a href="https://noxkeys.com/activation-error-code-lookup/">activation error code lookup</a>.</p>
<p><strong>Microsoft references:</strong></p>
<ul>
<li><a href="https://support.microsoft.com/help/10738">Get help with Windows activation errors</a> (Microsoft Support)</li>
<li><a href="https://learn.microsoft.com/windows-server/get-started/activation-slmgr-vbs-options">Slmgr.vbs options</a> (Microsoft Learn)</li>
</ul>
<hr />
<h2>FAQ</h2>
<h3>Do I need a product key to activate Windows 11?</h3>
<p>Not always. If the PC already has a digital licence (pre-installed Windows, a free upgrade from Windows 10, or an earlier activation), it activates automatically. You only need a key for a new licence or a different edition.</p>
<h3>Can I use a Windows 10 key to activate Windows 11?</h3>
<p>Yes. Genuine Windows 10 Home and Pro keys activate the same edition of Windows 11.</p>
<h3>How do I upgrade Windows 11 Home to Pro?</h3>
<p>Go to <strong>Settings → System → Activation → Change product key</strong> and enter a Windows 11 Pro key. Windows upgrades in place, keeps your files and apps, and restarts once.</p>
<h3>How long can I use Windows 11 without activating?</h3>
<p>There's no hard time limit. Windows keeps running with the watermark and locked personalisation, but it isn't properly licensed.</p>
<h3>Does Windows 11 activation work offline?</h3>
<p>Retail and OEM activation need an internet connection. If you can't get online, contact Microsoft support. Business PCs can use KMS on the local network.</p>
<h3>Can I activate one key on two PCs?</h3>
<p>No. A retail key is licensed for <strong>one PC at a time</strong>. To move it, deactivate it on the old PC first (<code>slmgr /upk</code>), then activate it on the new one.</p>
<h3>Does this work on Windows 11 26H2?</h3>
<p>Yes. All of these methods work the same on every current version, including <strong>26H2</strong> (released September 2026).</p>
<hr />
<p><em>Ran into an activation problem that isn't covered here? Share the error code and your Windows edition in the comments.</em></p>
]]></content:encoded></item><item><title><![CDATA[How to Check Your Windows 11 Version and Build Number (5 Ways)]]></title><description><![CDATA[In short: Press Win + R, type winver and press Enter. The window shows your Windows 11 version (for example 25H2) and OS build (for example 26200.xxxx)…]]></description><link>https://noxkeys.hashnode.dev/how-to-check-your-windows-11-version-and-build-number-5-ways</link><guid isPermaLink="true">https://noxkeys.hashnode.dev/how-to-check-your-windows-11-version-and-build-number-5-ways</guid><dc:creator><![CDATA[Bennett Page]]></dc:creator><pubDate>Mon, 09 Nov 2026 15:44:59 GMT</pubDate><content:encoded><![CDATA[<blockquote>
<p><strong>In short:</strong> Press <code>Win + R</code>, type <code>winver</code> and press Enter. The window shows your Windows 11 <strong>version</strong> (for example <em>25H2</em>) and <strong>OS build</strong> (for example <em>26200.xxxx</em>). The first five digits of the build tell you the version: <strong>26200 = 25H2</strong>, <strong>26100 = 24H2</strong>, <strong>22631 = 23H2</strong>. For scripts, use PowerShell: <code>Get-ComputerInfo -Property OSDisplayVersion, OsBuildNumber</code>.</p>
</blockquote>
<h2>Contents</h2>
<ol>
<li><a href="#heading-version-vs-build-vs-edition-whats-the-difference">Version vs build vs edition: what's the difference?</a></li>
<li><a href="#heading-method-1-winver-fastest">Method 1: winver (fastest)</a></li>
<li><a href="#heading-method-2-settings-about">Method 2: Settings → About</a></li>
<li><a href="#heading-method-3-command-prompt-ver-and-systeminfo">Method 3: Command Prompt (ver and systeminfo)</a></li>
<li><a href="#heading-method-4-powershell">Method 4: PowerShell</a></li>
<li><a href="#heading-method-5-registry-for-scripts-and-inventory">Method 5: Registry (for scripts and inventory)</a></li>
<li><a href="#heading-windows-11-build-number-to-version-table">Windows 11 build number to version table</a></li>
<li><a href="#heading-bonus-check-many-pcs-at-once">Bonus: check many PCs at once</a></li>
<li><a href="#heading-faq">FAQ</a></li>
</ol>
<hr />
<h2>Version vs build vs edition: what's the difference?</h2>
<p>People mix these up all the time, so here's the quick version:</p>
<table>
<thead>
<tr>
<th>Term</th>
<th>Example</th>
<th>What it means</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Edition</strong></td>
<td>Home, Pro, Enterprise</td>
<td>Which licence/feature set you have</td>
</tr>
<tr>
<td><strong>Version</strong></td>
<td>24H2, 25H2</td>
<td>The yearly feature release (year + half: <em>25H2</em> = 2025, second half)</td>
</tr>
<tr>
<td><strong>OS build</strong></td>
<td>26200.9278</td>
<td>The exact build: base build + monthly update revision</td>
</tr>
</tbody></table>
<p>A full build number like <code>10.0.26200.9278</code> breaks down as:</p>
<pre><code class="language-text">10   . 0     . 26200  . 9278
major  minor   build    revision (UBR)
</code></pre>
<ul>
<li><strong>26200</strong> is the base build, which tells you the version (25H2).</li>
<li><strong>9278</strong> is the revision, which goes up with every monthly cumulative update.</li>
</ul>
<p>So two PCs on 25H2 can show different builds. One of them just has newer updates.</p>
<blockquote>
<p><strong>Why it matters:</strong> Microsoft support dates are tied to the <strong>version</strong>. Windows 11 24H2 Home and Pro stopped getting security updates in <strong>October 2026</strong>, so if <code>winver</code> shows 24H2 on a Home or Pro PC, it's time to update to 25H2.</p>
</blockquote>
<hr />
<h2>Method 1: winver (fastest)</h2>
<ol>
<li>Press <code>Win + R</code>.</li>
<li>Type <code>winver</code> and press <strong>Enter</strong>.</li>
</ol>
<p>A small "About Windows" window opens showing:</p>
<pre><code class="language-text">Microsoft Windows
Version 25H2 (OS Build 26200.xxxx)
</code></pre>
<p>It also shows the licensed edition at the bottom ("licensed to…"). That's it, and it takes three seconds.</p>
<hr />
<h2>Method 2: Settings → About</h2>
<ol>
<li>Open <strong>Settings</strong> (<code>Win + I</code>).</li>
<li>Go to <strong>System → About</strong>.</li>
<li>Scroll to <strong>Windows specifications</strong>.</li>
</ol>
<p>You'll see:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>Example</th>
</tr>
</thead>
<tbody><tr>
<td>Edition</td>
<td>Windows 11 Pro</td>
</tr>
<tr>
<td>Version</td>
<td>25H2</td>
</tr>
<tr>
<td>Installed on</td>
<td>the date the current version was installed</td>
</tr>
<tr>
<td>OS build</td>
<td>26200.xxxx</td>
</tr>
<tr>
<td>Experience</td>
<td>Windows Feature Experience Pack…</td>
</tr>
</tbody></table>
<p>There's a <strong>Copy</strong> button next to it, which is handy for pasting into a support ticket.</p>
<hr />
<h2>Method 3: Command Prompt (ver and systeminfo)</h2>
<h3>Quick: <code>ver</code></h3>
<pre><code class="language-cmd">ver
</code></pre>
<p>Output:</p>
<pre><code class="language-text">Microsoft Windows [Version 10.0.26200.xxxx]
</code></pre>
<p>Yes, it says <strong>10.0</strong> even on Windows 11. That's normal. Windows 11 kept the 10.0 kernel version number, and the <strong>build</strong> is what separates them: any build <strong>22000 or higher is Windows 11</strong>.</p>
<h3>Detailed: <code>systeminfo</code></h3>
<pre><code class="language-cmd">systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
</code></pre>
<p>Output:</p>
<pre><code class="language-text">OS Name:     Microsoft Windows 11 Pro
OS Version:  10.0.26200 N/A Build 26200
</code></pre>
<p>This gives you the edition and build in one go, but not the "25H2" label. Use the table below to map it.</p>
<hr />
<h2>Method 4: PowerShell</h2>
<p>The cleanest option for scripts:</p>
<pre><code class="language-powershell">Get-ComputerInfo -Property OsName, OSDisplayVersion, OsBuildNumber
</code></pre>
<p>Output:</p>
<pre><code class="language-text">OsName                   OSDisplayVersion OsBuildNumber
------                   ---------------- -------------
Microsoft Windows 11 Pro 25H2             26200
</code></pre>
<p><code>Get-ComputerInfo</code> can take a few seconds because it collects a lot of data. For a faster check, use CIM:</p>
<pre><code class="language-powershell">Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber
</code></pre>
<hr />
<h2>Method 5: Registry (for scripts and inventory)</h2>
<p>Everything above ultimately reads from this key:</p>
<pre><code class="language-text">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
</code></pre>
<p>Read it with PowerShell:</p>
<pre><code class="language-powershell">Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
  Select-Object EditionID, DisplayVersion, CurrentBuild, UBR
</code></pre>
<p>Output:</p>
<pre><code class="language-text">EditionID    DisplayVersion CurrentBuild UBR
---------    -------------- ------------ ----
Professional 25H2           26200        9278
</code></pre>
<p>To build the full version string:</p>
<pre><code class="language-powershell">$cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
"$($cv.DisplayVersion) (OS Build $($cv.CurrentBuild).$($cv.UBR))"
# 25H2 (OS Build 26200.9278)
</code></pre>
<blockquote>
<p><strong>Gotcha:</strong> The <code>ProductName</code> value in this key still says <strong>"Windows 10 Pro"</strong> on many Windows 11 machines. Don't use it to detect Windows 11. Check <code>CurrentBuild -ge 22000</code> instead:</p>
<pre><code class="language-powershell">$build = [int](Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuild
if ($build -ge 22000) { 'Windows 11' } else { 'Windows 10' }
</code></pre>
</blockquote>
<hr />
<h2>Windows 11 build number to version table</h2>
<p>Match the first five digits of your build:</p>
<table>
<thead>
<tr>
<th>Base build</th>
<th>Version</th>
<th>Released</th>
<th>Notes</th>
</tr>
</thead>
<tbody><tr>
<td>22000</td>
<td>21H2</td>
<td>Oct 2021</td>
<td>Original Windows 11, out of support</td>
</tr>
<tr>
<td>22621</td>
<td>22H2</td>
<td>Sep 2022</td>
<td>Out of support</td>
</tr>
<tr>
<td>22631</td>
<td>23H2</td>
<td>Oct 2023</td>
<td>Home/Pro out of support</td>
</tr>
<tr>
<td>26100</td>
<td>24H2</td>
<td>Oct 2024</td>
<td>Home/Pro support ended Oct 2026</td>
</tr>
<tr>
<td>26200</td>
<td>25H2</td>
<td>Sep 2025</td>
<td><strong>Current release for existing PCs</strong></td>
</tr>
<tr>
<td>28000</td>
<td>26H1</td>
<td>Feb 2026</td>
<td>Only on certain new devices, not an upgrade for existing PCs</td>
</tr>
</tbody></table>
<p>A note on <strong>26H1</strong>: it has the highest number, but Microsoft only ships it pre-installed on specific new hardware. Existing 24H2/25H2 PCs won't get it through Windows Update, so don't worry if you don't see it.</p>
<p>For the latest revision numbers and KB articles, Microsoft keeps an official list on the <a href="https://learn.microsoft.com/windows/release-health/windows11-release-information">Windows 11 release information</a> page.</p>
<p>If you'd rather paste a build number and get the version, release date and support status back, I use this free <a href="https://noxkeys.com/REPLACE-WITH-BUILD-LOOKUP-URL">Windows &amp; Office build number lookup</a>. It also covers Office builds, which are much harder to decode.</p>
<hr />
<h2>Bonus: check many PCs at once</h2>
<p>If you manage a few machines with PowerShell remoting enabled:</p>
<pre><code class="language-powershell">$computers = 'PC-01', 'PC-02', 'PC-03'

Invoke-Command -ComputerName $computers -ScriptBlock {
  $cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
  [pscustomobject]@{
    Edition = $cv.EditionID
    Version = $cv.DisplayVersion
    Build   = "$($cv.CurrentBuild).$($cv.UBR)"
  }
} | Select-Object PSComputerName, Edition, Version, Build |
  Format-Table -AutoSize
</code></pre>
<p>Add <code>| Export-Csv .\windows-versions.csv -NoTypeInformation</code> to save it as a spreadsheet. That's a quick way to spot machines still on 24H2 that need updating.</p>
<hr />
<h2>FAQ</h2>
<h3>How do I know if I have Windows 10 or Windows 11?</h3>
<p>Run <code>winver</code>. If the build is <strong>22000 or higher</strong>, it's Windows 11. Builds starting with 19041–19045 are Windows 10.</p>
<h3>Why does Command Prompt say "Version 10.0" on Windows 11?</h3>
<p>Windows 11 kept the internal version number 10.0 for app compatibility. The build number is what tells them apart.</p>
<h3>What is the latest Windows 11 version?</h3>
<p>For existing PCs, <strong>25H2</strong> (build 26200) is the current feature release. Version 26H1 (build 28000) exists but only ships on certain new devices.</p>
<h3>How do I update to the latest version?</h3>
<p>Go to <strong>Settings → Windows Update</strong> and click <strong>Check for updates</strong>. If 25H2 is available for your PC, it appears as a feature update. Going from 24H2 to 25H2 is a small enablement package and installs quickly.</p>
<h3>Does the build number tell me if Windows is activated?</h3>
<p>No. To check activation, go to <strong>Settings → System → Activation</strong>, or run <code>slmgr /xpr</code> in an admin Command Prompt. If you're seeing an activation error, I wrote a full guide: <a href="https://dev.to/stevegass/windows-activation-error-codes-complete-list-with-fixes-2026-22n2">Windows Activation Error Codes: Complete List With Fixes</a>.</p>
<h3>Where can I see what changed in each build?</h3>
<p>Every build on Microsoft's <a href="https://learn.microsoft.com/windows/release-health/windows11-release-information">Windows 11 release information</a> page links to its KB article, which lists the fixes and changes in that update.</p>
<hr />
<p><em>Which build are you on right now? Drop it in the comments. I'm curious how many people are still on 24H2.</em></p>
]]></content:encoded></item></channel></rss>