| Previous | Next |
| SL_E_RIGHT_NOT_GRANTED | SL_E_PRODUCT_SKU_NOT_INSTALLED |
SL_E_PKEY_NOT_INSTALLED
What the licensing code means
SL_E_PKEY_NOT_INSTALLED identifies a specific point in product-key and edition matching: validation and installation of a product key against the installed edition, activation channel, SKU, PID configuration and license package. Its diagnostic consequence is that the target Activation ID has no product key installed or available for the requested licensing operation.
Telemetry should retain 0xC004F014, this result, and the affected Activation ID. The same computer can expose several licensing products, and a state read from the wrong instance can contradict the operation that actually failed.
Data that identifies the actual cause
To verify this, enumerate SoftwareLicensingProduct instances, Activation ID, partial product key, product description and key installation history. Before changing the system, add the following context:
- Product identity: operation used to install, change, validate or activate the key.
- Activation context: current edition and Activation ID.
- State at failure: key channel/type and only the partial product key in ordinary logs.
- Correlation evidence: Product ID and PID configuration.
- Change history: installed license package/SKU inventory.
Do not infer the cause of this result from the activation UI alone. A missing key differs from an installed but invalid or blocked key. Keep the exact HRESULT in user-facing diagnostics instead of collapsing it into a generic activation failure.
The surrounding licensing model prevents two common misdiagnoses. Key installation and activation are separate operations: successful installation does not prove that entitlement, activation limits, or server-side policy will allow activation. A syntactically well-formed key can still be unusable because its channel, edition, key range, upgrade rights, or Activation ID does not match the installed product.
Checks in the order that matters
- Select the exact licensing product or Activation ID that returned this result; do not rely only on the first line of
slmgr /dlv. - Confirm the mechanism in use: validation and installation of a product key against the installed edition, activation channel, SKU, PID configuration and license package.
- Prove the code-specific condition by collecting: enumerate SoftwareLicensingProduct instances, Activation ID, partial product key, product description and key installation history.
- Apply the distinction “a missing key differs from an installed but invalid or blocked key” before choosing a key, network, certificate, firmware, time, or entitlement repair.
- Change one relevant precondition, rerun one activation/evaluation operation, and verify the resulting LicenseStatus and LicenseStatusReason.
Do not collapse these related states
| Result | Different condition |
|---|---|
SL_E_INVALID_PKEY | Different condition: the local licensing layer rejects the selected product key before it can authorize the current product. |
SL_E_MISMATCHED_PID | Different condition: the Product ID derived from or associated with the key does not match the Product ID expected by the license. |
SL_E_MISMATCHED_PKEY_RANGE | Different condition: the product key falls outside the key range declared by the installed license package. |
Actions that usually make this harder to diagnose
- Avoid cycling through unrelated keys without first identifying edition and channel.
- Avoid publishing a complete product key in logs, tickets or screenshots.
Targeted fix
The appropriate correction is to install the correct key for that Activation ID or select the product instance that already owns the intended key. Keep the original evidence until a subsequent status query confirms that the intended Activation ID reached the expected state.
Representative failure: An activation script targets an add-on Activation ID that has no key while the base OS has a different key.
Verification after the change
Build a regression case that intentionally creates “the target Activation ID has no product key installed or available for the requested licensing operation” 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
- Microsoft activation error-code troubleshooting — Microsoft guidance for the activation mechanism represented by this HRESULT.
- Plan for volume activation — platform behavior relevant to this HRESULT.
- KMS client activation keys — diagnostic and operational context.
- Slmgr.vbs activation options — supported tools and state fields used to verify the resulting state.
Looking for a different code? Search another status or error code.