| Previous | Next |
| SL_E_CHPA_TIMEBASED_ACTIVATION_NOT_AVAILABLE | SL_E_CHPA_NO_RULES_TO_ACTIVATE |
SL_E_CHPA_TIMEBASED_PRODUCT_KEY_NOT_CONFIGURED
SL_E_CHPA_TIMEBASED_PRODUCT_KEY_NOT_CONFIGURED is HRESULT 0xC004C033 from Windows activation-service policy and product-key processing. It means that the submitted key is not configured. The practical shorthand CHPA activation time-based product key not configured is useful because it points to Application ID, Activation ID and partial key as the first evidence to preserve.
How to distinguish nearby failures
Nearby condition: This is a program configuration mismatch rather than a blocked key. Hold the recorded identifiers and values constant while changing only the prerequisite described.
Why this HRESULT is specific
The key can be identifiable while lacking the server-side association required by the requested program.
The decisive question is whether the primary record supports the reported condition that the submitted key is not configured. Keep evidence tied to the failing operation.
Evidence that can change the diagnosis
| Record | Why it matters |
|---|---|
| Primary record | Application ID, Activation ID and partial key; this is the shortest evidence path to the decision. |
| Object correlation | Keep the product, account, package, device, key, or API identity associated with the recorded identifiers and values beside the first timestamped result. |
| Neighboring-state control | Use a controlled comparison that tests whether this is a program configuration mismatch rather than a blocked key; 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 submitted key is not configured, 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: Activate method — diagnostic/remediation API reference.
- Microsoft: Troubleshoot Windows activation error codes — lifecycle reference.
Looking for a different code? Search another status or error code.