Two different things people call "activation"
Windows can be licensed in ways that behave very differently when the machine changes. Understanding which one you hold explains most of what happens after a reinstall, a motherboard swap or an edition change.
The product key
A 25-character string tied to a licence entitlement. Retail keys can be transferred between machines within the licence terms; OEM keys are bound to the device they shipped with. Entering a key triggers a validation request, but the key itself is the credential.
Check for one embedded in firmware:
wmic path softwarelicensingservice get OA3xOriginalProductKey
Many prebuilt machines carry an OEM key there, which is why they reactivate on their own after a clean install of the same edition.
The digital licence
A record on Microsoft's activation servers linking an entitlement to a hardware fingerprint of your machine. There is no string to type. When Windows reinstalls, it sends the fingerprint, the server recognises it, and activation completes with no interaction.
This is the mechanism behind the free upgrade entitlements, Microsoft Store purchases, and the HWID path in activation tooling.
Which do I have?
slmgr /dli
slmgr /dlv
The channel field tells you the licence type: Retail, OEM, Volume:MAK or Volume:GVLK. Settings shows a plainer version under System → Activation — "Windows is activated with a digital licence" versus "activated using a product key".
What breaks each one
| Change | Digital licence | Product key |
|---|---|---|
| Clean reinstall, same edition, same hardware | Reactivates automatically | Re-enter the key |
| Motherboard replacement | Usually breaks the fingerprint | Retail key can be reused; OEM cannot |
| Edition change (Home → Pro) | Needs the entitlement for the new edition | Needs a key for the new edition |
| Disk or GPU change | Normally fine | Normally fine |
Linking the licence to a Microsoft account before major hardware changes gives you the troubleshooter route to reclaim it afterwards. Without that link, a board swap leaves no way to point the server at the old record.
Where activation methods fit
Community methods do not create a third licence type. They target one of the existing mechanisms:
- HWID targets the digital-licence path for supported client editions.
- KMS-based methods target volume licensing behaviour.
- Office methods operate at the Office licensing layer, which is separate from Windows entirely.
That is why edition support matters so much: a method that targets a mechanism your edition does not use will fail no matter how many times you run it.
The practical takeaway
Before changing hardware or reinstalling, find out which licence you hold. It takes one command, and it determines whether the next boot activates silently or leaves you hunting for a key you may not have.
Related reading
- MAS activation methods compared
- MAS version history (upstream releases)
- Activation troubleshooting
- Security and source verification
massgrave.download is an independent documentation and troubleshooting resource. It is not the official Massgrave project. The official project lives at massgrave.dev and github.com/massgravel.