# Windows 11 activation: digital licences, hardware changes and what to do when it fails

> How activation is bound to hardware, what survives a motherboard swap, how to move a retail licence legitimately, and how to read the actual error.

**Tested on**

- Build: 26300.9457 / 26100.33650
- Edition: Pro (26H2) / Server
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## The short answer

Activation is a **hardware fingerprint match**, not a password check:

- A **digital licence** is tied to the device (a hash of key components) and stored by Microsoft.
- A **product key** is either retail (movable), OEM (tied to the first board it activates), or volume (organisation-managed).
- **Changing the motherboard** is the one event that breaks a digital licence on a retail/OEM install — and the one case where "it worked for years" stops working.

There is no legitimate way to activate Windows with a key you did not buy. Anything that claims otherwise is either a volume-key leak or a loader.

## Read the actual state before changing anything

```powershell
# edition, channel and licence status
Get-CimInstance SoftwareLicensingProduct |
  Where-Object { $_.PartialProductKey -and $_.Name -match 'Windows' } |
  Select-Object Name,Description,LicenseStatus,PartialProductKey
Get-CimInstance SoftwareLicensingService | Select-Object OA3xOriginalProductKey,ClientMachineID
```

`LicenseStatus`: **1** = licensed, **0** = unlicensed, **2** = grace, **5** = notification (out of tolerance), **6** = extended grace.

`Description` tells you the channel: `Windows(R), Professional edition` with `VOLUME_KMSCLIENT` means a KMS client — a machine that must reach a KMS server, not a retail licence.

> **Caution: Run these as administrator**
>
> `SoftwareLicensingProduct` is readable without elevation, but several fields come back empty. Elevate if you want the full picture.

## What survives a hardware change

| Change | Retail digital licence | OEM | Volume/MAK |
|---|---|---|---|
| RAM, disk, GPU | fine | fine | fine |
| **Motherboard** | usually reactivates | usually **fails** | depends on the agreement |
| CPU (same socket) | fine | fine | fine |
| Whole machine replaced | no | no | no |

Windows tolerates small changes because the fingerprint is a score, not an exact match. Swapping a board usually crosses the threshold.

## The legitimate paths when activation fails

1. **Troubleshoot** — *Settings → System → Activation → Troubleshoot*. If the licence is linked to your Microsoft account, this moves it to the new hardware. It works for retail licences and for Store purchases.
2. **Enter the key again** — *Change product key*. For a retail key that is all that is needed.
3. **Phone activation** — the troubleshooter offers it; it is the intended path for machines with no internet or a stuck licence.
4. **Buy the right licence** — retail (movable) or OEM (cheaper, tied). For a business, volume licensing through the correct channel.

```powershell
# force a licence re-check after a hardware change
slmgr /ato
slmgr /dlv      # detailed licence info, including the error code
```

`slmgr /dlv` is the honest source when the UI just says "something went wrong": it prints the specific error, e.g. `0xC004F211` (hardware change) or `0xC004F074` (no KMS server reachable).

## Common error codes, translated

| Code | Means | Action |
|---|---|---|
| `0xC004F211` | hardware changed | Troubleshoot, or re-enter key |
| `0xC004F074` | KMS server unreachable | domain machine: check DNS/`_vlmcs` record |
| `0xC004C003` | key blocked/invalid | key is not legitimate |
| `0xC004F050` | key invalid for this edition | wrong edition key |
| `0xC004FC03` | network/firewall blocked activation | allow `activation.sls.microsoft.com` |

## What about "activators" and cheap keys

They fall into three groups, and none of them is a licensing strategy:

- **KMS emulators / loaders** — patch boot or spoof a KMS host. Malware-adjacent by construction, break on updates, and are not a licence.
- **Volume-key leaks** — you are sharing one key with thousands of machines; Microsoft blocks them in batches, and your install deactivates.
- **"Lifetime" marketplace keys** — usually leaked volume keys or MSDN keys. Same outcome, later.

> **Danger: This site does not document activation bypasses**
>
> There is no legitimate way to activate Windows without a licence you acquired. Instructions for loaders, KMS emulators or leaked keys are excluded here on purpose — they are both unlawful and a common malware vector.

## Managed and subscription activation

If the machine belongs to an organisation, activation may come from somewhere else entirely:

- **Subscription activation** — Windows 11 Enterprise via a Microsoft 365 licence; the user signs in and the edition steps up.
- **MAK/KMS** — volume channel, configured by the admin.
- **Autopilot** — device-based provisioning that carries the licence with the hardware record.

In those cases the local "Activate Windows" watermark is a symptom of an expired token or a lost network path, not of a missing purchase. Ask the administrator before buying anything.

## Related

- [Windows 11 Home vs Pro](https://winbook.fyi/en/windows/start/home-vs-pro/)
- [Windows 10 after the end: ESU, LTSC, or replace](https://winbook.fyi/en/windows/start/win10-eol-esu/)
- [Which Windows 11? 26H2, 25H2, LTSC and ARM64](https://winbook.fyi/en/windows/start/versions/)

## Lab boundary

E1. Licensing states and error codes are Microsoft-documented. The lab VMs are activated through the Proxmox/KMS path used for testing; no retail or OEM licence transfer was performed, so hardware-change reactivation is described from documentation.

## Sources

- [Microsoft Learn — Subscription activation](https://learn.microsoft.com/en-us/windows/deployment/windows-10-subscription-activation)
- [Microsoft Learn — Volume activation](https://learn.microsoft.com/en-us/windows/deployment/volume-activation/volume-activation-windows-10)
- [Microsoft Learn — Licensing policy CSP](https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-licensing)
- [Microsoft Learn — Windows Autopilot](https://learn.microsoft.com/en-us/windows/deployment/windows-autopilot/)

---

Source: https://winbook.fyi/en/windows/security/activation/