| Previous | Next |
| SL_I_TIMEBASED_VALIDITY_PERIOD | SL_I_TIMEBASED_EXTENDED_GRACE_PERIOD |
SL_I_PERPETUAL_OOB_GRACE_PERIOD
How to interpret this result
Interpret SL_I_PERPETUAL_OOB_GRACE_PERIOD 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 licensing policy grants an out-of-box grace state without the ordinary countdown to expiry.
Record both this result and 0x4004FC05. 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.
Signals that separate this case from its neighbors
The decisive record is to record license policy identity, LicenseStatusReason, GracePeriodRemaining representation, edition and activation channel. Before changing the system for this HRESULT, add the following context:
- Product identity for this HRESULT: activation channel, partial product key and last successful activation/renewal.
- Activation context for this HRESULT: LicenseStatus and LicenseStatusReason for the exact Activation ID.
- State at failure for this HRESULT: GracePeriodRemaining and EvaluationEndDate.
- Correlation evidence for this HRESULT: trusted time and recent time-service events.
- Change history for this HRESULT: hardware or firmware changes affecting binding.
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.
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.
How to correct the producing condition
Use the narrow remediation: honor the applicable license policy and avoid repeatedly attempting activation unless the product workflow requires it. Avoid simultaneous key changes, store resets, service restarts, and network changes because they make it impossible to identify which precondition mattered.
Representative failure: A specialized image reports a persistent grace status by design rather than an activation timer.
The most useful separator is this: perpetual grace is policy-defined and should not be mistaken for a normal activated Licensed state. That this result distinction determines whether the next action belongs to key/edition selection, the activation endpoint, certificate policy, firmware, trusted time, or persistent licensing state.
Choose recovery by the producing stage
| Result | Different boundary |
|---|---|
SL_I_TIMEBASED_EXTENDED_GRACE_PERIOD | Relative to it: the product is within an extended grace interval associated with a time-based license. |
SL_I_TIMEBASED_VALIDITY_PERIOD | Relative to it: the license is currently valid only within its configured time-based validity interval. |
SL_I_STORE_BASED_ACTIVATION | Relative to it: the current product activation is backed by a Store-delivered license rather than a conventional installed key channel alone. |
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.
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
Build a regression case that intentionally creates “the licensing policy grants an out-of-box grace state without the ordinary countdown to expiry” and asserts it. The corrected the case should change only the decisive input, then verify the same Activation ID, final LicenseStatus/Reason, and any relevant grace, renewal, certificate, binding, or expiry data.
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.