| Previous | Next |
| SL_E_TOKSTO_INVALID_FILE | SL_E_TOKSTO_CANT_ACQUIRE_MUTEX |
SL_E_TOKSTO_CANT_CREATE_MUTEX
How to read this result without losing context
Keep the symbolic result SL_E_TOKSTO_CANT_CREATE_MUTEX together with HRESULT 0xC004E012. 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 the repository cannot create its synchronization object.
For triage, this belongs to the logical license and token repository. No synchronization object exists; CANT_ACQUIRE_MUTEX means one exists but cannot be obtained. 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 mutex name/namespace, caller context, underlying system error and service-instance state.
Store initialization, property parsing, file I/O and synchronization failures require different repairs even when the activation UI shows the same unlicensed state.
Checks in the useful order
- Identify the caller and operation instance that produced
0xC004E012. - Collect the code-specific evidence: record mutex name/namespace, caller context, underlying system error and service-instance state.
Minimum data for a reliable diagnosis
- target Application ID and Activation ID
- token or license identifier
- property name, type and serialized value
- store initialization and mutex state
- file path, access result and Security-SPP event
Why the symbolic code matters
| Result | Different condition |
|---|---|
SL_E_TOKSTO_CANT_ACQUIRE_MUTEX | Compared with this result, the repository’s synchronization object exists but cannot be acquired for the operation. |
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_NO_TOKEN_DATA | Compared with this result, a token object lacks the serialized data required for evaluation or persistence. |
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.
Recommended handling
Repair service/security context or resource exhaustion and start with one clean service instance.
Representative case: A damaged service environment prevents creation of the named repository mutex.
Technical references
- Rebuild the Tokens.dat file — reference for evidence collection and post-repair verification.
- Software Licensing provider — technical contract for the subsystem producing it.
- SoftwareLicensingService WMI class — official platform context used to interpret it.
- SoftwareLicensingProduct WMI class — supported state, API or recovery information relevant to this HRESULT.
Looking for a different code? Search another status or error code.