HRESULT 0xC004F023 is exposed as SL_E_LICENSE_DECRYPTION_FAILED by the local Software Protection Platform. The code says more than the friendly message: the service found the license but could not decrypt its protected payload.
Windows reports “The Software Licensing Service reported that the license is invalid”.
From input to HRESULT
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
Record the exact licensing operation that returned this HRESULT.
Commit or status
Do not infer the intended licensing state from outputs produced by the failed operation.
What the constant itself tells you
Signal
Interpretation
Family
The code comes from Software Protection Platform; correlate it with one product object rather than the computer as a whole.
Object
The license object or one of its dependencies is the primary subject.
Operation
The operation did not complete or commit its intended licensing state.
State
Use the exact HRESULT and first failing operation before attempting a broad activation reset.
Evidence to keep before remediation
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?
license/package identity, version, digest and dependency
Which signed package or dependency was evaluated, and does its version or digest match the expected product state?
caller identity and elevation
Which account and token performed the operation, and was the required elevation present?
Code-specific distinction
Does the evidence support “preserve package and security-processor versions and restore matching signed components” rather than absence of decryption licenses or failure of the outer signature?
Work from identity to cause
Record 0xC004F023, UTC time, caller and the first method or server request that returned it.
Capture Application ID, Activation ID and product name.
Before remediation, confirm that the failure is not instead the neighboring condition: absence of decryption licenses or failure of the outer signature.
license evaluation completed but the license does not authorize the requested operation
SL_E_WINDOWS_INVALID_LICENSE_STATE
Windows product licensing state is inconsistent with the operation being requested
SL_E_LUA_ACCESSDENIED
the operation requires an elevated administrator token and the caller is not authorized
A focused reproduction for this exact result
Control
Design
Failing fixture
A protected license is moved to an incompatible environment.
Single variable
Change only the narrow input or state named by the HRESULT while product identity remains fixed.
Positive control
A known-good value for that condition succeeds and the failing fixture still reproduces the code.
Different result
If the experiment instead proves “license evaluation completed but the license does not authorize the requested operation”, diagnose that condition separately rather than treating it as this HRESULT.
What successful remediation must prove
A supported correction is to preserve package and security-processor versions and restore matching signed components.
Changes that make this code harder to diagnose
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.
Avoid copying license packages or protected stores from another computer.
