Fix it now
Microsoft documents 0xC004F04D as SL_E_CIDIID_INVALID_CHECK_DIGITS: the Installation ID or the Confirmation ID is not valid. The numbers themselves fail their own validation, so the answer is a fresh pair rather than a repair to the machine. 0xC004F02D is not published and behaves the same way in practice.
slmgr /dti
slmgr /atp <Confirmation ID>
slmgr /dli
- Discard any Installation ID you were holding from earlier.
slmgr /dtiprints the one that is current now, which is the only one worth anything. - Obtain a Confirmation ID against that value, not against the one in an old ticket or screenshot.
- Submit it with
slmgr /atprather than typing it into the dialog. Copying both halves removes the step where check digits usually fail. - Complete the exchange in the same session, without rebooting, reinstalling the key or running any repair in between.
- If it still fails, reinstall the product key with
slmgr /ipkand start the exchange again from a freshslmgr /dti.
Both halves have check digits. A single wrong character anywhere in either number fails validation, which is why the fix is always a fresh pair rather than an edit.
If activation completes, you are done. If the pair is refused again, the next section covers what validation is actually rejecting.
Why it happens
Offline activation moves two long numbers between two systems. Windows produces an Installation ID from the installed key and the installation; Microsoft produces a Confirmation ID for that specific Installation ID; Windows checks what it is given before doing anything with it. Both numbers carry check digits, and that is the mechanism these codes are reporting on.
Microsoft documents 0xC004F04D as SL_E_CIDIID_INVALID_CHECK_DIGITS, with the description that the Installation ID or the Confirmation ID is not valid. It is a documented return value of the functions Windows uses to deposit an offline Confirmation ID, which is exactly the operation you are performing. Nothing in that description says anything about a version of the offline exchange, and a good deal of material about this code claims otherwise.
0xC004F02D is not published at all, and neither are 0xC004F02E, 0x803FA08D or 0x803FA090. What can be said about them is that they arrive at the same point in the same operation and clear the same way, so treat them as company rather than as separate diagnoses.
The practical distinction worth carrying is between three failures that feel identical. 0xC004F02C is a shape problem: the value is the wrong length or contains something that is not a digit. These codes are a validation problem: the value looks right and does not verify. And a value that verifies but belongs to a different Installation ID fails later still. All three are fixed by the same move – a fresh pair, collected and applied in one session – which is why it is worth doing that properly the first time.
A stale Installation ID was reused
You have this one if The ID came from a note, a screenshot or a ticket raised some time ago rather than from the machine as it is now.
- Discard the stored Installation ID entirely.
- Run
slmgr /dtiand use the value it prints now. - Request a Confirmation ID against that value and apply it straight away with
slmgr /atp.
Treat an Installation ID as valid for one working session on one machine. Anything longer and it becomes a liability rather than a shortcut.
The machine changed between collection and entry
You have this one if A feature update installed, the key was reinstalled, or the machine was rebuilt after the ID was captured.
- Let any pending update or restart finish completely first.
- Confirm the installed key is the one you intend to activate:
slmgr /dli. - Start the exchange again from a fresh
slmgr /dti, and complete it before anything else touches the machine.
A character was lost or altered in transit
You have this one if The value was read aloud, retyped, or pasted through something that reformats text.
- Paste the value into a plain text editor and check it against the source character by character.
- Strip spaces, dashes and line breaks before submitting.
- Use
slmgr /atpso the whole value goes in at once rather than group by group.
The Confirmation ID is for a different product
You have this one if The same ticket or call covered both Windows and an Office installation, and the values were used in the wrong place.
- Check which product you are activating before entering anything.
- Match the Confirmation ID against the Installation ID it was issued for.
- Obtain a fresh value for the product actually in front of you.
The value came from a third-party tool
You have this one if The Confirmation ID was produced by a downloaded utility or a website rather than by Microsoft.
- Discard it. Values from those sources fail validation by design.
- Attempt online activation first; most machines at this dialog do not need to be there.
- For an isolated network with several machines, use VAMT proxy activation rather than the telephone route.
Full reference
Telling the three offline failures apart
| Code | What is wrong with the value | What to do |
|---|---|---|
0xC004F02C |
The shape: wrong length, or something that is not a digit | Re-enter it, digits only, every group complete |
0xC004F04D |
Validation: the Installation ID or Confirmation ID does not verify | Start again from a fresh slmgr /dti |
0xC004F02D |
Not published. Behaves like the row above in practice | Same answer: a fresh pair in one session |
| A pairing failure later in the process | The value verifies but belongs to a different Installation ID | Get a Confirmation ID for the ID showing now |
The commands that keep this simple
| Command | What it does |
|---|---|
slmgr /dti |
Displays the current Installation ID for offline activation |
slmgr /atp <Confirmation ID> |
Activates using the Confirmation ID you supply |
slui 4 |
Opens the phone activation dialog, if you would rather use it |
slmgr /ipk <key> |
Installs a product key. This regenerates the Installation ID |
slmgr /dli |
Confirms which key is installed and the licence status |
slmgr /rearm |
Resets activation timers. Also called by sysprep /generalize |
Using slmgr /dti and slmgr /atp rather than the dialog is the single highest-value change in this article. Both values can then be copied and pasted, and check digits are only ever wrong because a character moved.
Planning the exchange so it works first time
- Finish everything else on the machine first: updates, restarts, key installation, any repair.
- Confirm the key you intend to activate is the one installed, with
slmgr /dli. - Read the Installation ID with
slmgr /dtiand copy it, rather than transcribing it. - Obtain the Confirmation ID for that exact value.
- Apply it with
slmgr /atpin the same session, and confirm withslmgr /dliandslmgr /xpr.
Written out, that looks obvious. It is worth writing out because the common failure is doing these steps in a different order – collecting an ID at the start of a build and applying a Confirmation ID at the end of it, with a rekey and two restarts in between.
When it keeps failing on one machine
- Reinstall the product key with
slmgr /ipk, then collect a completely fresh Installation ID. This regenerates both halves of the problem. - Rebuild the licence files with
slmgr /rilcand restart the Software Protection service, then try again. - Confirm you are not activating a product other than the one you think. Windows and Office have separate exchanges.
- Confirm the machine has finished any pending servicing operation, which can change what the Installation ID is derived from.
- If the machine can reach the internet at all, use online activation. Most machines that end up here do not need to be here.
Why none of this is an entitlement problem
These codes describe a mismatch between two numbers. Your key, your entitlement and your activation count are unaffected, and a failed attempt does not consume anything. If a tool or service is asking to be paid to generate a Confirmation ID, it cannot do what it is claiming: nothing outside Microsoft’s activation service can compute a value that validates.
The same applies to reinstalling Windows. Nothing about the installation is damaged. What has gone wrong is which pair of values you are holding, and starting the exchange again resolves it without touching the system.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F02D |
Reported during offline activation. Microsoft publishes no meaning for it; in practice it clears the same way as the validated-pair failure below | not published by the vendor |
0x803FA08D |
Seen from the Settings activation client in the same circumstances. No published meaning | not published by the vendor |
0xC004F02E |
Another offline activation refusal in the same area. No published meaning | not published by the vendor |
0xC004F04D |
SL_E_CIDIID_INVALID_CHECK_DIGITS: the Installation ID or the Confirmation ID is not valid. Documented as a return value of the offline Confirmation ID functions | Microsoft Learn |
0x803FA090 |
Reported alongside the codes above. No published meaning, and no source pairs it with a specific 0xC004F code | not published by the vendor |
Confirm the fix worked
- The activation completes rather than returning you to the entry boxes.
slmgr /dlireports Licence Status: Licensed.slmgr /xprreports permanent activation rather than a grace window.slmgr /dtiand the Confirmation ID you used belong to the same session on this machine.- Reboot and re-check, so you know the state survived a restart.
Questions people ask about this
How long does an Installation ID stay usable?
Treat it as valid only while the machine stays as it was when the ID appeared. A rekey, a feature update, a rebuild or a significant hardware change produces a new one, and any Confirmation ID issued against the old value stops being useful at that moment.
Is this different from 0xC004F02C?
Yes, and the difference is worth noticing. 0xC004F02C is a shape check: wrong length, or a character that is not a digit. 0xC004F04D is documented as the Installation ID or Confirmation ID not being valid, which is a validation failure on numbers that look right.
Do I need to reinstall Windows?
No. Nothing about the installation is damaged. The only thing wrong is which pair of values you are holding, and a fresh exchange resolves it.
Will this cost anything to sort out?
No. Your key, entitlement and activation count are unaffected, and a failed attempt consumes nothing. Anything asking to be paid to generate a Confirmation ID cannot produce one that validates.
Is 0xC004F02D a version mismatch?
There is no source for that. Microsoft publishes no meaning for 0xC004F02D at all, and the code it is usually paired with, 0xC004F04D, is documented as a check-digit failure on the Installation ID or Confirmation ID. A fresh pair is the answer for both.
