| Previous | Next |
| SL_E_VL_AD_SCHEMA_VERSION_NOT_SUPPORTED | SL_E_EDITION_MISMATCHED |
SL_E_NOT_GENUINE
The activation stage represented here
Interpret SL_E_NOT_GENUINE inside license state, grace and validity, not as a generic activation failure. Windows has reached the Software Protection Platform state machine that evaluates whether a license is active, in a grace or validity interval, out of tolerance, expired, non-genuine, or in notification; in this case, the Software Protection Platform’s genuine-state evaluation does not accept the current Windows licensing state.
The stored HRESULT is 0xC004F200. 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.
Two platform rules are especially relevant to this result. for this HRESULT: Informational licensing HRESULTs can describe a valid grace or time-based state even though the value is not S_OK; callers should inspect severity and state rather than treating every nonzero code as failure. for this HRESULT: Grace expiration, validity expiration, hardware out-of-tolerance, non-genuine state, and notification mode have different causes and transitions even when the user sees a similar activation banner.
A practical investigation order
- Preserve this result,
0xC004F200, 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 producing boundary directly: record GenuineStatus, LicenseStatusReason, key channel/partial key, validation events, image integrity and activation history.
- do not continue until the evidence supports this distinction: non-genuine is not synonymous with merely unactivated; a system can fail genuine validation for key, binding or integrity reasons.
- perform the targeted action, then repeat the same query/activation path and compare state, events, and expiry/renewal information.
Signals that separate this case from its neighbors
The decisive record is to record GenuineStatus, LicenseStatusReason, key channel/partial key, validation events, image integrity and activation history. Before changing the system for this HRESULT, add the following context:
- Product identity for this HRESULT: LicenseStatus and LicenseStatusReason for the exact Activation ID.
- Activation context for this HRESULT: GracePeriodRemaining and EvaluationEndDate.
- State at failure for this HRESULT: trusted time and recent time-service events.
- Correlation evidence for this HRESULT: hardware or firmware changes affecting binding.
- Change history for this HRESULT: activation channel, partial product key and last successful activation/renewal.
When investigating this result, protect secrets while collecting evidence. Full product keys, complete IID/CID values, private keys, PINs, challenge blobs, account credentials, and unredacted certificate material for this HRESULT do not belong in public tickets. Partial keys, hashes, thumbprints, IDs, timestamps, and state transitions are normally enough to correlate the failure.
Related outcomes and why they are not equivalent
| Result | Different boundary |
|---|---|
SL_E_NONGENUINE_GRACE_TIME_EXPIRED_2 | Relative to this result: the second non-genuine grace category has expired. |
SL_E_NONGENUINE_GRACE_TIME_EXPIRED | Relative to it: the first non-genuine remediation grace period has ended without restoring a genuine license state. |
SL_E_VALIDITY_TIME_EXPIRED | Relative to it: the license’s validity time check has expired at evaluation. |
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.
The diagnostic fork is precise: non-genuine is not synonymous with merely unactivated; a system can fail genuine validation for key, binding or integrity reasons. A broad instruction for this HRESULT to “try another key” or “check the Internet” would discard what this HRESULT already established.
The narrow remediation path
Recovery should preserve entitlement and state rather than erase symptoms. In this case, use legitimate media and entitlement, correct the precise validation cause, and re-evaluate genuine status; then query the same product instance and retain the post-fix it HRESULT and status.
Representative failure: A previously activated image has inconsistent license or system-file evidence and fails genuine validation.
Actions that usually make this harder to diagnose
- While diagnosing it, avoid resetting licensing state merely to hide an expired or non-genuine condition. That action changes evidence for this HRESULT without correcting the established boundary.
- avoid interpreting a positive informational HRESULT as an activation failure without checking LicenseStatus. The result already narrows the problem more precisely.
- do not delete licensing stores, edit signed license files, alter firmware markers, bypass certificate checks, or use unofficial activation tools. During investigation, those actions can create a second integrity problem and destroy the evidence needed to repair the legitimate license.
Verification after the change
After remediating it, repeat the original operation rather than relying on the absence of a notification banner. Confirm that it is no longer produced and that the intended product instance reports the expected durable licensing state.
Technical references
- SoftwareLicensingProduct WMI class — supported tools and state fields used to verify it.
- WMI properties for volume activation — Microsoft guidance for the activation mechanism represented by it.
- Slmgr.vbs activation options — platform behavior relevant to it.
- Microsoft activation error-code troubleshooting — diagnostic and operational context for this HRESULT.
Looking for a different code? Search another status or error code.