| Previous | Next |
| SL_E_LUA_ACCESSDENIED | SL_E_TAMPER_DETECTED |
SL_E_PROXY_KEY_NOT_FOUND
Where this result is produced
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”.
Minimum diagnostic record
| 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.
REM Evidence context: SL_E_PROXY_KEY_NOT_FOUND
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Do not merge these conditions
| Result | Different condition |
|---|---|
SL_E_LUA_ACCESSDENIED | 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
To correct this using supported mechanisms, record the proxy-policy key and product context and repair policy through its supported source.
Technical references
Looking for a different code? Search another status or error code.