| Previous | Next |
| SL_E_CIDIID_MISMATCHED_PKEY | SL_E_LICENSE_NOT_BOUND |
SL_E_CIDIID_NOT_BOUND
What this result narrows down
Interpret SL_E_CIDIID_NOT_BOUND inside offline IID/CID activation, not as a generic activation failure. Windows has reached the offline activation exchange in which an Installation ID is generated for one activation context and a Confirmation ID is returned for that same context; in this case, the offline identifiers do not bind to the machine environment currently presenting them.
Record both this result and 0xC004F07F. Licensing wrappers often preserve only a friendly message, but the facility value is what separates key, KMS, certificate, offline, OEM, Store, and state-machine failures.
What to collect from the affected system
Record hardware/firmware or VM-generation changes since IID creation, Activation ID, key, and the machine identity used by the activation workflow. Before changing the system, add the following context:
- Product identity: Activation ID selected for /dti and /atp.
- Activation context: IID and CID length/version without publishing the complete identifiers.
- State at failure: partial product key and edition/channel.
- Correlation evidence: hardware or environment change between IID generation and CID deposit.
- Change history: exact slmgr or API operation and Software Protection event.
How to test the failing stage
- Begin with the operation that emitted this result and its target Activation ID.
- Inventory Activation ID, product key, Installation ID, Confirmation ID, hardware binding and deposit operation; this establishes whether the request was aimed at the intended product and activation channel.
- Use events and tool output to demonstrate: record hardware/firmware or VM-generation changes since IID creation, Activation ID, key, and the machine identity used by the activation workflow.
- Rule out the adjacent case: this is an environment-binding problem rather than a formatting or check-digit error.
- After the targeted fix, verify both the immediate HRESULT and the persistent licensing state after service restart or reboot when relevant.
The surrounding licensing model prevents two common misdiagnoses. Formatting errors, unsupported versions, mismatched IDs, and a failure to save a valid CID occur at different points and should not be merged into one “telephone activation failed” message. The Installation ID must be obtained before the Confirmation ID is deposited; the returned CID is tied to the activation context represented by that IID.
The diagnostic fork is precise: this is an environment-binding problem rather than a formatting or check-digit error. A broad instruction to “try another key” or “check the Internet” would discard the more specific condition already established by the code.
Actions that usually make this harder to diagnose
- Avoid posting complete installation or confirmation identifiers in public logs.
- Avoid reusing a CID produced for another IID, product key, or machine state.
Choose recovery by the producing stage
| Result | Different condition |
|---|---|
SL_E_CIDIID_MISMATCHED_PKEY | Different condition: the offline IID/CID exchange belongs to a product key different from the key currently selected for activation. |
SL_E_CIDIID_INVALID_CHECK_DIGITS | Different condition: the local Software Protection Platform detects invalid integrity digits in the supplied IID/CID value. |
SL_E_CIDIID_MISMATCHED | Different condition: the Confirmation ID was issued for a different Installation ID than the one represented by the current request. |
How to correct the producing condition
Use the targeted fix: generate the IID after the target environment is stable and request a new CID for that environment. Avoid simultaneous key changes, store resets, service restarts, and network changes because they make it impossible to identify which precondition mattered.
Representative failure: A VM is moved or materially reconfigured between generating its IID and applying the CID.
Verification after the change
Build a regression case that intentionally creates “the offline identifiers do not bind to the machine environment currently presenting them” and asserts it. The corrected case should change only the relevant input, then verify the same Activation ID, final LicenseStatus/Reason, and any relevant grace, renewal, certificate, binding, or expiry data.
Technical references
- Slmgr.vbs activation options — diagnostic and operational context.
- Microsoft activation error-code troubleshooting — supported tools and state fields used to verify the resulting state.
- ActivateOffline WMI method — Microsoft guidance for the activation mechanism represented by this HRESULT.
- SoftwareLicensingProduct WMI class — platform behavior relevant to this HRESULT.
Looking for a different code? Search another status or error code.