SL_E_PROXY_KEY_NOT_FOUND is HRESULT 0xC004F026. It belongs to the local Software Protection Platform. Its narrow boundary is: a required proxy or indirection key cannot be resolved in local licensing policy data.
Result-specific evidence: The documented meaning is “The Software Licensing Service reported that the required data is not found.” Verification should prove or disprove that exact condition before broader remediation.
Windows reports “The Software Licensing Service reported that the required data is not found”.
Objects and state transitions
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
A lookup completed without locating the named object.
Operation
Use the exact HRESULT and first failing operation before attempting a broad activation reset.
State
Its HRESULT severity is failure; later status messages can describe only the resulting state.
Minimum diagnostic record
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?
caller identity and elevation
Can whether a clean reboot reproduces the result without modifying state be captured before changing state?
whether a clean reboot reproduces the result without modifying state
Does the evidence support “record the proxy-policy key and product context and repair policy through its supported source” rather than a network proxy host that cannot be found by DNS?
How to reproduce the same condition
Record 0xC004F026, 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: a network proxy host that cannot be found by DNS.
the operation requires an elevated administrator token and the caller is not authorized
SL_E_TAMPER_DETECTED
the local licensing platform detects modification of protected license state or components
SL_E_WINDOWS_INVALID_LICENSE_STATE
Windows product licensing state is inconsistent with the operation being requested
A focused reproduction for this exact result
Control
Design
Failing fixture
A generated policy references an absent backing value.
Single variable
Change only presence of the exact required object in the correct product and storage scope.
Positive control
Restoring only that official dependency removes the code without a broad store reset.
Different result
If the experiment instead proves “the operation requires an elevated administrator token and the caller is not authorized”, diagnose that condition separately rather than treating it as this HRESULT.
Recovery without broad resets
A supported correction is to record the proxy-policy key and product context and repair policy through its supported source.
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.