| Previous | Next |
| SL_E_DEPENDENT_PROPERTY_NOT_SET | SL_E_MISMATCHED_PRODUCT_SKU |
SL_E_NONGENUINE_GRACE_TIME_EXPIRED_2
Where this licensing result is produced
SL_E_NONGENUINE_GRACE_TIME_EXPIRED_2 belongs to license state, grace and validity. The producing mechanism is 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. The important the boundary is: the second non-genuine grace category has expired.
Telemetry should retain 0xC004F067, 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.
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 useful diagnostic record
The decisive record is to capture its distinct LicenseStatusReason, prior type-2 informational state, validation evidence and transition timestamp. Before changing the system for this HRESULT, add the following context:
- Product identity for this HRESULT: trusted time and recent time-service events.
- Activation context for this HRESULT: hardware or firmware changes affecting binding.
- State at failure for this HRESULT: activation channel, partial product key and last successful activation/renewal.
- Correlation evidence for this HRESULT: LicenseStatus and LicenseStatusReason for the exact Activation ID.
- Change history for this HRESULT: GracePeriodRemaining and EvaluationEndDate.
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.
Diagnostic sequence
- Begin with the operation that emitted this result and its target Activation ID.
- inventory Activation ID, LicenseStatus, LicenseStatusReason, GracePeriodRemaining, EvaluationEndDate, GenuineStatus, trusted time and hardware binding; this establishes whether the request was aimed at the intended product and activation channel.
- use events and tool output to demonstrate: capture its distinct LicenseStatusReason, prior type-2 informational state, validation evidence and transition timestamp.
- rule out the adjacent case: keeping the type-2 reason avoids conflating two different state-machine paths with identical UI symptoms.
- After the narrow correction for this HRESULT, verify both the immediate HRESULT and the persistent licensing state after service restart or reboot when relevant.
Do not infer the cause of it from the activation UI alone. Keeping the type-2 reason avoids conflating two different state-machine paths with identical UI symptoms. Preserve the boundary when converting the HRESULT into user-facing diagnostics.
Related outcomes and why they are not equivalent
| Result | Different boundary |
|---|---|
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. |
SL_E_OUT_OF_TOLERANCE | Relative to it: the current hardware identity differs from the licensed binding beyond the allowed tolerance. |
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.
Corrective direction
Recovery should preserve entitlement and state rather than erase symptoms. In this case, resolve the underlying validation/licensing cause and confirm genuine status through the exact Activation ID; then query the same product instance and retain the post-fix it HRESULT and status.
Representative failure: Monitoring detects expiry of the alternate non-genuine grace state on a managed endpoint.
Actions that usually make this harder to diagnose
- While diagnosing it, avoid interpreting a positive informational HRESULT as an activation failure without checking LicenseStatus. That action changes evidence for this HRESULT without correcting the established boundary.
- avoid resetting licensing state merely to hide an expired or non-genuine condition. 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 — platform behavior relevant to it.
- WMI properties for volume activation — diagnostic and operational context for this HRESULT.
- Slmgr.vbs activation options — supported tools and state fields used to verify it.
- Microsoft activation error-code troubleshooting — Microsoft guidance for the activation mechanism represented by it.
Looking for a different code? Search another status or error code.