| Previous | Next |
| SL_E_SFS_DUPLICATE_TOKEN_NAME | SL_E_SFS_INVALID_TOKEN_DATA_HASH |
SL_E_SFS_TOKEN_SIZE_MISMATCH
Why this is more specific than an activation failure
Keep the symbolic result SL_E_SFS_TOKEN_SIZE_MISMATCH together with HRESULT 0x8004E107. The producer is the serialized Token Store file format; at the low-level reader/writer that validates the Token Store container, descriptor table, token records and transaction state before licenses can be evaluated, Windows determined that the token’s declared length disagrees with the bytes available in its serialized extent.
This result already rules out several broad guesses: a size mismatch can be detected before hashing and does not by itself prove malicious modification. Preserve its operation name, product instance and timestamp so a later retry does not hide this boundary.
From HRESULT to a verified cause
- Start with the earliest event carrying this result; later status queries may only report the resulting unlicensed or notification state.
- tie the event to one Application ID/Activation ID, handle, namespace, token or crypto object rather than to the computer in general.
- use read-only inspection first: compare declared size, descriptor extent, file length and any interrupted-write or disk-error event.
- check whether the issue reproduces after normal service restart without altering signed store or policy data.
- After a supported repair for this HRESULT, query the same object and confirm that the original boundary no longer fails.
State to compare on both sides of the failure
| Item | Why it matters here |
|---|---|
| file-system result and Software Protection event | Reveals whether servicing, migration, restore, cloning or concurrent work changed the precondition. |
| Tokens.dat or the applicable licensing-store file | Identifies the protected object or product instance that returned the code. |
| store header and format version | Separates format/version failure from damage, absence or access failure. |
| descriptor table and token offsets | Shows the state transition immediately before the HRESULT. |
| token name, extension, declared size and hash | Correlates service-level evidence with storage, crypto or policy evidence. |
Code-specific check: compare declared size, descriptor extent, file length and any interrupted-write or disk-error event.
Where it sits in the licensing pipeline
A structural Token Store error occurs before an individual product key can be accepted or rejected. The decisive proof for this HRESULT is to compare declared size, descriptor extent, file length and any interrupted-write or disk-error event.
The documented Tokens.dat rebuild procedure is a recovery action, not the first evidence-gathering step; preserve the original error and licensing inventory first. Keep that product/object identity because the same service can expose several independent licensing instances.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_E_SFS_DUPLICATE_TOKEN_NAME | Compared with this result, two descriptor entries resolve to the same token name where the store requires uniqueness. |
SL_E_SFS_INVALID_TOKEN_DATA_HASH | Compared with this result, the protected token payload no longer matches the integrity hash recorded for this HRESULT. |
SL_E_SFS_BAD_TOKEN_EXT | Compared with it, a token record carries an unsupported or malformed extension/type suffix. |
A narrow remediation path
Correct storage corruption and regenerate the store; do not pad or truncate the record manually. Preserve the original store, event export, hashes and licensing inventory until the operation succeeds and the expected state survives any required restart.
Representative case: Power loss occurs after the descriptor length is committed but before all token bytes reach disk.
Actions that usually destroy useful evidence
- do not assuming a product-key change can repair a malformed container.
- do not editing or copying individual records inside the signed store.
- While resolving it, do not use unofficial activation tools, patched binaries, copied stores, disabled integrity checks or hand-edited signed data; they can create a second tamper condition.
Verification after correction
Repeat the operation that originally produced it, not merely a UI refresh. Confirm the exact product/object completes, review LicenseStatus and LicenseStatusReason when applicable, and check that no related boundary replaces it.
Regression testing, retain one failing fixture that reproduces “the token’s declared length disagrees with the bytes available in its serialized extent” and one passing fixture that changes only the decisive precondition; this avoids mistaking a broad reset for verification.
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 it.
- Slmgr.vbs options — reference for this HRESULT evidence collection and post-repair verification.
Looking for a different code? Search another status or error code.