What does HRESULT 0xC004F072 (SL_E_APPLICATION_POLICIES_MISSING) mean?

 
Previous Next
SL_E_PLUGIN_INVALID_MANIFEST SL_E_APPLICATION_POLICIES_NOT_LOADED

SL_E_APPLICATION_POLICIES_MISSING

How to interpret this HRESULT

When SL_E_APPLICATION_POLICIES_MISSING returns 0xC004F072, diagnosis has reached the local Software Protection Platform. Specifically, fast-query application policies cannot be found for the selected licensing application.

Windows reports “The Software Licensing Service reported that the license policies for fast query could not be found”.

What to collect first

whether a clean reboot reproduces the result without modifying stateDoes the evidence support “identify the Application ID and restore or regenerate its official policy data” rather than policies that exist but have not yet been loaded?

Checks in a useful order

  1. Record 0xC004F072, UTC time, caller and the first method or server request that returned it.
  2. Capture Application ID, Activation ID and product name.
  3. Before remediation, confirm that the failure is not instead the neighboring condition: policies that exist but have not yet been loaded.
REM Evidence context: SL_E_APPLICATION_POLICIES_MISSING
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"

Keep neighboring codes separate

ResultDifferent condition
SL_E_PLUGIN_INVALID_MANIFESTa Software Protection plug-in manifest cannot be parsed, verified or matched to the expected component
SL_E_APPLICATION_POLICIES_NOT_LOADEDapplication policies exist but are not loaded into the fast-query evaluation path
SL_E_SERVICE_STOPPINGthe Software Protection service is in shutdown and cannot begin or finish this operation

A focused reproduction for this exact result

ControlDesign
Failing fixtureA package cleanup removes the fast-query policy set.
Single variableChange only presence of the exact required object in the correct product and storage scope.
Positive controlRestoring only that official dependency removes the code without a broad store reset.
Different resultIf the experiment instead proves “a Software Protection plug-in manifest cannot be parsed, verified or matched to the expected component”, diagnose that condition separately rather than treating it as this HRESULT.

Safe recovery direction

To correct this using supported mechanisms, identify the Application ID and restore or regenerate its official policy data.

Technical references


Looking for a different code? Search another status or error code.