| Previous | Next |
| SL_E_LICENSE_SIGNATURE_VERIFICATION_FAILED | SL_E_INVALID_LICENSE |
SL_E_DATATYPE_MISMATCHED
What the constant narrows down
HRESULT 0xC004F01E is exposed as SL_E_DATATYPE_MISMATCHED by the local Software Protection Platform. The code says more than the friendly message: the caller supplies a value whose type differs from the type declared by the license property.
Windows reports “The Software Licensing Service determined that the input data type does not match the data type in the license”.
Evidence to keep before remediation
| property key, expected type and supplied type | Can caller identity and elevation be captured before changing state? |
| Code-specific distinction | Does the evidence support “record property name, expected type and supplied type and correct the API caller” rather than a correctly typed property that is missing or read-only? |
Work from identity to cause
- Record
0xC004F01E, 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 correctly typed property that is missing or read-only.
REM Evidence context: SL_E_DATATYPE_MISMATCHED
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Similar messages, different conditions
| Result | Different condition |
|---|---|
SL_E_LICENSE_SIGNATURE_VERIFICATION_FAILED | the cryptographic signature on a license or associated artifact does not verify |
SL_E_INVALID_LICENSE | the selected license object fails general structural or semantic validation |
SL_E_DECRYPTION_LICENSES_NOT_AVAILABLE | the licenses required to decrypt or interpret protected licensing data are absent |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | Automation sends text where the license schema requires an integer or binary value. |
| Single variable | Change only property identity, declared type and supplied value. |
| Positive control | A schema-defined property accepts a value of the declared type. |
| Different result | If the experiment instead proves “the cryptographic signature on a license or associated artifact does not verify”, diagnose that condition separately rather than treating it as this HRESULT. |
What successful remediation must prove
To correct this using supported mechanisms, record property name, expected type and supplied type and correct the API caller.
Technical references
- Troubleshoot Windows activation error codes.
- MS-ERREF Windows Error Codes
- SoftwareLicensingProduct WMI class
- SoftwareLicensingService WMI class
Looking for a different code? Search another status or error code.