| Previous | Next |
| SL_E_TOKSTO_CANT_PARSE_PROPERTIES | SL_E_TOKSTO_INVALID_FILE |
SL_E_TOKSTO_PROPERTY_NOT_FOUND
How to read this result without losing context
Keep the symbolic result SL_E_TOKSTO_PROPERTY_NOT_FOUND together with HRESULT 0xC004E010. The producer is the logical license and token repository; at the repository layer that initializes licensing context, locates token records, parses properties, serializes files and synchronizes concurrent access, Windows determined that a requested property is absent from an otherwise accessible token.
For triage, this belongs to the logical license and token repository. The property collection exists and parses; one field is missing. Product-key changes or network tests are useful only when the evidence points back to those layers.
Inputs that distinguish this condition
- file path, access result and Security-SPP event
- target Application ID and Activation ID
- token or license identifier
- property name, type and serialized value
- store initialization and mutex state
A practical way to isolate the cause
- Identify the caller and operation instance that produced
0xC004E010. - Collect the code-specific evidence: record token ID, property name/type, package schema version and dependency expecting it.
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 token ID, property name/type, package schema version and dependency expecting it.
Store initialization, property parsing, file I/O and synchronization failures require different repairs even when the activation UI shows the same unlicensed state.
Why the symbolic code matters
| Result | Different condition |
|---|---|
SL_E_TOKSTO_CANT_PARSE_PROPERTIES | Compared with this result, the repository reads the token but cannot decode its property collection. |
SL_E_TOKSTO_INVALID_FILE | Compared with this result, a license-store file is readable but fails identity, structure or integrity validation. |
SL_E_TOKSTO_CANT_CREATE_MUTEX | Compared with this result, the repository cannot create its synchronization object. |
Correcting the producing condition
Use a compatible package containing the required property or handle it as optional only when documented.
Representative case: A newer evaluator expects a policy property absent from an older license package.
Actions that usually destroy useful evidence
- Do not rename or replacing store files without preserving the original and following the supported rebuild sequence.
- Do not repeatedly installing keys while repository operations are failing.
Technical references
- Rebuild the Tokens.dat file — technical contract for the subsystem producing it.
- Software Licensing provider — official platform context used to interpret it.
- SoftwareLicensingService WMI class — supported state, API or recovery information relevant to this HRESULT.
- SoftwareLicensingProduct WMI class — reference for evidence collection and post-repair verification.
Looking for a different code? Search another status or error code.