| Previous | Next |
| SL_I_PERPETUAL_OOB_GRACE_PERIOD | NS_I_TIGER_START |
SL_I_TIMEBASED_EXTENDED_GRACE_PERIOD
Where this licensing result is produced
SL_I_TIMEBASED_EXTENDED_GRACE_PERIOD identifies a specific point in license state, grace and validity: 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. Its diagnostic consequence is that the product is within an extended grace interval associated with a time-based license.
Record both this result and 0x4004FC06. 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
Record original validity end, extended-grace limit, trusted time, LicenseStatusReason and the event that entered extension. Before changing the system, add the following context:
- Product identity: activation channel, partial product key and last successful activation/renewal.
- Activation context: LicenseStatus and LicenseStatusReason for the exact Activation ID.
- State at failure: GracePeriodRemaining and EvaluationEndDate.
- Correlation evidence: trusted time and recent time-service events.
- Change history: hardware or firmware changes affecting binding.
The surrounding licensing model prevents two common misdiagnoses. 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.
Work from state to cause
- 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: record original validity end, extended-grace limit, trusted time, LicenseStatusReason and the event that entered extension.
- Rule out the adjacent case: extension is not a new perpetual license and differs from the primary validity period.
- After the targeted fix, verify both the immediate HRESULT and the persistent licensing state after service restart or reboot when relevant.
Corrective direction
Use the targeted fix: renew or replace the time-based entitlement before extended grace ends, then verify the state transition. Avoid simultaneous key changes, store resets, service restarts, and network changes because they make it impossible to identify which precondition mattered.
Representative failure: A temporary license passes its nominal end date and enters the configured extension window.
The diagnostic fork is precise: extension is not a new perpetual license and differs from the primary validity period. A broad instruction to “try another key” or “check the Internet” would discard the more specific condition already established by the code.
Do not collapse these related states
| Result | Different condition |
|---|---|
SL_I_PERPETUAL_OOB_GRACE_PERIOD | Relative to this result: the licensing policy grants an out-of-box grace state without the ordinary countdown to expiry. |
SL_I_TIMEBASED_VALIDITY_PERIOD | Different condition: the license is currently valid only within its configured time-based validity interval. |
SL_I_STORE_BASED_ACTIVATION | Different condition: the current product activation is backed by a Store-delivered license rather than a conventional installed key channel alone. |
Actions that usually make this harder to diagnose
- Avoid interpreting a positive informational HRESULT as an activation failure without checking LicenseStatus.
- Avoid resetting licensing state merely to hide an expired or non-genuine condition.
Verification after the change
Build a regression case that intentionally creates “the product is within an extended grace interval associated with a time-based license” and asserts it. The corrected case should change only the relevant 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 the resulting state.
- WMI properties for volume activation — Microsoft guidance for the activation mechanism represented by this HRESULT.
- Slmgr.vbs activation options — platform behavior relevant to this HRESULT.
- Microsoft activation error-code troubleshooting — diagnostic and operational context.
Looking for a different code? Search another status or error code.