| Previous | Next |
| SL_E_AUTHN_WRONG_VERSION | SL_E_AUTHN_CHALLENGE_NOT_SET |
SL_E_AUTHN_MISMATCHED_KEY
The stage that stopped
SL_E_AUTHN_MISMATCHED_KEY is HRESULT 0xC004F078. It belongs to the local Software Protection Platform. Its narrow boundary is: the authentication response or data is bound to a different key than the verifier expects.
Windows reports “The Software Licensing Service reported that the key is mismatched”.
Evidence that avoids a false diagnosis
| challenge correlation, key ID, data version and verifier | Can caller identity and elevation be captured before changing state? |
| Code-specific distinction | Does the evidence support “correlate key ID, challenge and product instance and restart the authentication exchange” rather than a challenge that was never initialized? |
Diagnostic sequence
- Before remediation, confirm that the failure is not instead the neighboring condition: a challenge that was never initialized.
- Record
0xC004F078, UTC time, caller and the first method or server request that returned it. - Capture caller identity and elevation.
REM Evidence context: SL_E_AUTHN_MISMATCHED_KEY
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Important distinctions
| Result | Different condition |
|---|---|
SL_E_AUTHN_WRONG_VERSION | authentication data uses a version incompatible with the local licensing verifier |
SL_E_AUTHN_CHALLENGE_NOT_SET | the caller attempts verification before establishing the required authentication challenge |
SL_E_PLUGIN_NOT_REGISTERED | the requested Software Protection plug-in is not registered for discovery |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A response from one activation session is applied to another. |
| Single variable | Change only challenge, authentication-data version and key correlation. |
| Positive control | A fresh response generated for the same challenge and expected key verifies. |
| Different result | If the experiment instead proves “authentication data uses a version incompatible with the local licensing verifier”, diagnose that condition separately rather than treating it as this HRESULT. |
Fix the prerequisite, then verify
To correct this using supported mechanisms, correlate key ID, challenge and product instance and restart the authentication exchange.
Technical references
Looking for a different code? Search another status or error code.