| Previous | Next |
| SL_E_TKA_THUMBPRINT_CERT_NOT_FOUND | SL_E_TKA_TPID_MISMATCH |
SL_E_TKA_CRITERIA_MISMATCH
What the licensing code means
Interpret SL_E_TKA_CRITERIA_MISMATCH inside token-based activation, not as a generic activation failure. Windows has reached certificate-backed token activation for approved volume-licensing scenarios in isolated or high-security environments; in this case, the candidate certificate fails one or more explicit criteria in the token issuance license.
The stored HRESULT is 0xC004F30F. Keep that value, the symbolic name, and the target Activation ID together; converting it to a generic “Windows is not activated” status discards the stage that selected the next diagnostic step.
Evidence to preserve before changing anything
To verify this, enumerate each criterion and candidate value: issuer, subject, OID, EKU, key provider, hardware protection, validity and organization attributes. Before changing the system, add the following context:
- Product identity: private-key provider and exportability flag.
- Activation context: challenge/grant correlation and relevant licensing event IDs.
- State at failure: target Activation ID and SKU.
- Correlation evidence: installed token issuance license identity.
- Change history: certificate thumbprint, subject, issuer and validity interval.
This result is actionable because the chain and thumbprint may be valid; policy matching is the failing stage.
This result should be read against these rules: Certificate discovery, chain validation, challenge matching, grant parsing, and policy matching are distinct stages, so a generic certificate reinstall can conceal the failing stage. Token-based activation is a specialized volume activation method; the issuance license describes certificate criteria and is not interchangeable with a KMS host key or MAK.
A reproducible troubleshooting path
- Preserve this result,
0xC004F30F, timestamp, caller, and the exact licensing method. - Read the current product state before making changes, including key channel, LicenseStatusReason, and relevant time or binding data.
- Test the documented condition directly: enumerate each criterion and candidate value: issuer, subject, OID, EKU, key provider, hardware protection, validity and organization attributes.
- Do not continue until the evidence supports this distinction: the chain and thumbprint may be valid; policy matching is the failing stage.
- Perform the targeted action, then repeat the same query/activation path and compare state, events, and expiry/renewal information.
Do not collapse these related states
| Result | Different condition |
|---|---|
SL_E_TKA_THUMBPRINT_CERT_NOT_FOUND | Different condition: the supplied thumbprint is well formed but no visible certificate matches it. |
SL_E_TKA_TPID_MISMATCH | Different condition: the certificate trust-point identifier does not match the TPID required by the token issuance license. |
SL_E_TKA_INVALID_THUMBPRINT | Different condition: the certificate thumbprint supplied to token activation is syntactically invalid or uses an unacceptable representation. |
Choosing remediation by the symbolic code prevents an entitlement problem from being treated as transport failure, or a state-transition result from being treated as a bad product key.
Actions that usually make this harder to diagnose
- Avoid switching to a weaker certificate merely to bypass issuance-license criteria.
- Avoid exporting or replacing private keys before preserving certificate and provider evidence.
Targeted fix
Recovery should preserve entitlement and state rather than erase symptoms. In this case, issue or select a certificate that satisfies the complete approved criteria rather than relaxing the issuance policy; then query the same product instance and retain the post-fix it HRESULT and status.
Representative failure: A certificate chains correctly but lacks the required activation EKU.
Verification after the change
Build a regression case that intentionally creates “the candidate certificate fails one or more explicit criteria in the token issuance license” and asserts it. The corrected case should change only the relevant input, then verify the same Activation ID, final LicenseStatus/Reason, and any relevant grace, renewal, certificate, binding, or expiry data.
Technical references
- Plan for volume activation — Microsoft guidance for the activation mechanism represented by this HRESULT.
- Slmgr.vbs token-activation options — platform behavior relevant to this HRESULT.
- Microsoft token-activation event guidance — diagnostic and operational context.
- SoftwareLicensingProduct WMI class — supported tools and state fields used to verify the resulting state.
Looking for a different code? Search another status or error code.