| Previous | Next |
| SL_E_AUTHN_CHALLENGE_NOT_SET | SL_E_SERVICE_RUNNING |
SL_E_AUTHN_CANT_VERIFY
How to interpret this HRESULT
When SL_E_AUTHN_CANT_VERIFY returns 0xC004F07A, diagnosis has reached the local Software Protection Platform. Specifically, authentication data is present but the licensing service cannot complete verification.
Windows reports “The Software Licensing Service reported that the verification could not be done”.
What to collect first
| 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 “capture algorithm/provider, certificate/key identifiers and the first verifier event” rather than wrong version, mismatched key or missing challenge with a narrower reason? |
Checks in a useful order
- Record
0xC004F07A, UTC time, caller and the first method or server request that returned it. - Capture LicenseStatus, LicenseStatusReason and grace values.
- Before remediation, confirm that the failure is not instead the neighboring condition: wrong version, mismatched key or missing challenge with a narrower reason.
REM Evidence context: SL_E_AUTHN_CANT_VERIFY
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Keep neighboring codes separate
| Result | Different condition |
|---|---|
SL_E_AUTHN_CHALLENGE_NOT_SET | the caller attempts verification before establishing the required authentication challenge |
SL_E_SERVICE_RUNNING | the requested maintenance operation requires the Software Protection service not to be running |
SL_E_AUTHN_MISMATCHED_KEY | the authentication response or data is bound to a different key than the verifier expects |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | Cryptographic provider or protected-state failure prevents verification. |
| 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 caller attempts verification before establishing the required authentication challenge”, diagnose that condition separately rather than treating it as this HRESULT. |
Safe recovery direction
To correct this using supported mechanisms, capture algorithm/provider, certificate/key identifiers and the first verifier event.
Technical references
Looking for a different code? Search another status or error code.