| Previous | Next |
| SL_I_NONGENUINE_GRACE_PERIOD | SL_I_STORE_BASED_ACTIVATION |
SL_I_NONGENUINE_GRACE_PERIOD_2
What this result narrows down
SL_I_NONGENUINE_GRACE_PERIOD_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 boundary is: the installation is in the second defined non-genuine grace category used by the licensing state machine.
Record both this result and 0x4004F068. Licensing wrappers often preserve only a friendly message, but the facility value is what separates key, KMS, certificate, offline, OEM, Store, and state-machine failures.
This result should be read against these rules: 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. 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.
What to collect from the affected system
Capture the exact LicenseStatusReason, GenuineStatus, grace duration, triggering validation result and prior state transition. Before changing the system, add the following context:
- Product identity: GracePeriodRemaining and EvaluationEndDate.
- Activation context: trusted time and recent time-service events.
- State at failure: hardware or firmware changes affecting binding.
- Correlation evidence: activation channel, partial product key and last successful activation/renewal.
- Change history: LicenseStatus and LicenseStatusReason for the exact Activation ID.
Related outcomes and why they are not equivalent
| Result | Different condition |
|---|---|
SL_I_NONGENUINE_GRACE_PERIOD | Relative to this result: genuine validation placed the installation in the first valid non-genuine grace state before enforcement or notification transition. |
SL_I_OOT_GRACE_PERIOD | Different condition: the license has entered an out-of-tolerance grace interval after hardware or binding change exceeded the normal tolerance. |
SL_I_OOB_GRACE_PERIOD | Different condition: the product is operating in its initial out-of-box grace period before activation is required. |
Checks in the order that matters
- Select the exact licensing product or Activation ID that returned it; do not rely only on the first line of
slmgr /dlv. - Confirm the mechanism in use: 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.
- Prove the code-specific condition by collecting: capture the exact LicenseStatusReason, GenuineStatus, grace duration, triggering validation result and prior state transition.
- Apply the distinction “the type-2 state should be preserved in telemetry rather than collapsed with the first non-genuine grace result” 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.
It is actionable because the type-2 state should be preserved in telemetry rather than collapsed with the first non-genuine grace result.
Actions that usually make this harder to diagnose
- Avoid resetting licensing state merely to hide an expired or non-genuine condition.
- Avoid interpreting a positive informational HRESULT as an activation failure without checking LicenseStatus.
How to correct the producing condition
Recovery should preserve entitlement and state rather than erase symptoms. In this case, correct the underlying licensing/validation issue and verify transition to Licensed, not merely disappearance of UI notification; then query the same product instance and retain the post-fix it HRESULT and status.
Representative failure: An enterprise inventory agent encounters the alternate non-genuine grace reason and must report it distinctly.
Verification after the change
A useful test records the before/after values for the exact Activation ID. It should prove that the correction removes “the installation is in the second defined non-genuine grace category used by the licensing state machine” without replacing it with a different key, KMS, certificate, OEM, Store, or validity failure.
Technical references
- SoftwareLicensingProduct WMI class — platform behavior relevant to this HRESULT.
- WMI properties for volume activation — diagnostic and operational context.
- Slmgr.vbs activation options — supported tools and state fields used to verify the resulting state.
- Microsoft activation error-code troubleshooting — Microsoft guidance for the activation mechanism represented by this HRESULT.
Looking for a different code? Search another status or error code.