| Previous | Next |
| SL_E_SERVICE_STOPPING | SL_E_AUTHN_WRONG_VERSION |
SL_E_PLUGIN_NOT_REGISTERED
What the constant narrows down
HRESULT 0xC004F076 is exposed as SL_E_PLUGIN_NOT_REGISTERED by the local Software Protection Platform. The code says more than the friendly message: the requested Software Protection plug-in is not registered for discovery.
AllStat records “The Software Licensing Service reported that the requested plug-in cannot 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.
From input to HRESULT
| 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 | An extensibility component and its manifest/registration are involved. |
| 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. |
Evidence to keep before remediation
| 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? |
| plug-in identity, registration and manifest version | For this HRESULT: Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | For this HRESULT: Does the evidence support “restore registration through the product installer and verify component version” rather than a registered plug-in with an invalid manifest or runtime failure? |
Redact full keys, activation blobs, account tokens, private certificate material and raw hardware identifiers. Partial keys, hashes, IDs and UTC timestamps retain correlation value without publishing secrets.
Work from identity to cause
- Prove the distinction between the named boundary and a registered plug-in with an invalid manifest or runtime failure 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.
- Record
0xC004F076, UTC time, caller and the first method or server request that returned it. - Capture caller identity and elevation specifically for this HRESULT.
REM Evidence context: SL_E_PLUGIN_NOT_REGISTERED
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"Similar messages, different boundaries
| Result | Different condition |
|---|---|
SL_E_SERVICE_STOPPING | the Software Protection service is in shutdown and cannot begin or finish this operation |
SL_E_AUTHN_WRONG_VERSION | authentication data uses a version incompatible with the local licensing verifier |
SL_E_AUTHN_MISMATCHED_KEY | the authentication response or data is bound to a different key than the verifier expects |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A plug-in DLL remains on disk after its registration is removed. |
| 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 “the Software Protection service is in shutdown and cannot begin or finish this operation”, 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.
What successful remediation must prove
A supported correction is to restore registration through the product installer and verify component version. A representative incident is a plug-in DLL remains on disk after its registration is removed.
Changes that make this code harder to diagnose
- 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.
- avoid copying license packages or protected stores from another computer; it changes evidence without proving the named boundary.
Technical references
- Troubleshoot Windows activation error codes — official reference for the mechanism surrounding it.
- MS-ERREF Windows Error Codes
- SoftwareLicensingProduct WMI class
- SoftwareLicensingService WMI class
Looking for a different code? Search another status or error code.