| 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 the 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: 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.
What to collect from the affected system
The decisive record is to capture the exact LicenseStatusReason, GenuineStatus, grace duration, triggering validation result and prior state transition. Before changing the system for this HRESULT, add the following context:
- Product identity for this HRESULT: GracePeriodRemaining and EvaluationEndDate.
- Activation context for this HRESULT: trusted time and recent time-service events.
- State at failure for this HRESULT: hardware or firmware changes affecting binding.
- Correlation evidence for this HRESULT: activation channel, partial product key and last successful activation/renewal.
- Change history for this HRESULT: LicenseStatus and LicenseStatusReason for the exact Activation ID.
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_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 | Relative to it: the license has entered an out-of-tolerance grace interval after hardware or binding change exceeded the normal tolerance. |
SL_I_OOB_GRACE_PERIOD | Relative to it: the product is operating in its initial out-of-box grace period before activation is required. |
These values can appear in the same deployment but are not interchangeable. Preserve the first exact result in the failing operation; later notification, retry, or state-query codes may only describe the consequence.
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 decisive 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. Automation handling it should route the result to the owner of that layer rather than starting every recovery path at once.
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.
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 it 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 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.