| 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.
AllStat records “The Software Licensing Service reported that the required data is not found”. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
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 | 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
| Signal | Interpretation |
|---|---|
| Family | The result is local to Software Protection Platform and should be tied to one product object, not the computer in general. |
| Object | A lookup completed without locating the named object. |
| Operation | The suffix names the object or transition to inspect before any 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 boundary
- 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.
- Record
0xC004F026, UTC time, caller and the first method or server request that returned it. - Capture Application ID, Activation ID and product name.
- Prove the distinction between the named boundary and a network proxy host that cannot be found by DNS before remediation.
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”, follow that neighboring boundary rather than treating it as it. |
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.
Technical references
- SoftwareLicensingProduct WMI class — official reference for the mechanism surrounding it.
- SoftwareLicensingService WMI class
- WMI properties and methods for volume activation
- Slmgr.vbs options
Looking for a different code? Search another status or error code.