| Previous | Next |
| E_RM_UNKNOWN_ERROR | SL_E_IA_THROTTLE_LIMIT_EXCEEDED |
SL_E_VALIDITY_PERIOD_EXPIRED
The activation stage represented here
SL_E_VALIDITY_PERIOD_EXPIRED 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 configured time-based license validity period has ended.
The stored HRESULT is 0xC004FC07. Keep that value, the symbolic name, and the target Activation ID together; converting it to a generic “Windows is not activated” status discards the stage that selected the next diagnostic step.
Keep the mechanism’s contract in view: for it: 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. In addition, the second rule for it is: for it: 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.
The diagnostic fork is precise: validity expiry is a contractual time boundary, not failed KMS discovery or hardware tolerance. A broad instruction for it to “try another key” or “check the Internet” would discard what this HRESULT already established.
Data that identifies the actual cause
The decisive record is to record EvaluationEndDate, trusted time, license type, Activation ID and whether an extended-grace policy exists. Before changing the system for it, add the following context:
- Product identity for it: trusted time and recent time-service events.
- Activation context for it: hardware or firmware changes affecting binding.
- State at failure for it: activation channel, partial product key and last successful activation/renewal.
- Correlation evidence for it: LicenseStatus and LicenseStatusReason for the exact Activation ID.
- Change history for it: 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 it do not belong in public tickets. Partial keys, hashes, thumbprints, IDs, timestamps, and state transitions are normally enough to correlate the failure.
Work from state to cause
- Identify whether this result came from key installation, activation, renewal, validation, certificate selection, offline deposit, or status query.
- tie that call to Activation ID, LicenseStatus, LicenseStatusReason, GracePeriodRemaining, EvaluationEndDate, GenuineStatus, trusted time and hardware binding.
- capture the proof needed for this specific result: record EvaluationEndDate, trusted time, license type, Activation ID and whether an extended-grace policy exists.
- use the related-code comparison below to avoid correcting the wrong layer.
- retest with a fresh operation generation and confirm that no parallel retry or stale response can overwrite the result.
Important distinctions
| Result | Different boundary |
|---|---|
SL_E_NOT_GENUINE | Relative to this result: the Software Protection Platform’s genuine-state evaluation does not accept the current Windows licensing state. |
SL_E_NONGENUINE_GRACE_TIME_EXPIRED_2 | Relative to this result: the second non-genuine grace category has expired. |
SL_E_NONGENUINE_GRACE_TIME_EXPIRED | Relative to it: the first non-genuine remediation grace period has ended without restoring a genuine license state. |
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.
Recovery without damaging licensing evidence
Use the narrow remediation: renew, replace, or remove the expired time-based license according to the authorized program. Avoid simultaneous key changes, store resets, service restarts, and network changes because they make it impossible to identify which precondition mattered.
Representative failure: A time-limited Windows entitlement reaches its stated end date.
Verification after the change
Build a regression case that intentionally creates “the configured time-based license validity period has ended” 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.
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 it 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.
Technical references
- SoftwareLicensingProduct WMI class — Microsoft guidance for the activation mechanism represented by it.
- WMI properties for volume activation — platform behavior relevant to it.
- Slmgr.vbs activation options — diagnostic and operational context for it.
- Microsoft activation error-code troubleshooting — supported tools and state fields used to verify it.
Looking for a different code? Search another status or error code.