| Previous | Next |
| SL_E_BLOCKED_PRODUCT_KEY | SL_E_MISSING_OVERRIDE_ONLY_ATTRIBUTE |
SL_E_DUPLICATE_POLICY
The stage that stopped
SL_E_DUPLICATE_POLICY is HRESULT 0xC004F052. It belongs to the local Software Protection Platform. Its narrow boundary is: the combined license set defines the same policy more than once where uniqueness is required.
AllStat records “The Software Licensing Service reported that the licenses contain duplicated properties” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
Why the producing layer matters
| 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
- The result is local to Software Protection Platform and should be tied to one product object, not the computer in general.
- evaluated licensing rules or their cache are the producing layer.
- The suffix names the object or transition to inspect before any broad activation reset.
- Its HRESULT severity is failure; later status messages can describe only the resulting state.
Evidence that avoids a false diagnosis
| 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? |
| policy ID, source package and cache generation | For this HRESULT: Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | For this HRESULT: Does the evidence support “inventory contributing licenses and remove/reinstall the unintended duplicate through supported package management” rather than two different policies whose evaluated values conflict? |
Diagnostic sequence
- Record
0xC004F052, UTC time, caller and the first method or server request that returned it. - Capture first API/slmgr method and earliest Security-SPP event specifically for this HRESULT.
- Prove the distinction between the named boundary and two different policies whose evaluated values conflict before remediation.
- 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.
REM Evidence context: SL_E_DUPLICATE_POLICY
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Important distinctions
| Result | Different condition |
|---|---|
SL_E_MISSING_OVERRIDE_ONLY_ATTRIBUTE | an override policy lacks the attribute that marks or constrains it as override-only |
SL_E_LICENSE_MANAGEMENT_DATA_DUPLICATED | license-management metadata appears more than once where the schema permits one record |
SL_E_LICENSE_MANAGEMENT_DATA_NOT_FOUND | license-management metadata required to evaluate or maintain the license is absent |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | Overlapping add-on packages publish duplicate policy identifiers. |
| Single variable | Change only the narrow input or state named by the HRESULT while product identity remains fixed. |
| Positive control | A known-good value at that boundary succeeds and the failing fixture still reproduces the code. |
| Different result | If the experiment instead proves “an override policy lacks the attribute that marks or constrains it as override-only”, follow that neighboring boundary rather than treating it as it. |
Fix the prerequisite, then verify
A supported correction is to inventory contributing licenses and remove/reinstall the unintended duplicate through supported package management. A representative incident is overlapping add-on packages publish duplicate policy identifiers.
Changes that make this code harder to diagnose
- 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.
- avoid using rearm or key replacement as a universal package/policy repair; it changes evidence without proving the named boundary.
Technical references
- Slmgr.vbs options — official reference for the mechanism surrounding it.
- Troubleshoot Windows activation error codes
- MS-ERREF Windows Error Codes
- SoftwareLicensingProduct WMI class
Looking for a different code? Search another status or error code.