0xC004F069 Activation Error: How to Fix It on Windows Server

The 0xC004F069 activation error means the Software Licensing Service could not find the product SKU your key belongs to: the key is for a different edition or version than the one installed, or the server is an evaluation build that will not take a retail key directly. To fix 0xC004F069 on Windows Server, check the edition with DISM, convert an evaluation install with DISM /online /Set-Edition, or install a key for the exact edition and version you run.

On Server Core the code often arrives with a puzzling line: “On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC004F069’ to display the error text.” That is just Windows telling you the full message is not available in a console session. The full text is “The Software Licensing Service reported that the product SKU is not found.” Short version: wrong key for this installation.

Key takeaways

• 0xC004F069 = product SKU not found: the key does not match the installed edition (Standard, Datacenter, Essentials) or version (2019, 2022, 2025).
• Evaluation installs are the top cause. slmgr /ipk with a retail or MAK key fails; convert first with DISM /online /Set-Edition:<edition> /ProductKey:<key> /AcceptEula.
• DISM /online /Get-CurrentEdition and DISM /online /Get-TargetEditions show what you have and what you can convert to.
• A Datacenter evaluation converts only to Datacenter retail, and an evaluation domain controller cannot be converted at all, per Microsoft Learn.
• CAL keys, Windows client keys and keys for another Server version produce the same error.

What does the 0xC004F069 activation error mean?

Error 0xC004F069 means Windows could not find a licensed product (SKU) on the system that matches the key you tried to install or activate. It shows up mostly on Windows Server when the key is for another edition or version, or when the server runs an evaluation build. Matching the key to the installed edition, or converting the edition, fixes it.

Every Windows installation carries license files for the editions it can become. When you run slmgr /ipk, the licensing service looks for the SKU that the key belongs to among those files. If none fits (a Windows Server 2022 Standard key on a Windows Server 2025 install, for example), the service gives up with 0xC004F069. Nothing is damaged. The key and the installation simply do not belong together.

What causes error 0xC004F069?

The common causes of 0xC004F069 are an evaluation installation that cannot accept a retail or volume key through slmgr, a key for a different edition (Standard key on Datacenter), a key for a different Server version, a Remote Desktop or user CAL key entered as a Windows key, and a Windows client key used on a server. Retail versus volume channel alone usually is not the problem.

• Evaluation build. The free 180-day evaluation ISO installs ServerStandardEval or ServerDatacenterEval. Those editions do not take production keys with slmgr /ipk; they need a DISM conversion.
• Edition mismatch. Datacenter keys do not install on Standard via slmgr, and Standard keys do not install on Datacenter.
• Version mismatch. Server keys are version-specific. A 2019 key does not activate 2022, and a 2022 key does not activate 2025.
• CAL key instead of a server key. RDS CAL packs and user CALs come with 25-character codes too. They belong in the Remote Desktop Licensing Manager, not in slmgr.
• Client key on a server. Windows 11 Pro or Windows 10 Enterprise keys have no SKU on Windows Server.
• Desktop Experience versus Core on evaluation. Since Windows Server 2016, Microsoft does not support converting a Desktop Experience evaluation to a Core retail install.

How to fix the 0xC004F069 activation error

To fix 0xC004F069, first confirm the installed edition and whether it is an evaluation. For an evaluation, list the target editions and convert with DISM and your retail key. For a non-evaluation server, install a key for the exact edition and version with slmgr /ipk, then activate with slmgr /ato and verify.

1. Open Command Prompt or PowerShell as administrator and run DISM /online /Get-CurrentEdition. An edition name ending in Eval (for example ServerStandardEval) means evaluation.
2. Run slmgr /dlv as a second check. “EVAL” in the description confirms an evaluation install; the line also shows the version and channel.
3. Compare with your key: the license confirmation should name the same version (2019, 2022, 2025) and edition (Standard, Datacenter, Essentials). If it names a CAL, it is not a server key.
4. For an evaluation, run DISM /online /Get-TargetEditions and note the edition you want, such as ServerStandard or ServerDatacenter.
5. Convert it: DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula. Restart when DISM asks; the conversion usually needs more than one restart.
6. For a non-evaluation server with a matching key, run slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX instead.
7. Activate with slmgr /ato, then run slmgr /dlv and check for “License Status: Licensed”.
8. If the key is for a version or edition you do not run, either get the right key or reinstall from media for the licensed edition and version.

