Fixing the 10 Most Common Windows Activation Errors

Almost every failed activation reports a code, and each code has a short list of real causes. Find yours below and skip the guesswork.

Read the code, not the message

Windows activation error text is deliberately generic. The hex code is the useful part. Here are the ones that account for the overwhelming majority of failures.

0xC004F074 — the KMS host could not be contacted

The single most common error. Causes, in order of likelihood:

  1. The Software Protection service is stopped. net start sppsvc.
  2. System time is wrong. KMS tolerates only a small skew — enable automatic time sync and resync.
  3. DNS is blocking the lookup. Switch to 1.1.1.1.
  4. A VPN or corporate proxy is intercepting the connection. Disconnect and retry.

0xC004C003 — the activation server determined the key is blocked

A stale generic key is cached. Clear and retry:

slmgr /upk
slmgr /cpky

Then run HWID again.

0x80070005 — access denied

The console is not elevated, or Controlled Folder Access is blocking writes to the token store. Run as administrator; if it persists, disable Controlled Folder Access temporarily under Windows Security → Ransomware protection.

0xC004F050 — the product key is invalid

The key does not match the installed edition. Check with slmgr /dli — activating a Pro key on Home fails here. Either install the matching edition or use TSforge, which does not depend on a key.

0x8007232B — DNS name does not exist

The machine is looking for a KMS host that is not there. On an unmanaged home machine this means a leftover corporate KMS setting. Clear it with slmgr /ckms and re-run.

0xC004E015 / 0xC004F017 — licensing state mismatch

Usually a half-finished previous activation attempt. Repair the store and retry:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

0xC004F012 — a required licensing file is missing

A third-party cleaner or aggressive antivirus deleted licensing files. DISM restore health is the fix; if it fails, an in-place repair upgrade rebuilds the store without losing data.

0x803FA067 — the digital license did not apply

Specific to HWID, and often transient. Wait ten minutes, then slmgr /ato. If it repeats, the hardware ID changed — a motherboard swap or a firmware update that reset the machine GUID.

Office: 0x4004F00C and 0x8004FC12

Both are Ohook not loading. Check quarantine first, Smart App Control second. Verify with cscript ospp.vbs /dstatus in the Office folder.

The universal reset

When nothing above matches, put the licensing stack back to a known state:

net stop sppsvc
slmgr /upk
slmgr /cpky
slmgr /ckms
net start sppsvc

Reboot, then run MAS again and pick the method that matches your situation.

Get the script

Open Terminal (Admin) or PowerShell (Admin) and run:

irm https://get.activated.win | iex

Prefer offline? Grab the archive from the download page and run MAS_AIO.cmd as administrator. More help: troubleshooting guide · error decoder · all guides.

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.

Download from official repositoryView official releasesView source

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.