Reinstalling Windows Without Losing Activation: What to Check First

How activation behaves across a clean install, an in-place repair and a hardware change, and the checks to run before wiping a machine.

Activation and reinstalls: what actually carries over

A clean install is the moment people discover what kind of licence they really had. Some machines reactivate before the desktop finishes loading; others land in notification mode. The difference is predictable if you check beforehand.

Before you wipe anything

Run these three commands and save the output somewhere off the machine:

slmgr /dlv
wmic path softwarelicensingservice get OA3xOriginalProductKey
winver

They give you the licence channel, any firmware-embedded OEM key, and the exact edition and build. Reinstalling a different edition than the one you were licensed for is the most common self-inflicted activation failure.

What survives a clean install

Licence typeAfter clean install, same edition and hardware
Digital licenceReactivates automatically once online
Firmware OEM keyApplied automatically during setup
Retail keyRe-enter the key
Volume/KMSDepends on the environment; may need re-provisioning

The rule for digital licences is "same edition, same hardware". Change either and the server may not match the record.

Edition traps

  • Installing Home when the entitlement is for Pro leaves you unactivated even though the hardware is recognised.
  • Windows setup picks an edition from the firmware key when one exists; choosing manually can override that and cause a mismatch.
  • Single Language, N and Education SKUs are separate editions, not variants.

In-place repair versus clean install

An in-place upgrade repair (running setup from within Windows and keeping files and apps) preserves the licensing state along with everything else. If your goal is fixing a broken system rather than starting fresh, it is far less disruptive to activation.

Hardware changes

A motherboard replacement changes the fingerprint a digital licence depends on. If the licence is linked to a Microsoft account beforehand, the activation troubleshooter offers a path to reassign it: Settings → System → Activation → Troubleshoot → I changed hardware on this device recently. Without that link, the record cannot be matched to you.

Storage, memory and graphics changes do not normally affect the fingerprint.

After the reinstall

Give it time and connectivity, then check rather than assume:

slmgr /xpr

If it reports notification mode, look at the exact error code before running anything. Codes in the 0xC004… family are specific and point at very different causes — wrong edition, server unreachable, key mismatch, time skew.

Office is separate

Windows activation state says nothing about Office. After a reinstall, verify Office independently with ospp.vbs /dstatus from the Office program folder, and remember that subscription installs depend on signing in, not on licensing commands.


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.

Get MAS from the official project

This site does not host its own build of the scripts. The buttons below go to the project’s own repository and mirrors, so what you get is what the developers published.

PowerShell one-liner published by the project:

irm get.activated.win | iex

Check the domain before running it, and see how to verify what you run.

Activation tooling is routinely classified as riskware by antivirus software. That is expected for this category and is not by itself evidence of malware — nor proof that a particular copy is clean. Verify the source before running anything.