Tip: Microsoft suggests saving the license terms first with DISM /online /Set-Edition:<edition> /GetEula:C:\license.rtf. It also confirms that DISM accepts the target edition name before you commit the key.

Which fix matches your cause? (Cause → Fix)

Each cause of 0xC004F069 points to one fix, and two commands usually reveal which applies: DISM /online /Get-CurrentEdition and slmgr /dlv. Compare their output with the version and edition on your license, then use the matching row below. Reinstalling is only needed when no conversion path exists.

How do I convert a Windows Server evaluation to stop 0xC004F069?

Convert an evaluation with DISM, not slmgr. Run DISM /online /Get-TargetEditions, pick the target, then run DISM /online /Set-Edition with the retail key and /AcceptEula. Microsoft Learn documents this path for Windows Server 2016 through 2025. After the restarts, slmgr /ato activates the server normally.

Two restrictions catch people. First, the evaluation edition decides your options: a Datacenter evaluation converts only to Datacenter retail, while a Standard evaluation can go to Standard or Datacenter. Second, an Active Directory domain controller cannot be converted. Microsoft’s Windows Server edition conversion guide says to stand up a retail DC, move the FSMO roles and remove AD DS from the evaluation server instead.

If you need a volume license (MAK or KMS) on that server, Microsoft’s advice is to convert to retail first and then switch channels with slmgr /ipk. Our walkthrough for converting Windows Server 2022 evaluation to Standard shows every screen of the DISM route, and the separate guide on activating Windows Server with DISM covers the error messages DISM itself can return.

Note: DISM conversion can take a while and often looks frozen at 10 percent. Leave it alone. Interrupting the process is a far bigger problem than the original 0xC004F069.

Can a Remote Desktop CAL key cause 0xC004F069?

Yes. Remote Desktop Services CALs and user or device CALs have 25-character codes that look like Windows keys, yet they do not license the operating system. Typed into slmgr /ipk or Settings, a CAL code fails with 0xC004F069 because no Windows SKU matches it. Install CALs through the Remote Desktop Licensing Manager instead.

The order matters for a new RDS host. Activate Windows Server itself with its own server key first. Then add the Remote Desktop Licensing role, activate the license server, and install the CAL pack there. The guide to managing CAL licenses in Windows Server 2022 goes through that sequence.

Does 0xC004F069 appear on Windows 10 or Windows 11?

It can, though far less often than on Windows Server. On Windows 10 and 11 it typically appears when a key for an edition with no matching SKU on the installation is used, for instance an Enterprise key on an Enterprise Evaluation install, or a server key on a desktop PC. The fix follows the same principle: match edition and key.

Windows 10 and 11 Enterprise evaluations differ from server evaluations in one painful detail: they typically cannot be converted in place, so a reinstall from regular media is the usual route. For Home and Pro, key mismatches tend to show other codes, which the overview of Windows 11 activation errors lists in one place.

What if the key is for a different Server version?

Then the key cannot activate this installation, whatever command you use. Windows Server keys are tied to one version, so you need either a key for the version installed or a reinstall of the version you hold a key for.

When the server is still new and empty, reinstalling the licensed version is usually the fastest route. When it already runs production roles, a key for the installed version is the practical answer. Need a key that matches? Windows Server 2025 Standard is available with instant email delivery, and the Windows Server 2022 activation guide covers each 2022 edition.

Where these steps apply

These steps apply to Windows Server 2016, 2019, 2022 and 2025 in Standard, Datacenter and Essentials editions, with Desktop Experience or Server Core, including evaluation installs. The DISM conversion commands follow Microsoft Learn. Windows 10 and 11 notes cover Enterprise and Education; Home and Pro rarely show this code.

• Windows Server 2025, 2022, 2019, 2016 Standard and Datacenter: all steps, DISM conversion included.
• Windows Server Essentials: converts to the full retail version with slmgr /ipk and a retail, volume or OEM key, as Microsoft documents.
• Server Core: same commands; read errors with slmgr /dlv since the GUI message is not shown.
• Windows 10 and 11 Enterprise or Education: edition check and key matching; evaluation builds need a reinstall.