Windows Activation Error Codes: Complete List With Fixes (2026)

In short: Most Windows activation errors come down to one of four causes: the wrong type of key for the edition installed (often a KMS/volume key on a home PC), a key that's blocked or already used, a hardware change that broke the digital licence link, or a network/clock problem stopping Windows from reaching the activation servers. Find your code in the table below, apply the fix, then run slmgr /ato to retry.

Contents

• First, get the exact error code
• Quick lookup table
• Key and edition errors
• KMS and volume licence errors
• Hardware change and digital licence errors
• Network, clock and system errors
• Useful activation commands (cheat sheet)
• FAQ

First, get the exact error code

The Settings page sometimes shows a vague message. To see the real code, open Command Prompt as administrator and run:

slmgr /ato 

This forces an activation attempt and shows the result in a pop-up. For full licence details:

slmgr /dlv 

Look at three lines in the output:

If the description says VOLUME_KMSCLIENT on a home or small-office PC, that alone explains most 0xC004F074 and 0x8007232B errors. Keep it in mind as you read on.

Tip: Microsoft notes that the error code can change after you run the troubleshooter or retry activation. Always re-check the code before applying a fix.

Quick lookup table

Each code is explained in more detail below.

Key and edition errors

0xC004C003: activation server rejected the key

The key isn't valid for activation. Usually it has been blocked, was never genuine, or was already activated elsewhere. Microsoft points out that product keys are unique, assigned to a specific user for one device.

Fix:

1. Double-check you typed the key correctly (O vs 0, B vs 8).
2. If the key came with your PC or from a seller, contact them for a replacement.
3. Enter a different valid key: Settings → System → Activation → Change product key.

0xC004C008: key used on too many devices

Retail keys are licensed for one device at a time. If the same key is active on another machine, you'll see this.

Fix: Deactivate it on the old device (slmgr /upk then slmgr /cpky on that machine), wait a few hours, and retry. If the old PC is gone, use the Activation troubleshooter while signed in with your Microsoft account, or use a new key.

0xC004C060: key is no longer valid

This one is common with keys that were valid once but have since been blocked.

Fix: You'll need a different key. Retrying won't help.

0xC004F050 and 0xC004F034: invalid product key

Either the key is mistyped, or it's for a different product (for example, a Windows 10 Enterprise key on Windows 11 Pro, or an Office key).

Fix:

1. Re-enter the key carefully.
2. Check your edition: press Win + R, type winver, and match the key to that edition.
3. Install the key from the command line to get a clearer error:

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX slmgr /ato 

0xC004F210 and 0xC004F212: key doesn't match your edition

A Pro key won't activate Home, and vice versa. This often happens after a clean reinstall where you picked the wrong edition on the setup screen.

Fix:

• Have a Pro key but Home installed? Go to Settings → System → Activation → Change product key and enter the Pro key. Windows upgrades from Home to Pro in place, with no reinstall.
• Digital licence for Pro but installed Home? Reinstall and pick Pro during setup, or run the Activation troubleshooter, which detects a licence for a different edition and tells you how to switch.

0xC004F213: no product key found

Windows couldn't find a key stored in firmware or linked to your account. This is typical after a motherboard replacement or a clean install on new hardware.

Fix: Enter a key manually, or if you previously linked a digital licence to your Microsoft account, use the troubleshooter's "I changed hardware on this device recently" option.

To check whether your PC has a key embedded in the BIOS/UEFI (common on laptops), run this in PowerShell:

