| Previous | Next |
| SL_E_DECRYPTION_LICENSES_NOT_AVAILABLE | SL_E_DATATYPE_MISMATCHED |
SL_E_LICENSE_SIGNATURE_VERIFICATION_FAILED
How to interpret this HRESULT
When SL_E_LICENSE_SIGNATURE_VERIFICATION_FAILED returns 0xC004F01D, diagnosis has reached the local Software Protection Platform. Specifically, the cryptographic signature on a license or associated artifact does not verify.
Windows reports “The Software Licensing Service reported that the verification of the license failed”.
What to collect first
| license/package identity, version, digest and dependency | Can signer, signature result, file hashes and servicing history be captured before changing state? |
| signer, signature result, file hashes and servicing history | Does the evidence support “preserve hashes and signer information and reinstall through trusted servicing” rather than an external signature file that is missing entirely? |
Checks in a useful order
- Capture license/package identity, version, digest and dependency.
- Before remediation, confirm that the failure is not instead the neighboring condition: an external signature file that is missing entirely.
- Record
0xC004F01D, UTC time, caller and the first method or server request that returned it.
REM Evidence context: SL_E_LICENSE_SIGNATURE_VERIFICATION_FAILED
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_DECRYPTION_LICENSES_NOT_AVAILABLE | the licenses required to decrypt or interpret protected licensing data are absent |
SL_E_DATATYPE_MISMATCHED | the caller supplies a value whose type differs from the type declared by the license property |
SL_E_EVENT_ALREADY_REGISTERED | the event ID is already registered in the relevant licensing context |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A license file is modified or paired with the wrong signature. |
| Single variable | Change only original signed artifact and its matching signature chain. |
| Positive control | The unmodified Microsoft/OEM-signed artifact verifies on the same serviced build. |
| Different result | If the experiment instead proves “the licenses required to decrypt or interpret protected licensing data are absent”, diagnose that condition separately rather than treating it as this HRESULT. |
Safe recovery direction
To correct this using supported mechanisms, preserve hashes and signer information and reinstall through trusted servicing.
Technical references
- WMI properties and methods for volume activation.
- Slmgr.vbs options
- Troubleshoot Windows activation error codes
- MS-ERREF Windows Error Codes
Looking for a different code? Search another status or error code.