Fix it now
Microsoft publishes no meaning for these four codes, and no page states that token activation refuses exportable keys as a rule. What it does document is that the PIN argument on the activation command exists for hardware-protected certificates such as smart cards. Establish where your key is held, then ask the policy’s author what it accepts.
slmgr /lil
slmgr /ltc
slui.exe 0x2a 0xC004F311
slmgr /lillists the installed issuance licences. Nothing listed is a different problem: the policy is not on the machine at all.slmgr /ltclists the certificates the licensing service considers usable. A software certificate that never appears here is not going to be accepted by anything you type next.- Read Microsoft’s own text for the code with
slui.exe 0x2a, substituting the code you have. - Establish which provider holds the private key for the certificate you are offering. A key in a software provider and a key on a card are different credentials even when the subject name is identical.
- Insert the hardware credential, wait for it to enumerate, then activate with the thumbprint explicitly:
slmgr /fta <thumbprint> <PIN>.
Where a software certificate and a card certificate carry the same subject name, remove the software copy so the wrong credential cannot be selected, and always pass the thumbprint on the command line.
If that fixed it you can stop here. If not, the next section explains what is actually documented about this method and what to ask the team that issued your licence.
Why it happens
Token-based activation is designed for networks that cannot reach Microsoft and cannot run internal activation infrastructure. Because there is no service-side check at activation time, the security of the arrangement rests on the credential. Microsoft’s documentation describes the method in terms of smart cards throughout, and the clearest published signal is in the activation command itself: the optional PIN argument on slmgr /fta is documented as unlocking the private key without a prompt for hardware-protected certificates such as smart cards.
What is not published is any statement that a certificate whose private key can be exported is refused, or that this is enforced by a check on the key container. Earlier versions of this article asserted both, and asserted that no registry value, policy setting or command line switch could change it. Those claims had no acceptable source and have been removed. If your environment cannot issue hardware credentials, ask the team that produced your issuance licence what the policy accepts before you conclude that the method is closed to you.
None of 0xC004F311, 0xC004F312, 0xC004F30B or 0xC004F30A has a published meaning. What can be said is where they appear: during token-based activation, when the credential offered and the installed issuance licence do not produce a usable pairing. slui.exe 0x2a followed by the code gives you Microsoft’s own wording for the build in front of you, which is a better basis for a support conversation than anybody’s table.
The practical structure of the problem is the same as for the rest of this family. slmgr /lil tells you whether a policy is installed. slmgr /ltc tells you whether any credential the machine can see satisfies it. If the certificate you intend to use never appears in the second list, the question to answer is why – which credential store holds it, which authority issued it, and whether it is the kind of credential your issuance licence was written for.
The certificate is a software copy imported from a file
You have this one if The certificate is in the personal store with no card inserted, and it was installed by opening a .pfx or .p12 file.
- Establish which provider holds the private key for that certificate before anything else.
- Remove the software copy if a hardware credential with the same subject name also exists, so the wrong one cannot be picked.
- Have the certificate issued onto the hardware credential your issuance licence was written for.
- Enrol it, confirm it appears in
slmgr /ltc, then activate withslmgr /fta.
Reimporting the same file with a different exportability setting does not move the key to different hardware. It is the same credential in the same place.
No issuance licence is installed
You have this one if slmgr /lil returns nothing, and Event ID 12321 appears with HR=0xC004F011.
- Obtain the issuance licence file for this edition from whoever administers your token activation policy.
- Install it with
slmgr /ilc <full path to the .xrm-ms file>. - Confirm it registered with
slmgr /lil. - Restart the licensing service and retry.
This is Microsoft’s documented cause for that event, and it is worth ruling out before you spend time on credentials.
The card is present but Windows cannot open it
You have this one if The reader appears but no certificate or key container is visible, and slmgr /ltc returns nothing.
- Confirm the Smart Card service and the service that surfaces cards to applications are both running.
- Install the card vendor’s minidriver or middleware, then reinsert the card.
- Re-check that a certificate and a container are both visible before trying to activate.
- Retry
slmgr /fta <thumbprint> <PIN>.
Several credentials are present and the wrong one is chosen
You have this one if A card certificate and a software certificate share a subject name, and results vary between attempts.
- Enumerate both stores and work out which is which.
- Remove the copy you do not intend to use, so only one credential remains.
- Always pass the thumbprint explicitly on the command line, so a wrong selection is impossible rather than merely unlikely.
The credential type is not what the policy was written for
You have this one if A credential that looks correct in every respect – the right subject, a valid chain, a non-exportable key – and activation is still refused.
- Ask the team that produced the issuance licence which credentials it was written to accept, including which root it expects the certificate to chain to.
- Test one credential of the type you intend to standardise on before deploying it widely.
- Where the answer is that the policy does not cover it, a new issuance licence is the fix rather than a change on the endpoint.
This applies to TPM-backed virtual smart cards too. Whether one is acceptable depends on the policy in your issuance licence, and no general rule can tell you. Test one before planning around it.
Full reference
What is published about these codes
| Code | Status |
|---|---|
0xC004F311 |
No published meaning found on learn.microsoft.com or support.microsoft.com |
0xC004F312 |
No published meaning found |
0xC004F30B |
No published meaning found |
0xC004F30A |
No published meaning found |
The published statement that comes closest to describing the credential requirement is not a code at all: it is Microsoft’s description of the PIN argument on slmgr /fta, which exists to unlock the private key without a prompt for hardware-protected certificates such as smart cards. That tells you the method was designed around cards. It does not tell you that a software certificate is rejected by a specific check, and this article no longer claims that it does.
Checking a credential before you deploy it
| Check | What a good result looks like |
|---|---|
| The card enumerates | A reader, a card, a key container and a certificate all visible without errors |
slmgr /lil |
At least one issuance licence installed for the edition on this machine |
slmgr /ltc |
The intended thumbprint appears in the list of usable certificates |
slmgr /fta <thumbprint> <PIN> |
Completes without returning a code |
slmgr /dlv |
Licence status reads Licensed afterwards |
Do this on one machine and one credential before you enrol an estate. The cost of finding out that the policy does not accept your chosen credential type is one card if you test, and a reissuance programme if you do not.
What to ask before you standardise on a credential
- Which credential types was this issuance licence written to accept?
- Which root must the certificate chain to, and has that authority changed since the licence was produced?
- Which template should cards be issued from?
- Are TPM-backed virtual smart cards acceptable under this policy, or only physical cards?
- Who can issue a replacement issuance licence if the answer to any of these changes?
If token-based activation is not viable here
Where the environment genuinely cannot issue the credentials your policy requires, the question becomes which activation method fits instead. For domain-joined machines in a forest, Active Directory-based activation needs no host, no port and no count threshold, and the client carries only its generic volume licence key. For machines that are not forest members, a Key Management Service host or MAK keys are the alternatives. Which of those is available to you depends on your volume agreement rather than on anything you can configure.
The one thing worth doing on every attempt
Pass the thumbprint explicitly. slmgr /fta takes it as its first argument, and supplying it removes the possibility that a different credential with the same subject name was selected. On a machine that has both a card certificate and a software copy, that ambiguity is the single most common reason two people running the same command get different results.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F311 |
Reported when token-based activation refuses the credential offered. No published meaning; read the machine’s own text with slui.exe 0x2a | not published by the vendor |
0xC004F312 |
Reported in the same token activation family. No published meaning | not published by the vendor |
0xC004F30B |
Reported in the same token activation family, typically where the certificate cannot be used with its key container. No published meaning | not published by the vendor |
0xC004F30A |
Reported in the same token activation family. No published meaning | not published by the vendor |
Confirm the fix worked
slmgr /lillists an issuance licence for the edition installed.slmgr /ltclists the credential you intend to use.slmgr /fta <thumbprint> <PIN>completes without returning a code.slmgr /dlvreports a licence status of Licensed.- Remove the credential and reboot; the activation state should persist without it being present.
Questions people ask about this
Is there a policy that allows software certificates for activation?
Microsoft does not publish an answer to this either way, so this article will not give you one. What is documented is that the PIN argument on slmgr /fta exists for hardware-protected certificates such as smart cards. Ask the team that produced your issuance licence what its policy accepts.
Does buying a licence fix this?
No. The entitlement for token-based activation is in the issuance licence already installed on the machine. What is in question is the credential, which comes from your own public key infrastructure.
Can I use a certificate on a USB hardware token rather than a card?
Possibly, and the only way to know is to test one against your issuance licence. The policy lives in a signed file produced by your organisation, and no general rule about token types can answer for it.
What if the machine has no card reader at all?
Then this method is not available to it, and the question is which of the alternatives your agreement covers – Active Directory-based activation for forest-joined machines, a KMS host, or MAK keys. Which of those carries a cost depends on your agreement rather than on the activation method.
Why has this article stopped saying that exportable keys are always refused?
Because no acceptable source publishes it. It may well be true of your policy; it is not something this article can assert on Microsoft’s behalf, and stating it as a universal rule sent readers away from the questions that would actually resolve their case.
