| Previous | Next |
| SL_E_CHPA_TIMEBASED_ACTIVATION_BEFORE_START_DATE | SL_E_CHPA_TIMEBASED_ACTIVATION_NOT_AVAILABLE |
SL_E_CHPA_TIMEBASED_ACTIVATION_AFTER_END_DATE
Within Windows activation-service policy and product-key processing SL_E_CHPA_TIMEBASED_ACTIVATION_AFTER_END_DATE (0xC004C031) reports that the CHPA transaction was submitted after the authorized activation window ended. Treat it as the CHPA activation time-based activation after end date condition and start with Application ID, Activation ID and partial key, not with the final dialog text.
Why this HRESULT is specific
The server compared the request time with a time-bounded entitlement and found the end boundary had passed.
The decisive question is whether the recorded evidence supports the reported condition that the CHPA transaction was submitted after the authorized activation window ended. Keep evidence tied to the failing operation.
How to distinguish nearby failures
The key comparison is this: This is a policy-window decision, not a local grace-period or Store app-license expiration. A valid CHPA activation time-based activation after end date test keeps Application ID, Activation ID and partial key attached to the same object and varies one supported prerequisite.
Evidence that can change the diagnosis
- Primary record: Application ID, Activation ID and partial key.
- Object correlation: keep the product, account, package, device, key, or API identity associated with Application ID, Activation ID and partial key beside the first timestamped result.
- Neighboring-state control: use a controlled comparison that tests whether this is a policy-window decision, not a local grace-period or Store app-license expiration; this separates the named condition from a nearby status.
- Before/after result: retain the outcome before and after the corrective action “change only the prerequisite named by the HRESULT”; keep the same identifiers until the same CHPA transaction reaches its intended policy or commit stage and the resulting license state persists.
Controlled troubleshooting sequence
- Locate the exact object: Use the primary record to identify the transaction or licensed object that actually returned this result.
- Preserve the first decision: Record the earliest event stating that the CHPA transaction was submitted after the authorized activation window ended, together with the code, UTC time, and the same identity fields.
- Change one prerequisite: Change only the prerequisite named by the HRESULT; do not combine this with a store reset, key replacement, account removal, package reinstall, or unrelated repair.
- Repeat the user operation: Re-run the original operation and require that the same CHPA transaction reaches its intended policy or commit stage and the resulting license state persists; if another HRESULT appears, diagnose it as a new boundary.
Evidence-preserving cautions
While investigating this result, do not delete the licensing store or replace the key before preserving the original transaction evidence. That shortcut can replace or invalidate that evidence before the original decision is understood.
Verification
The incident is resolved only when the same CHPA transaction reaches its intended policy or commit stage and the resulting license state persists. Confirm the result by repeating the exact operation that produced this result; maintenance success alone is insufficient.
Technical references
- Microsoft Win32 metadata: winerror.h — status definition reference.
- Microsoft: SoftwareLicensingProduct WMI class — owning service/API reference.
- Microsoft: Troubleshoot Windows activation error codes — diagnostic/remediation API reference.
- Microsoft: Plan for volume activation — lifecycle reference.
Looking for a different code? Search another status or error code.