| Previous | Next |
| SL_E_INVALID_RUNNING_MODE | SL_E_CIDIID_INVALID_DATA |
SL_E_SLP_NOT_SIGNED
The stage that stopped
SL_E_SLP_NOT_SIGNED is HRESULT 0xC004F02A. It belongs to the local Software Protection Platform. Its narrow boundary is: the license or SLP artifact is expected to be signed but no acceptable signature is present.
A local licensing operation can fail while loading a package, verifying a signature, resolving policy, authorizing a right, registering an event or changing service state. Each boundary is narrower than the final activation status shown in Settings. The code is not interchangeable with a signed artifact whose signature verification fails.
AllStat records “The Software Licensing Service reported that the license is invalid”. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
Why the producing layer matters
| Stage | Role |
|---|---|
| Product instance | Application ID and Activation ID identify the exact licensed object. |
| License inputs | Packages, dependencies, signatures and policies feeding this result are loaded for that object. |
| Requested transition | The right, property, event, plug-in or service operation that returns this result is evaluated. |
| Commit or status | The intended state cannot be trusted or committed while this result remains unresolved. |
A later unlicensed, notification or grace-state message describes a consequence. Preserve the earliest event carrying this HRESULT for the same product object or service request.
What the constant itself tells you
- The result is local to Software Protection Platform and should be tied to one product object, not the computer in general.
- The suffix names the object or transition to inspect before any broad activation reset.
- Its HRESULT severity is failure; later status messages can describe only the resulting state.
- The exact first caller and object identity are needed to distinguish a producer error from cleanup noise.
Evidence that avoids a false diagnosis
| Evidence | Question answered |
|---|---|
| Application ID, Activation ID and product name | Which Application ID and Activation ID returned the code? |
| LicenseStatus, LicenseStatusReason and grace values | Was the failure during package load, policy evaluation, authorization or service maintenance? |
| first API/slmgr method and earliest Security-SPP event | Is the named object absent, invalid, mismatched, duplicated or in the wrong lifecycle state? |
| signer, signature result, file hashes and servicing history | Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | Does the evidence support “replace it with the OEM/Microsoft-signed artifact through supported servicing” rather than a signed artifact whose signature verification fails? |
Redact full keys, activation blobs, account tokens, private certificate material and raw hardware identifiers. Partial keys, hashes, IDs and UTC timestamps retain correlation value without publishing secrets.
Diagnostic sequence
- Record
0xC004F02A, UTC time, caller and the first method or server request that returned it. - Capture first API/slmgr method and earliest Security-SPP event.
- Prove the distinction between the named boundary and a signed artifact whose signature verification fails before remediation.
- After one supported change, repeat the same operation and compare state, events and response correlation.
- Bind this result to the exact Application ID, Activation ID, edition and partial key.
REM Evidence context: SL_E_SLP_NOT_SIGNED
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Use the status output as evidence. Run an activation retry only after the collected state supports the identified prerequisite; blind retries can add quota, throttle or cleanup noise.
Important distinctions
| Result | Different condition |
|---|---|
SL_E_INVALID_RUNNING_MODE | the Software Protection service is being started or used in an OS mode that does not support this operation |
SL_E_POLICY_CACHE_INVALID | the compiled or cached licensing policy cannot be trusted or parsed |
SL_E_TAMPER_DETECTED | the local licensing platform detects modification of protected license state or components |
Sort related HRESULTs by timestamp and object/request identity. The first code from the producing layer is usually more actionable than a later summary from Settings, deployment software or a wrapper.
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | An unsigned custom license is introduced into an SLP workflow. |
| 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 Software Protection service is being started or used in an OS mode that does not support this operation”, follow that neighboring boundary rather than treating it as it. |
Fix the prerequisite, then verify
A supported correction is to replace it with the OEM/Microsoft-signed artifact through supported servicing.
Verification must repeat the original operation for the same product or request scope. Confirm the intended license status, binding, policy, record or server response persists after any required restart.
Changes that make this code harder to diagnose
- Avoid copying license packages or protected stores from another computer.
- Avoid force-deleting policy, plug-in or license files while sppsvc owns them.
- Avoid using rearm or key replacement as a universal package/policy repair.
Technical references
- Slmgr.vbs options — official reference for the mechanism surrounding it.
- Troubleshoot Windows activation error codes
- MS-ERREF Windows Error Codes
- SoftwareLicensingProduct WMI class
Looking for a different code? Search another status or error code.