Windows 11 Activation Error Codes: Every Code Explained

Find your code

Every code below is one a Windows 11 user is realistically going to meet, sorted by what has gone wrong rather than by number. Type your code to jump straight to it. Partial codes work, and so do plain words — try clock or already in use if you have a message rather than a number.

First, work out which kind of key you have

This sounds like a detour. It is the single most useful thing on the page, because Microsoft documents several of these codes twice — once for people who bought a key, once for organisations running their own activation server — and the two answers are different. Land on the wrong one and you will spend an evening solving a problem you do not have.

If you bought the key — from a shop, from us, or with the PC — you have a retail or OEM licence and the middle column is yours. If it arrived from an employer, a college or an IT department, you have a volume licence, and the fixes run through whoever issued it rather than through anything you can do at your desk. Microsoft’s own remedy for one of these codes is simply to “Contact your organization’s support person”, which tells you everything about who owns the problem.

The ten-second check

If you are not sure, open Command Prompt and run slmgr /dlv. It needs no administrator rights and changes nothing — Microsoft describes it as displaying “the license information for the installed operating system”. The description line names the channel: retail, OEM or volume. A shorter version, slmgr /dli, does the same job with less detail.

One more tell: slmgr /xpr reports when activation expires. Microsoft notes it is “primarily useful for KMS clients, because MAK and retail activation is perpetual”. If it tells you activation is permanent, you are not on a KMS licence. If it gives you a date a few months out, you are.

Codes that mean the key is for the wrong edition or version

This is the most common cause that is genuinely about the key, and the easiest to misread as a faulty one. A Windows key is tied to a specific edition and version. A Windows 10 Pro key will not activate Windows 11 Pro, and a Home key will not activate Pro, however genuine either of them is.

Check what you are running before you change anything: Settings → System → Activation names the edition at the top. If the mismatch is that you have Home and a Pro key, you do not have a problem — you have an upgrade, and there is a specific route for it in our guide to upgrading Home to Pro.

Codes that mean the key looks like it’s already in use

These are the codes that cause the most alarm and the most wasted money, so they are worth reading slowly. Microsoft’s wording for 0xC004C008, 0xC004C770 and 0x803FA071 is that the key “has already been used on another device, or it’s being used on more devices than the Microsoft Software License Terms allow”.

Read as a verdict, that sounds final. It is not a verdict. It is what Microsoft’s activation server says when it has a record of that key and the machine in front of it does not match. There are several ordinary ways to produce that mismatch with a perfectly good licence:

• The key was submitted twice. A connection drops part-way through activation, the key gets entered again, and the second attempt arrives while the first is still registering. The Office equivalent of this is well documented and the same thing happens on Windows.
• The machine has changed since it last activated. A new motherboard, a swapped drive, sometimes a firmware update. Windows no longer recognises the hardware and treats it as a different device.
• Windows was reinstalled, or the edition changed between attempts. The key is remembered against the previous installation.
• The key genuinely is on another machine — an old PC that was never retired, or a second computer someone tried to cover with the same licence.

Only the last of those is about the key itself. So before doing anything drastic: wait fifteen to thirty minutes and try activating again. If the first attempt was still being processed, the second will now go through, and you will have solved it for free.

Two related codes belong here. 0xC004C003 reports the key as not valid, which Microsoft associates with a key that has been used on multiple devices — on a work licence, the same code means the key has been blocked. And there is a larger group — 0xC004C060, 0xC004C4A2, 0xC004C001, 0xC004B001 and a dozen others — that Microsoft lists together under three quite different causes: a key that cannot be used to activate Windows, activation servers that were busy, or a free upgrade that was never reactivated after a reinstall. Two of those three resolve themselves. That is a good reason not to draw a conclusion from the code alone.

If what you are really asking is how many machines one licence is allowed to cover, that has its own answer: see how many PCs one Windows 11 Pro licence activates. And if you meant to move a licence rather than share it, the transfer guide covers the order to do it in.

