| 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. The decisive condition is: fast-query application policies cannot be found for the selected licensing application.
AllStat records “The Software Licensing Service reported that the license policies for fast query could not be found” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
Relevant processing model
| Stage | Role for this HRESULT |
|---|---|
| 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 | The suffix names the object or transition to inspect before any broad activation reset. |
| Operation | Its HRESULT severity is failure; later status messages can describe only the resulting state. |
| State | The exact first caller and object identity are needed to distinguish a producer error from cleanup noise. |
What to collect first
| Evidence | Question answered |
|---|---|
| Application ID, Activation ID and product name | For this HRESULT: Which Application ID and Activation ID returned the code? |
| LicenseStatus, LicenseStatusReason and grace values | For this HRESULT: Was the failure during package load, policy evaluation, authorization or service maintenance? |
| first API/slmgr method and earliest Security-SPP event | For this HRESULT: Is the named object absent, invalid, mismatched, duplicated or in the wrong lifecycle state? |
| caller identity and elevation | For this HRESULT: 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 | For this HRESULT: Does 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
- After one supported change, repeat the same operation and compare state, events and response correlation for this HRESULT.
- Bind this result to the exact Application ID, Activation ID, edition and partial key.
- Record
0xC004F072, UTC time, caller and the first method or server request that returned it. - Capture Application ID, Activation ID and product name specifically for this HRESULT.
- Prove the distinction between the named boundary and policies that exist but have not yet been loaded before remediation.
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
| Result | Different condition |
|---|---|
SL_E_PLUGIN_INVALID_MANIFEST | a Software Protection plug-in manifest cannot be parsed, verified or matched to the expected component |
SL_E_APPLICATION_POLICIES_NOT_LOADED | application policies exist but are not loaded into the fast-query evaluation path |
SL_E_SERVICE_STOPPING | the Software Protection service is in shutdown and cannot begin or finish this operation |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A package cleanup removes the fast-query policy set. |
| 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 “a Software Protection plug-in manifest cannot be parsed, verified or matched to the expected component”, follow that neighboring boundary rather than treating it as it. |
This controlled comparison is stronger than a broad reset because it changes one prerequisite and leaves product identity, evidence source and observation method stable.
Safe recovery direction
A supported correction is to identify the Application ID and restore or regenerate its official policy data. A representative incident is a package cleanup removes the fast-query policy set.
Changes that make this code harder to diagnose
- avoid using rearm or key replacement as a universal package/policy repair; it changes evidence without proving the named boundary.
- avoid copying license packages or protected stores from another computer; it changes evidence without proving the named boundary.
- avoid force-deleting policy, plug-in or license files while sppsvc owns them; it changes evidence without proving the named boundary.
Technical references
- WMI properties and methods for volume activation — official reference for the mechanism surrounding it.
- Slmgr.vbs options
- Troubleshoot Windows activation error codes
- MS-ERREF Windows Error Codes
Looking for a different code? Search another status or error code.