| Previous | Next |
| SL_REMAPPING_SP_STATUS_PUSHKEY_CONFLICT | SL_E_INVALID_CONTEXT |
SL_REMAPPING_SP_PUB_PROXY_SOFT_TAMPER
Where the failure occurs in Software Protection Platform
0xC004D702 maps to SL_REMAPPING_SP_PUB_PROXY_SOFT_TAMPER. This result belongs to Software Protection integrity and kernel-cache enforcement and narrows the operation to the integrity path that authenticates protected modules, compares security-processor state with kernel-mode policy data, restores cached state and detects proxy or patch interference. In concrete terms, a protected proxy execution path detected interference or returned an integrity-related failure.
This distinction matters because this is local protected-execution integrity, not an HTTP proxy connectivity error. A later “not licensed” state should not replace the first exact HRESULT in logs.
What to capture before recovery
- digital signature and file hash
- OS build and servicing level
- kernel-cache policy generation and reboot state
- SFC/DISM results and Security-SPP event correlation
- exact module/file and version
Where it sits in the licensing pipeline
A module or cache integrity result should be investigated as a component-integrity problem before changing product keys or activation endpoints. To verify this, identify proxy component, caller, loaded/injected modules, operation, inner status and system-file verification results.
Servicing tools can repair protected system files, while unofficial replacements, patchers or permission resets can create a second mismatch and destroy provenance.
From HRESULT to a verified cause
- Use read-only inspection first: identify proxy component, caller, loaded/injected modules, operation, inner status and system-file verification results.
Recommended handling
Remove unsupported hooks or patches and repair signed platform components.
Representative case: A security tool injects into a protected licensing proxy and changes its execution environment.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_KM_CACHE_TAMPER_RESTORE_FAILED | Compared with this result, the platform detected a damaged kernel-mode cache and its automatic restoration attempt also failed. |
SL_REMAPPING_SP_PUB_KM_CACHE_TAMPER | Compared with it, kernel-mode licensing cache data fails its integrity check. |
SL_REMAPPING_SP_PUB_TAMPER_SECURITY_PROCESSOR_PATCHED | Compared with it, the security-processor implementation appears patched or inconsistent with the signed platform image. |
Actions that usually destroy useful evidence
- Do not use unofficial activation, patching or proxy tools to bypass the integrity check.
- Do not replace protected binaries from another computer or build.
Technical references
- System File Checker — supported state, API or recovery information relevant to this HRESULT.
- Repair-WindowsImage — reference for evidence collection and post-repair verification.
- Software Licensing provider — technical contract for the subsystem producing it.
- Windows SDK constants — official platform context used to interpret it.
Looking for a different code? Search another status or error code.