| Previous | Next |
| SL_E_AUTHN_MISMATCHED_KEY | SL_E_AUTHN_CANT_VERIFY |
SL_E_AUTHN_CHALLENGE_NOT_SET
Where this result is produced
SL_E_AUTHN_CHALLENGE_NOT_SET is HRESULT 0xC004F079. It belongs to the local Software Protection Platform. Its narrow boundary is: the caller attempts verification before establishing the required authentication challenge.
Windows reports “The Software Licensing Service reported that the authentication data is not set”.
Minimum diagnostic record
| 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 “restart the sequence and persist the challenge/response correlation” rather than a challenge that exists but cannot be verified? |
How to reproduce the same condition
- Record
0xC004F079, UTC time, caller and the first method or server request that returned it. - Capture first API/slmgr method and earliest Security-SPP event.
- Before remediation, confirm that the failure is not instead the neighboring condition: a challenge that exists but cannot be verified.
REM Evidence context: SL_E_AUTHN_CHALLENGE_NOT_SET
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Do not merge these conditions
| Result | Different condition |
|---|---|
SL_E_AUTHN_MISMATCHED_KEY | the authentication response or data is bound to a different key than the verifier expects |
SL_E_AUTHN_CANT_VERIFY | authentication data is present but the licensing service cannot complete verification |
SL_E_AUTHN_WRONG_VERSION | authentication data uses a version incompatible with the local licensing verifier |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | An asynchronous workflow loses the challenge state before response processing. |
| 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 “the authentication response or data is bound to a different key than the verifier expects”, diagnose that condition separately rather than treating it as this HRESULT. |
Recovery without broad resets
To correct this using supported mechanisms, restart the sequence and persist the challenge/response correlation.
Technical references
Looking for a different code? Search another status or error code.