Fix it now
Microsoft publishes no meaning for 0xC004E01D, so judge it by what the machine does: it understands the key and refuses to attach it to this installation. The usual reasons are an evaluation build, which is converted with DISM rather than keyed, and a channel or edition mismatch. Establish which of the two you have before changing anything.
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
cscript //nologo %windir%\system32\slmgr.vbs /dli
- If the current edition name contains Evaluation, stop entering keys. Evaluation media is converted, not activated.
- Convert to an edition you hold a licence for, using one from the target list:
DISM /online /Set-Edition:<TargetEdition> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, then reboot. - If your target edition is not in that list, Microsoft’s documented answer is a fresh install of the retail version you want.
- If the edition is not an evaluation, compare the channel in the
/dlioutput with what the key was sold as. Retail, OEM and volume keys do not cross.
On Windows client, an upgrade such as Home to Pro is done by entering the key at Settings > System > Activation > Change product key, or with changepk.exe /ProductKey <key>. DISM edition conversion is a Windows Server operation.
If the conversion or the matching key activates the machine, you can stop here. If not, the next section covers what an installation will and will not accept, and why.
Why it happens
None of the five codes in this record is published by Microsoft. That is worth saying plainly, because articles about this error usually assign each of them a confident meaning and there is nothing behind it. What can be described is the behaviour: the licensing service reads the key, decides it does not belong to this installation, and refuses it locally. The refusal is instant and identical whether the machine is online or not, which is itself the diagnosis.
A Windows installation is not a blank slate waiting for any key. The image carries licence files describing which editions and channels it is prepared to be, and the licensing service looks for a match among them before it does anything else. Evaluation media is the clearest case: it is built to run for a fixed period and carries no licence for the full product, so there is nothing for a retail key to bind to.
Microsoft’s supported route for that case is conversion rather than keying. DISM /online /Set-Edition writes the correct licence files and applies the key in one operation, and the documented restrictions are worth knowing before you start. An evaluation domain controller cannot be converted at all. Since Windows Server 2016 an evaluation Desktop Experience installation cannot become a retail Server Core one. An evaluation Datacenter installation can only become retail Datacenter, not Standard. Windows Server Essentials is converted with slmgr /ipk rather than DISM.
The machine is running evaluation media
You have this one if DISM /online /Get-CurrentEdition returns an edition name containing Evaluation, and the desktop shows an expiry warning.
- Run
DISM /online /Get-TargetEditionsand note which editions are offered. - Read the licence terms first if you want them:
DISM /online /Set-Edition:<TargetEdition> /GetEula:C:\license.rtf. - Convert:
DISM /online /Set-Edition:<TargetEdition> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, then reboot. - Confirm with
DISM /online /Get-CurrentEditionand activate withslmgr /ato.
If the machine is already a domain controller, Microsoft’s documented route is to build a new retail DC, transfer the FSMO roles to it, then remove AD DS from the evaluation one. There is no in-place conversion.
The key is for a different channel from the installed image
You have this one if slmgr /dli describes the installation as retail, OEM or volume, and your key belongs to one of the other two.
- Read the channel from
slmgr /dliand compare it against the invoice rather than against memory. - If they do not match, reinstall from media of the correct channel, or obtain a key for the channel already installed.
- Install the key with
slmgr /ipkand activate withslmgr /ato.
The key is an upgrade-only key on a clean installation
You have this one if The key was sold as an upgrade, and the machine was built from scratch rather than upgraded from an earlier Windows.
- Look for 0xC004F061 in the output, which Microsoft documents as a key that can only be used for upgrading and not for clean installations.
- Install the qualifying earlier version first and upgrade, or obtain a full licence for this installation.
This is one of the few situations in this family where Microsoft does publish a code, so it is worth checking for before assuming the key is dead.
The edition on disk sits above the edition the key licenses
You have this one if An Enterprise or Education installation refusing a Pro key, or an LTSC installation refusing a general availability key.
- Confirm the installed edition with
winver. - Microsoft documents supported downgrade paths only from Enterprise and Education. Everything else means a clean installation of the edition you own.
- Back up user data before you start, then install the matching edition and supply the key.
Upward changes are straightforward and downward ones are not. Decide the edition before deployment rather than afterwards.
Full reference
The conversion and edition commands, and what each is for
| Command | What it does | Where it applies |
|---|---|---|
DISM /online /Get-CurrentEdition |
Reports the installed edition, including whether it is an evaluation | Windows Server |
DISM /online /Get-TargetEditions |
Lists the editions this installation can be converted to | Windows Server |
DISM /online /Set-Edition:<ed> /GetEula:C:\license.rtf |
Writes out the licence terms for the target edition | Windows Server |
DISM /online /Set-Edition:<ed> /ProductKey:<key> /AcceptEula |
Converts the installation and applies the key | Windows Server |
changepk.exe /ProductKey <key> |
Changes the product key, and with it the edition, on Windows client | Windows client |
cscript.exe c:\windows\system32\slmgr.vbs /ipk <key> |
Installs a key from the command line with console output | Both |
slmgr /dli |
Shows the current edition, channel and partial key | Both |
An edition conversion rewrites system components and cannot be reversed without reinstalling. Take a backup or a snapshot first, and do not run one on a production server during working hours.
What the documented restrictions actually rule out
| Starting point | Can it be converted | What Microsoft documents |
|---|---|---|
| Evaluation Standard, Desktop Experience | Yes | To retail Standard or Datacenter, Desktop Experience |
| Evaluation Standard Core | Yes | To retail Datacenter Core |
| Evaluation Desktop Experience to retail Server Core | No | Blocked since Windows Server 2016 |
| Evaluation Datacenter to Standard | No | Datacenter converts only to retail Datacenter |
| An evaluation domain controller | No | Build a new retail DC, move the FSMO roles, then demote the evaluation one |
| Windows Server Essentials | Yes | Converted with slmgr /ipk rather than DISM |
Windows client is a different set of rules
On the client side there is no DISM edition conversion to reach for. Microsoft documents Home to Pro as supported by entering a product key or buying through the Microsoft Store, and specifically not by the command-line tool, MDM or a provisioning package. Paths such as Pro to Enterprise or Pro to Education support all of those methods. Downgrades are documented only from Enterprise and Education; where a downgrade path is not supported, a clean install is required.
That asymmetry explains most client-side cases of this error. A Pro key offered to a Home installation is a supported upgrade and will be accepted through Settings. A Home key offered to a Pro installation is not a supported change at all, and no amount of retyping turns it into one.
When none of the above matches
- Check whether the installation is a preview build. Preview images are licensed by the programme they came from rather than by a retail key, and moving to a released build is the only route to a normal licence.
- Check whether the key is for a different product entirely – Windows Server, Office or an ESU add-on. The 25-character shape is identical across all of them and order emails look alike.
- Read
slmgr /dlvin full rather than/dli. The description line names the product it thinks it is, which is often not what the person at the keyboard assumed. - If a conversion was interrupted, the installation may be between two editions. Re-run
DISM /online /Get-CurrentEditionand complete the conversion properly rather than starting a new one. - If the target edition is genuinely not offered, Microsoft’s documented answer is a fresh install of the version you want. There is no supported workaround.
When a licence is the actual fix
If the installation and the key belong to different worlds, one of the two has to change. Reinstalling costs nothing but a day; buying the key that matches what is already deployed usually costs less overall, and on a production server it is not close. Arco supplies Windows 11 Pro retail keys and Windows Server licences, and will read the output of slmgr /dli or DISM /online /Get-CurrentEdition with you first, so the licence you order is one this installation will actually accept rather than one that produces the same refusal again. If the answer is that a conversion you can run yourself will fix it, we will tell you that instead.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004E01D |
Seen when the licensing service refuses to attach a key to the current installation. Microsoft publishes no meaning for it; diagnose by edition, channel and whether the image is an evaluation | not published by the vendor |
0xC004E01E |
Raised at the same stage of the licensing exchange. No published meaning | not published by the vendor |
0xC004E01F |
Another refusal from the same stage. No published meaning; check edition and channel before anything else | not published by the vendor |
0xC004E01C |
Appears while the installed licence set is being matched against the key. No published meaning | not published by the vendor |
0xC004E019 |
A related licensing failure with no published meaning. Treat it as the same class of mismatch | not published by the vendor |
Confirm the fix worked
DISM /online /Get-CurrentEditionno longer contains the word Evaluation.slmgr /dlinames the edition and channel you intended, with Licence Status reading Licensed.slmgr /xprreports permanent activation rather than a countdown.- Any expiry warning on the desktop has gone after a reboot.
Questions people ask about this
Can I activate a Windows Server evaluation with a normal key?
No. The evaluation image carries no licence for the full product, so the key has nothing to bind to. Convert with DISM /online /Set-Edition, supplying the key as part of that command, and reboot.
Does converting an evaluation lose my data?
The supported conversion runs in place and keeps roles, features and data. It is still a major change, so take a snapshot or backup first and expect at least one reboot.
My server is a domain controller. Can I convert it?
No. Microsoft documents that an evaluation domain controller cannot be converted to retail. The supported route is to install a new domain controller on the retail version, transfer the FSMO roles to it, then remove AD DS from the evaluation server.
Why can I go from Home to Pro but not back again?
Microsoft documents supported downgrade paths only from Enterprise and Education. Home to Pro is a supported upgrade by product key or through the Store; the reverse is not a supported path, so it means a clean installation.
What does 0xC004E01D actually mean?
Microsoft does not publish a meaning for it, and neither does anyone else who can be relied on. What is reliable is when it appears: at the moment a key is offered to an installation that has no licence matching it. Diagnose it by edition, channel and evaluation status rather than by the number.
