| Previous | Next |
| SL_REMAPPING_SP_STATUS_INVALIDARG | SL_REMAPPING_SP_STATUS_INSUFFICIENT_BUFFER |
SL_REMAPPING_SP_STATUS_ALREADY_EXISTS
How to read this result without losing context
Keep the symbolic result SL_REMAPPING_SP_STATUS_ALREADY_EXISTS together with HRESULT 0xC004D105. The producer is the Software Protection security-processor API; at the stateful API layer that initializes a protected environment, validates handles and versions, commits changes, enumerates data and enforces trusted-time or debugger restrictions, Windows determined that creation was requested for an object or value that is already present in the protected environment.
For triage, treat this result as a the Software Protection security-processor API result. existing state is different from a duplicate serialized token or a trusted-store entry-key collision at a lower layer. Product-key changes or network tests are useful only when it evidence points back to those layers.
From HRESULT to a verified cause
- Identify the caller and operation generation that produced
0xC004D105. - preserve the first inner I/O, crypto, parser or policy status that precedes the public HRESULT.
- collect the code-specific evidence: record object identifier, namespace, create/open flags and whether the first creation committed successfully.
- rule out stale handles, parallel activation, incomplete servicing and image rollback where they affect this subsystem.
- retest once, then confirm LicenseStatus/LicenseStatusReason or the equivalent protected-object state persists.
Where it sits in the licensing pipeline
These results describe the protected API contract; they are not automatically evidence that the installed product key is invalid. The decisive proof for this HRESULT is to record object identifier, namespace, create/open flags and whether the first creation committed successfully.
Handle creation, mutation, commit and enumeration are separate stages, so the first failing call is more useful than a later activation summary. Keep that product/object identity because the same service can expose several independent licensing instances.
The diagnostic record that matters
| Item | Why it matters here |
|---|---|
| trusted time and system UTC time | Correlates service-level evidence with storage, crypto or policy evidence. |
| Security-SPP event sequence and caller process | Reveals whether servicing, migration, restore, cloning or concurrent work changed the precondition. |
| operation and API version | Identifies the protected object or product instance that returned the code. |
| environment or handle lifetime | Separates format/version failure from damage, absence or access failure. |
| buffer length and returned required size | Shows the state transition immediately before the HRESULT. |
Code-specific check: record object identifier, namespace, create/open flags and whether the first creation committed successfully.
What to repair—and what not to reset
Open/update the existing object when permitted or choose a genuinely new identifier. Preserve the original store, event export, hashes and licensing inventory until the operation succeeds and the expected state survives any required restart.
Representative case: A retry repeats create after the first request succeeded but its response was lost.
Do not confuse it with these nearby results
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_STATUS_INVALIDARG | Compared with this result, an API argument is outside the accepted range, combination or object contract. |
SL_REMAPPING_SP_STATUS_GENERIC_FAILURE | Compared with this result, the security processor failed without exposing a more specific public status at this boundary. |
SL_REMAPPING_SP_STATUS_INSUFFICIENT_BUFFER | Compared with this result, the caller-provided output buffer cannot hold the complete security-processor result. |
Actions that usually destroy useful evidence
- do not retrying the whole activation workflow without preserving the first API result.
- do not attaching debuggers or instrumentation to a protected production path while reproducing the issue.
- While resolving it, do not use unofficial activation tools, patched binaries, copied stores, disabled integrity checks or hand-edited signed data; they can create a second tamper condition.
Verification after correction
Repeat the operation that originally produced it, not merely a UI refresh. Confirm the exact product/object completes, review LicenseStatus and LicenseStatusReason when applicable, and check that no related boundary replaces it.
Regression testing, retain one failing fixture that reproduces “creation was requested for an object or value that is already present in the protected environment” and one passing fixture that changes only the decisive precondition; this avoids mistaking a broad reset for verification.
Technical references
- Software Licensing provider — official platform context used to interpret it.
- SoftwareLicensingService WMI class — supported state, API or recovery information relevant to it.
- SoftwareLicensingProduct WMI class — reference for this HRESULT evidence collection and post-repair verification.
- Windows SDK constants — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.