| Previous | Next |
| SL_E_ISSUANCE_LICENSE_NOT_INSTALLED | SL_E_NONGENUINE_GRACE_TIME_EXPIRED |
SL_E_SLP_OEM_CERT_MISSING
The activation stage represented here
Interpret SL_E_SLP_OEM_CERT_MISSING inside OEM firmware activation, not as a generic activation failure. Windows has reached OEM activation that binds an OEM key and certificate or firmware marker to the edition and manufacturer data embedded by the device maker; in this case, the legacy OEM SLP installation lacks the OEM certificate needed to pair the key with firmware SLIC data.
This result is HRESULT 0xC004F063. Pair it with the selected product/Activation ID and operation name so later logs do not attribute an add-on, edition, or volume-license result to the base Windows product.
The surrounding licensing model prevents two common misdiagnoses. Legacy OEM SLP activation validates an OEM key and OEM certificate against the manufacturer-specific SLIC data in firmware; later OA3 systems use a firmware-injected product key workflow. A missing marker, malformed marker, missing certificate, and wrong marker version are different evidence states and are not repaired by changing KMS discovery settings.
Diagnostic sequence
- 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: OEM activation that binds an OEM key and certificate or firmware marker to the edition and manufacturer data embedded by the device maker.
- Prove the code-specific condition by collecting: record installed license/certificate inventory, OEM key channel, firmware OEM identifiers, edition and image provenance.
- Apply the distinction “firmware can be correct while the Windows-side OEM certificate is missing” 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.
A useful diagnostic record
Record installed license/certificate inventory, OEM key channel, firmware OEM identifiers, edition and image provenance. Before changing the system, add the following context:
- Product identity: hardware or firmware change preceding the failure.
- Activation context: system manufacturer/model and firmware version.
- State at failure: presence and version of the relevant ACPI licensing table or firmware marker.
- Correlation evidence: installed key channel and edition.
- Change history: OEM certificate presence where the mechanism requires it.
Related outcomes and why they are not equivalent
| Result | Different condition |
|---|---|
SL_E_SLP_BAD_FORMAT | Relative to this result: the OEM licensing data found in firmware cannot be parsed or validated in the required SLP format. |
SL_E_SLP_MISSING_SLP_MARKER | Different condition: the firmware licensing table exists, but the manufacturer-specific SLP marker required by the installed OEM license is absent. |
SL_E_SLP_MISSING_ACPI_SLIC | Different condition: the legacy OEM SLP path cannot find the ACPI SLIC table required to validate the OEM key and certificate. |
When it appears with related results, order them by timestamp and Activation ID. The earliest code from the producing component usually carries more diagnostic value than a later summary state.
firmware can be correct while the Windows-side OEM certificate is missing. A broad instruction to “try another key” or “check the Internet” would discard the more specific condition already established by the code.
Recovery without damaging licensing evidence
Resolve this code at its producing layer: restore the certificate only from legitimate manufacturer recovery media or use another valid activation channel. 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 generic reinstallation preserves the OEM key but omits the XML OEM certificate supplied by the manufacturer image.
Actions that usually make this harder to diagnose
- Avoid injecting unofficial firmware tables or certificates.
- Avoid assuming a motherboard replacement preserves the original OEM binding automatically.
Verification after the change
Verification should include a failing fixture for “the legacy OEM SLP installation lacks the OEM certificate needed to pair the key with firmware SLIC data” 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 OEM activation error guidance — supported tools and state fields used to verify the resulting state.
- OEM Activation 3.0 system — Microsoft guidance for the activation mechanism represented by this HRESULT.
- Microsoft activation error-code troubleshooting — platform behavior relevant to this HRESULT.
- Activate Windows — diagnostic and operational context.
Looking for a different code? Search another status or error code.