(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey 

If it returns a key, enter that key. If it returns nothing, there's no OEM key on the board.

KMS and volume licence errors

KMS (Key Management Service) is how companies activate hundreds of PCs from an internal server. These errors are normal on work machines that are off the office network, and they're a red flag on a home PC, because they mean a volume key is installed.

0xC004F074: no KMS could be contacted

This is the most-searched activation error. Windows is trying to reach a KMS server and can't.

If this is a personal PC: a KMS client key was installed (by a previous owner, a pre-activated image, or an activator tool). Swap it for a proper retail or OEM key:

slmgr /upk slmgr /cpky slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX slmgr /ato 

If this is a work PC on a KMS network:

1. Connect to the company network or VPN.
2. Check the KMS host is discoverable in DNS:

 nslookup -type=srv _vlmcs._tcp 

1. Check TCP port 1688 is open to the KMS host:

 Test-NetConnection kms.yourdomain.local -Port 1688 

1. Point the client at the host manually if needed:

 slmgr /skms kms.yourdomain.local:1688 slmgr /ato 

1. Make sure the client's clock is within 4 hours of the KMS host.

0x8007232B and 0x8007007B: DNS name doesn't exist

These have the same root cause as 0xC004F074: Windows has a KMS client key and is searching DNS for a KMS host that doesn't exist.

Fix: On a personal PC, replace the key with a retail/OEM/MAK key (commands above). On a domain, ask IT to confirm the _vlmcs._tcp SRV record.

0xC004F038: KMS count is insufficient

A KMS host only activates clients once it has seen enough of them: 25 for Windows client editions, 5 for Windows Server.

Fix: Wait for more machines to contact the host, or use a MAK key for small environments.

0xC004F039: KMS not enabled

The KMS host isn't responding. The Software Protection service might be stopped, or the firewall is blocking it.

Fix (on the KMS host): Check that sppsvc is running and that port 1688 is allowed through Windows Firewall.

0xC004F06C: KMS request timestamp invalid

The client's clock is too far off from the KMS host's clock.

Fix: Sync time:

w32tm /resync 

Then check that the date and time zone are correct in Settings → Time & language.

Hardware change and digital licence errors

0xC004F211: hardware changed

Windows licences are tied to your hardware. Replace the motherboard (and sometimes the boot drive) and Windows may no longer recognise the device.

Fix:

1. Sign in to Windows with the Microsoft account you used before the change.
2. Go to Settings → System → Activation → Troubleshoot.
3. Choose "I changed hardware on this device recently" and pick your device from the list.

Note: This only works for retail licences and digital licences linked to your account. OEM licences (pre-installed by the PC maker) are tied to the original motherboard. Microsoft says you may need a new licence after replacing the board.

0x803F7001: no valid licence found

This is common after a clean install, a hardware change, or installing the wrong edition.

Fix:

1. Check the edition you installed matches the one you're licensed for.
2. Run the Activation troubleshooter.
3. If you have a key, enter it under Change product key.

0x800704CF: network location can't be reached

Microsoft describes this as "no valid licence found", but it often shows up when the PC is offline or a proxy/VPN blocks the activation servers.

Fix: Check your connection, disable VPN/proxy briefly, then retry with slmgr /ato.

Network, clock and system errors

0x80072F8F: secure connection failed

Windows couldn't establish a TLS connection to the activation servers. A wrong system clock is the usual cause.

Fix:

1. Set the date, time and time zone correctly (w32tm /resync).
2. Install pending Windows updates (they include root certificate updates).
3. Make sure no firewall or antivirus is doing HTTPS inspection on Microsoft domains.

0xC004F012: licence store value missing

The licence files on your system are damaged.

Fix: Rebuild them, then repair system files:

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

Restart, then run slmgr /ato.

0x80070005: access denied

You ran slmgr without admin rights.

Fix: Right-click Command Prompt or Terminal and choose Run as administrator.

0xC004FD01: not running on a supported Hyper-V platform

This only applies to AVMA (Automatic Virtual Machine Activation) keys inside Windows Server VMs. The guest must run on a Windows Server Datacenter Hyper-V host.

Fix: Run the VM on a Datacenter host, or use a standard retail/MAK key instead of the AVMA key.

Useful activation commands (cheat sheet)

Run all of these in an elevated Command Prompt.

And one PowerShell one-liner to see every licensed product (Windows and Office) on a machine:

Get-CimInstance SoftwareLicensingProduct -Filter "PartialProductKey IS NOT NULL" | Select-Object Name, Description, LicenseStatus, PartialProductKey 

LicenseStatus values: 0 = Unlicensed, 1 = Licensed, 2 = OOB grace, 3 = OOT grace, 4 = Non-genuine grace, 5 = Notification, 6 = Extended grace.

Still stuck?

If your code isn't listed here, the Noxkeys activation error code lookup covers more Windows and Office activation errors. Paste the code and it shows the cause and the fix.

For Microsoft's own references:

• Get help with Windows activation errors (Microsoft Support)
• Troubleshoot Windows activation error codes (Microsoft Learn, for IT pros)
• Error 0xC004F074 when you try to activate Windows (Microsoft Learn)

FAQ

Found an error code that isn't covered here? Drop it in the comments with what you were doing when it appeared, and I'll add the fix.