| Previous | Next |
| SL_E_EVALUATION_FAILED | SL_E_NOT_ACTIVATED |
SL_E_NOT_EVALUATED
How to read this result without losing context
The useful meaning of SL_E_NOT_EVALUATED, value 0xC004E004, is not simply “activation failed.” It comes from the logical license and token repository, where the repository layer that initializes licensing context, locates token records, parses properties, serializes files and synchronizes concurrent access. The condition to investigate is the requested license state has not yet been evaluated for this context or generation.
For triage, this belongs to the logical license and token repository. Absence of evaluation is not equivalent to an evaluated unlicensed result. Product-key changes or network tests are useful only when the evidence points back to those layers.
Where it sits in the licensing pipeline
The logical token repository sits below product activation: a missing, unreadable or inconsistent token can prevent evaluation before any server request occurs. To verify this, record product ID, service startup/refresh state, pending operation and whether RefreshLicenseStatus completed.
Store initialization, property parsing, file I/O and synchronization failures require different repairs even when the activation UI shows the same unlicensed state.
Inputs that distinguish this condition
- store initialization and mutex state
- file path, access result and Security-SPP event
- target Application ID and Activation ID
- token or license identifier
- property name, type and serialized value
Checks in the useful order
- Use read-only inspection first: record product ID, service startup/refresh state, pending operation and whether RefreshLicenseStatus completed.
Similar symptoms, different conditions
| Result | Different condition |
|---|---|
SL_E_EVALUATION_FAILED | Compared with this result, the rules engine attempted license evaluation but could not produce a valid result. |
SL_E_INVALID_GUID | Compared with this result, a licensing identifier expected to be a GUID is malformed, empty or semantically invalid. |
SL_E_TOKEN_STORE_INVALID_STATE | Compared with it, the logical license repository contains mutually inconsistent state that prevents reliable evaluation. |
Correcting the producing condition
Allow or trigger supported evaluation and then read the resulting state from the same Activation ID.
Representative case: A management tool queries immediately after installing a license package before status refresh finishes.
Actions that usually destroy useful evidence
- Do not repeatedly installing keys while repository operations are failing.
- Do not rename or replacing store files without preserving the original and following the supported rebuild sequence.
Technical references
- Rebuild the Tokens.dat file — official platform context used to interpret it.
- Software Licensing provider — supported state, API or recovery information relevant to this HRESULT.
- SoftwareLicensingService WMI class — reference for evidence collection and post-repair verification.
- SoftwareLicensingProduct WMI class — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.