Codes that have nothing to do with your key

A large share of activation failures are environmental. The key is fine, the licence is fine, and something between your PC and Microsoft is in the way. Start here, because these are the cheapest to fix.

The clock is worth singling out. Activation is a signed exchange with a server, and a machine whose date is badly wrong — a laptop that has been in a drawer, a fresh install that never picked up the time, a dead CMOS battery — gets rejected before the key is ever considered. It is a thirty-second fix that is skipped constantly because nobody expects the clock to have anything to do with a licence.

Codes that mean Windows can’t find a licence at all

These are different from a rejected key. Windows is not saying your key is wrong; it is saying there is nothing here to check.

The hardware-change case is the one people meet most. Microsoft’s explanation is plain: “If you make significant hardware changes on your device, such as replacing your motherboard, Windows will no longer find a license that matches your device, and you’ll need to reactivate Windows.” A licence linked to a Microsoft account is what makes this survivable — the Activation troubleshooter lists the devices on your account and asks you to tick “This is the device I’m using right now”, which is as clear a demonstration as you will get that activation is tracked per machine.

If you have no idea which key the machine had, it may still be recoverable before you buy anything — our guide to finding your Windows product key covers the ways to get it back. And if the terms in these messages are the confusing part, licence key, product key and activation key untangles them.

The order worth trying fixes in

If you would rather not diagnose the code at all, this sequence resolves most activation errors, cheapest first. Work down it and stop when Windows activates.

1. Fix the clock. Settings → Time & language → Date & time, with both automatic options on. Then retry.
2. Check the connection, and turn off any VPN or proxy. Corporate firewalls and some security suites block activation endpoints without saying so.
3. Confirm the edition matches the key. Settings → System → Activation names what is installed. A Home machine will never take a Pro key.
4. Retry activation directly with slmgr /ato from Command Prompt, which prompts Windows to try again without changing anything.
5. Run the Activation troubleshooter from Settings → System → Activation. It handles the hardware-change case that nothing else will.
6. Wait, if the code suggests the key was submitted twice or the servers were busy. Fifteen to thirty minutes, then one more attempt.
7. Ask whoever sold you the key. Not “buy another one” — ask. A seller can see the key’s history and whether it was ever activated, which you cannot, and a reputable one would rather sort it out than lose you.

Work and KMS codes: why this article can’t fix them

If your key came from an employer, a college or an IT department, your PC is activating against an organisation’s own server rather than against Microsoft directly. The codes below describe that conversation failing, and none of them can be fixed from your desk.

The same applies to a machine telling you “Your Windows License Will Expire Soon” with no code attached. That is a volume licence client that has lost contact with its activation server, and Microsoft’s advice is to “Contact your system administrator for further assistance”. Reconnecting to the work network, in person or over the company VPN, resolves a surprising number of these on its own.

If you are the person running the network, this is deployment territory rather than troubleshooting — our guide to deploying Windows 11 across multiple PCs covers the licensing routes, and Microsoft licensing terms explained defines MAK, KMS and the rest.

If it still won’t activate

If the key came from us, talk to us before you do anything else. That is not a formality. We can see whether a key was ever activated and what the activation server has recorded against it, which is information you have no way of getting from the error message, and it is frequently the difference between a five-minute fix and someone paying twice for the same licence. Use the chat or open a support ticket from our customer help page; if you have already ordered, there is a priority support address in your order confirmation. If the key turns out to be genuinely faulty or blocked, we replace it.

The honest other case is a key bought somewhere that has since gone quiet, a marketplace listing that cannot be traced, or a machine that never had a valid licence in the first place. There is no diagnostic that rescues those, and past a certain point the time spent is worth more than the licence. If you are wondering how a genuine licence can be sold at the prices it is, we have set that out separately in whether reselling Microsoft licence keys is legal in the UK.

Frequently asked questions