| Previous | Next |
| SL_REMAPPING_MDOLLAR_CIDIID_INVALID_DATA_LENGTH | SL_REMAPPING_MDOLLAR_TIMEBASED_ACTIVATION_BEFORE_START_DATE |
SL_REMAPPING_MDOLLAR_CIDIID_INVALID_CHECK_DIGITS
What Windows has already determined
SL_REMAPPING_MDOLLAR_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 the boundary is: the hosted activation service detects that IID/CID check digits do not agree with the remaining digits.
Telemetry should retain 0x803FA090, this result, and the affected Activation ID. The same computer can expose several licensing products, and a state read from the wrong instance can contradict the operation that actually failed.
The surrounding licensing model prevents two common misdiagnoses. for this HRESULT: 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. for this HRESULT: 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.
What to collect from the affected system
The decisive record is to compare each group against the original output, note human transcription or OCR, and keep the selected Activation ID and key channel. Before changing the system for this HRESULT, add the following context:
- Product identity for this HRESULT: IID and CID length/version without publishing the complete identifiers.
- Activation context for this HRESULT: partial product key and edition/channel.
- State at failure for this HRESULT: hardware or environment change between IID generation and CID deposit.
- Correlation evidence for this HRESULT: exact slmgr or API operation and Software Protection event.
- Change history for this HRESULT: Activation ID selected for /dti and /atp.
When investigating this result, protect secrets while collecting evidence. Full product keys, complete IID/CID values, private keys, PINs, challenge blobs, account credentials, and unredacted certificate material for this HRESULT do not belong in public tickets. Partial keys, hashes, thumbprints, IDs, timestamps, and state transitions are normally enough to correlate the failure.
Important distinctions
| Result | Different boundary |
|---|---|
SL_REMAPPING_MDOLLAR_CIDIID_INVALID_DATA_LENGTH | Relative to this result: the hosted activation service receives an offline identifier whose encoded length is incompatible with the expected version. |
SL_REMAPPING_MDOLLAR_CIDIID_INVALID_DATA | Relative to this result: the hosted activation service cannot parse the offline activation payload as a valid IID/CID data structure. |
SL_REMAPPING_MDOLLAR_CIDIID_INVALID_VERSION | Relative to it: the hosted activation response identifies an unsupported version in the offline IID/CID exchange. |
The comparison is also useful for tests: each branch should have a fixture that produces its own HRESULT and verifies the expected persistent licensing state.
A practical investigation order
- Identify whether it came from key installation, activation, renewal, validation, certificate selection, offline deposit, or status query.
- tie that call to Activation ID, product key, Installation ID, Confirmation ID, hardware binding and deposit operation.
- capture the proof needed for this specific result: compare each group against the original output, note human transcription or OCR, and keep the selected Activation ID and key channel.
- use the related-code comparison below to avoid correcting the wrong layer.
- retest with a fresh operation generation and confirm that no parallel retry or stale response can overwrite the result.
Do not infer the cause of it from the activation UI alone. Check-digit failure points to altered digits; it is more specific than a product-key mismatch. Preserve the boundary when converting the HRESULT into user-facing diagnostics.
Actions that usually make this harder to diagnose
- While diagnosing it, avoid reusing a CID produced for another IID, product key, or machine state. That action changes evidence for this HRESULT without correcting the established boundary.
- avoid posting complete installation or confirmation identifiers in public logs. The result already narrows the problem more precisely.
- do not delete licensing stores, edit signed license files, alter firmware markers, bypass certificate checks, or use unofficial activation tools. During investigation, those actions can create a second integrity problem and destroy the evidence needed to repair the legitimate license.
How to correct the producing condition
Recovery should preserve entitlement and state rather than erase symptoms. In this case, correct the transcription or regenerate the IID rather than retrying the same invalid sequence; then query the same product instance and retain the post-fix it HRESULT and status.
Representative failure: One spoken CID group is entered with two digits reversed, causing its integrity check to fail.
Verification after the change
Build a regression case that intentionally creates “the hosted activation service detects that IID/CID check digits do not agree with the remaining digits” and asserts it. The corrected the case should change only the decisive 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 — platform behavior relevant to it.
- Microsoft activation error-code troubleshooting — diagnostic and operational context for this HRESULT.
- ActivateOffline WMI method — supported tools and state fields used to verify it.
- SoftwareLicensingProduct WMI class — Microsoft guidance for the activation mechanism represented by it.
Looking for a different code? Search another status or error code.