| Previous | Next |
| SL_E_NONGENUINE_GRACE_TIME_EXPIRED_2 | SL_E_OPERATION_NOT_ALLOWED |
SL_E_MISMATCHED_PRODUCT_SKU
What Windows has already determined
Interpret SL_E_MISMATCHED_PRODUCT_SKU inside product-key and edition matching, not as a generic activation failure. Windows has reached validation and installation of a product key against the installed edition, activation channel, SKU, PID configuration and license package; in this case, the requested or licensed SKU cannot be matched to an installed product SKU.
The stored HRESULT is 0xC004F069. 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 installed SoftwareLicensingProduct IDs, edition/SKU, license package identities and the Activation ID used by the caller. Before changing the system, add the following context:
- Product identity: installed license package/SKU inventory.
- Activation context: operation used to install, change, validate or activate the key.
- State at failure: current edition and Activation ID.
- Correlation evidence: key channel/type and only the partial product key in ordinary logs.
- Change history: Product ID and PID configuration.
How to test the failing stage
- Identify whether this result came from key installation, activation, renewal, validation, certificate selection, offline deposit, or status query.
- Tie that call to full key held securely, partial product key for logs, key channel/type, Product ID, Activation ID, edition/SKU and installed license package.
- Capture the proof needed for this specific result: enumerate installed SoftwareLicensingProduct IDs, edition/SKU, license package identities and the Activation ID used by the caller.
- Use the related-code comparison below to avoid correcting the wrong layer.
- Retest with a fresh operation instance and confirm that no parallel retry or stale response can overwrite the result.
Two platform rules are especially relevant to this result. 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.
Do not infer the cause of this result from the activation UI alone. The product family may be present while the exact SKU is absent. Keep the exact HRESULT in user-facing diagnostics instead of collapsing it into a generic activation failure.
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.
Nearby results that require a different response
| Result | Different condition |
|---|---|
SL_E_PKEY_INVALID_UPGRADE | Different condition: the supplied key grants an upgrade path and cannot activate a clean installation lacking the qualifying base state. |
SL_E_BASE_SKU_NOT_AVAILABLE | Different condition: an add-on or edition license depends on a base SKU that is not installed or available. |
SL_E_INVALID_PRODUCT_KEY_TYPE | Different condition: the key type is incompatible with the selected activation method. |
Recommended handling
Resolve this code at its producing layer: target the installed SKU or install the licensed edition/package that provides the expected SKU. A successful command is not enough by itself; verify the stored licensing state and any renewal, validity, or binding data affected by the operation.
Representative failure: A management script uses an Activation ID from a different image edition.
Verification after the change
Verification should include a failing fixture for “the requested or licensed SKU cannot be matched to an installed product SKU” and a passing fixture after the targeted fix. Reboot or restart only when the documented mechanism requires it, and confirm that the state persists afterward.
Technical references
- Microsoft activation error-code troubleshooting — diagnostic and operational context.
- Plan for volume activation — supported tools and state fields used to verify the resulting state.
- KMS client activation keys — Microsoft guidance for the activation mechanism represented by this HRESULT.
- Slmgr.vbs activation options — platform behavior relevant to this HRESULT.
Looking for a different code? Search another status or error code.