| Previous | Next |
| SL_E_PROXY_POLICY_NOT_UPDATED | SL_E_LICENSE_MANAGEMENT_DATA_NOT_FOUND |
SL_E_CIDIID_INVALID_CHECK_DIGITS
Where this licensing result is produced
SL_E_CIDIID_INVALID_CHECK_DIGITS belongs to offline IID/CID activation. The producing mechanism is 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. The important boundary is: the local Software Protection Platform detects invalid integrity digits in the supplied IID/CID value.
This result is HRESULT 0xC004F04D. Pair it with the selected product/Activation ID and operation name so later logs do not attribute an add-on, edition, or volume-license result to the base Windows product.
Checks in the order that matters
- 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: compare grouped digits to the authoritative source, inspect OCR/manual entry, and record which stage copied the value.
- Rule out the adjacent case: this identifies transcription corruption rather than an activation-server policy refusal.
- After the targeted fix, verify both the immediate HRESULT and the persistent licensing state after service restart or reboot when relevant.
A useful diagnostic record
To verify this, compare grouped digits to the authoritative source, inspect OCR/manual entry, and record which stage copied the value. Before changing the system, add the following context:
- Product identity: exact slmgr or API operation and Software Protection event.
- Activation context: Activation ID selected for /dti and /atp.
- State at failure: IID and CID length/version without publishing the complete identifiers.
- Correlation evidence: partial product key and edition/channel.
- Change history: hardware or environment change between IID generation and CID deposit.
Two platform rules are especially relevant to this result. 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. 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.
Choose recovery by the producing stage
| Result | Different condition |
|---|---|
SL_E_CIDIID_MISMATCHED | Different condition: the Confirmation ID was issued for a different Installation ID than the one represented by the current request. |
SL_E_CIDIID_NOT_DEPOSITED | Different condition: a Confirmation ID passed validation far enough to be processed but could not be committed to the local licensing state. |
SL_E_CIDIID_INVALID_DATA_LENGTH | Different condition: the local deposit operation receives an IID/CID payload with the wrong total encoded length. |
Do not infer the cause of it from the activation UI alone. This identifies transcription corruption rather than an activation-server policy refusal. Keep the exact HRESULT in user-facing diagnostics instead of collapsing it into a generic activation failure.
Targeted fix
The appropriate correction is to correct the altered group or reacquire the CID and rerun the deposit command once. Keep the original evidence until a subsequent status query confirms that the intended Activation ID reached the expected state.
Representative failure: A photographed CID is transcribed with an 8 read as a 3.
Actions that usually make this harder to diagnose
- Avoid reusing a CID produced for another IID, product key, or machine state.
- Avoid posting complete installation or confirmation identifiers in public logs.
Verification after the change
Verification should include a failing fixture for “the local Software Protection Platform detects invalid integrity digits in the supplied IID/CID value” and a passing fixture after the targeted fix. Reboot or restart only when the documented mechanism requires it, and confirm that the state persists afterward.
Technical references
- Slmgr.vbs activation options — platform behavior relevant to this HRESULT.
- Microsoft activation error-code troubleshooting — diagnostic and operational context.
- ActivateOffline WMI method — supported tools and state fields used to verify the resulting state.
- SoftwareLicensingProduct WMI class — Microsoft guidance for the activation mechanism represented by this HRESULT.
Looking for a different code? Search another status or error code.