Error 0xC004F069 means “the product SKU is not found”: the product key you entered doesn’t match the edition of Windows Server installed. In most cases the server is running the evaluation edition, which won’t accept a retail or MAK key through slmgr /ipk. To fix it, check the edition with DISM /online /Get-CurrentEdition, convert it with DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula (or ServerDatacenter), restart, then activate with slmgr /ato.
slmgr /ipk alone always fails.You’ve installed Windows Server 2022, typed in your product key, and Windows Script Host pops up with Error: 0xC004F069, telling you to run slui.exe 0x2a 0xC004F069 to display the error text. Settings may also refuse the key with a vague message. It’s one of the most common Windows Server activation errors, and it’s almost never a problem with the key itself.
This guide explains exactly what Windows Server 2022 activation error 0xC004F069 means, how to tell which edition you’re running, and how to fix it step by step: converting an evaluation edition, matching Standard and Datacenter keys, activating virtual machines, and handling domain controllers.
slmgr /ipk on Windows Server 2022.What Does Error 0xC004F069 Mean?
0xC004F069 is a Software Licensing Service error meaning “the product SKU is not found.” A SKU is a specific product edition, such as Windows Server 2022 Standard or Datacenter. When you enter a key, Windows looks for a licence on the server that matches it. If the installed edition doesn’t have a matching licence, activation fails with this code.
Microsoft’s own support team summarises it like this on Microsoft Q&A: if you have an evaluation server edition, you can’t use the slmgr /ipk command with a volume (MAK) or retail key directly to activate it.
Why does slmgr say “run slui.exe 0x2a”?
The slmgr script only shows the raw code. Running slui.exe 0x2a 0xC004F069 opens Windows’ activation window to display the full description. It won’t fix anything on its own, and on Server Core installations it doesn’t open at all, because Server Core has no graphical activation window.
Is my product key faulty?
Almost certainly not. A faulty or already-used key produces different errors, such as 0xC004F050 (invalid key) or 0xC004C008 (key already used). 0xC004F069 points to the installation, not the key. Once the edition matches, the same key usually activates first time.
What Causes Error 0xC004F069?
Step 1: Check Which Edition You’re Running
Before changing anything, find out exactly which edition is installed. Open Command Prompt as administrator (or PowerShell as administrator) and run:
DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditionsWhat each edition ID means
You can also check in Settings › System › About: an evaluation installation shows Windows Server 2022 Standard Evaluation or Datacenter Evaluation as the edition, and the desktop watermark shows the days remaining.
Fix 1: Convert the Evaluation Edition to a Full Edition
If DISM shows ServerStandardEval or ServerDatacenterEval, convert it to the full edition your key is for. Microsoft documents this in its guide to Windows Server upgrade and conversion options.
ServerStandard or ServerDatacenter, with your 25-character key.slmgr /ato to activate, then confirm with slmgr /xpr.For Windows Server 2022 Standard:
DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaFor Windows Server 2022 Datacenter:
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaIf DISM rejects your product key
Some volume (MAK) and retail keys fail inside the DISM command even though they’re valid. The standard workaround is to convert using Microsoft’s published generic KMS client key for your edition, then replace it with your own key. Microsoft lists these generic keys on its KMS client activation keys page; they change the edition but don’t activate anything on their own.
DISM /online /Set-Edition:ServerStandard /ProductKey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /AcceptEulaThat’s Microsoft’s generic key for Windows Server 2022 Standard; for Datacenter use WX4NM-KYWYW-QJJR4-XV3QB-6VM33. Restart, then install and activate your own key:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /atoFix 2: Use a Key That Matches Standard or Datacenter
If DISM shows a full edition (ServerStandard or ServerDatacenter) and you still get 0xC004F069, the key is for the other edition. The key must match exactly:
- Standard key on Standard, or Datacenter key on Datacenter: works.
- Datacenter key on Standard: convert the edition first (below), then activate.
- Standard key on Datacenter: won’t work. Downgrading Datacenter to Standard requires a clean reinstall, so use a Datacenter key or reinstall Standard.
Upgrade Standard to Datacenter with DISM
A full Standard installation can be upgraded to Datacenter in place, using your Datacenter key:
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaRestart when prompted, then run slmgr /ato. Not sure which edition you need? Our guide to Windows Server 2025 Standard vs Datacenter explains the licensing differences, which are the same for 2022.
Fix 3: Install and Activate Your Key With slmgr
Once the edition matches your key, install and activate it from an administrator Command Prompt:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato/ipkinstalls your product key, replacing any existing one./atoactivates it online with Microsoft./dlvshows detailed licence information, including the edition and channel (Retail, OEM or Volume)./upkuninstalls the current key if you need to start again.
Each command opens a Windows Script Host window with the result. Wait a few seconds for it to appear before running the next command.
Fix 4: Activate by Phone
If the edition is correct but online activation fails, for example because the server has no internet access or the key has reached its online activation limit, activate by phone:
slui 4. On Server Core, use slmgr /dti to show the Installation ID instead.slmgr /atp CONFIRMATIONID on Server Core.Fix 5: Activating Windows Server 2022 Virtual Machines
Virtual machines hit 0xC004F069 for the same reasons as physical servers: usually an evaluation guest. Two extra points apply:
- Check the guest edition first. Many VM templates and lab images use the evaluation ISO. Run
DISM /online /Get-CurrentEditioninside the VM and convert it if needed (Fix 1). - AVMA keys only work on Datacenter hosts. Automatic Virtual Machine Activation lets guests activate against an activated Windows Server Datacenter Hyper-V host. On a Standard host, VMware or a cloud platform, an AVMA key fails; use a regular key instead.
- Licensing still applies. Each Windows Server VM must be covered by a licence on the host, whatever activation method you use.
Fix 6: If the Server Is a Domain Controller
Microsoft states that a domain controller running an evaluation edition can’t be converted to a full edition in place. If DISM refuses to convert a domain controller, you have two safe options:
How to Confirm Windows Server Is Activated
After converting and activating, check the result:
slmgr /xprThe machine is permanently activated.
slmgr /xpr.You can also open Settings › System › Activation, which should say Windows is activated, or run slmgr /dlv for full licence details.
/Set-Edition:ServerStandard (Fix 1).ServerDatacenter with a Datacenter key (Fix 1).slmgr /ipk (Fix 1).slui 4 (Fix 4).Related Windows Server Activation Errors
If you see 0xC004F074 after converting with a generic key, that just means the generic key is still installed: run slmgr /ipk with your own key. For “key already used” errors, see our guide to “This product key has already been used”.
Should You Still Install Windows Server 2022?
Windows Server 2022 left mainstream support on 13 October 2026 and receives security updates until 14 October 2031. It’s still a solid choice for existing estates, but for a new server, Windows Server 2025 gives you support until 2034. The activation steps in this guide work the same way on 2025; only the edition names stay the same (ServerStandard, ServerDatacenter). Our Windows Server 2025 Standard vs Datacenter guide covers which edition to choose.
How to Avoid Error 0xC004F069
- Install from full media, not the evaluation ISO, if you already have a licence.
- Check the edition before entering a key with
DISM /online /Get-CurrentEdition. - Buy the edition you install: a Standard key for Standard, a Datacenter key for Datacenter.
- Convert evaluation servers early, before promoting them to domain controllers.
- Keep your key and order details with the server’s documentation for future reinstalls.
Need a Windows Server Licence?
If you’re running an evaluation server and need a full licence, Noxkeys delivers genuine Windows Server keys instantly by email, with activation instructions. Licensing a large multi-core server or several VMs? Contact us before ordering and we’ll help you work out the right quantity.
Also available: Windows Server 2025 Datacenter. Browse all Windows Server licences, read our FAQ, or contact support with a screenshot of your DISM output if you get stuck. Checking a Windows client licence instead? See how to check if your Windows key is OEM or Retail.
Frequently Asked Questions
What does error 0xC004F069 mean?
It means the Software Licensing Service couldn’t find a product SKU matching the key you entered. The key doesn’t match the installed edition, most often because Windows Server is running the evaluation edition.
How do I fix 0xC004F069 on Windows Server 2022?
Check the edition with DISM /online /Get-CurrentEdition. If it ends in Eval, run DISM /online /Set-Edition:ServerStandard /ProductKey:your key /AcceptEula (or ServerDatacenter), restart, then run slmgr /ato.
Can I activate Windows Server evaluation with a product key?
Not directly. slmgr /ipk fails on evaluation editions with error 0xC004F069. Convert the edition with DISM first, which installs your key at the same time.
Can I convert Datacenter evaluation to Standard?
No. Datacenter evaluation can only be converted to full Datacenter. To use a Standard key, reinstall with Windows Server Standard.
Can a domain controller be converted from evaluation?
Microsoft states that a domain controller running evaluation can’t be converted in place. Demote it first (after confirming another domain controller exists), convert it, then promote it again, or build a new server.
Why does DISM reject my product key?
Some volume and retail keys aren’t accepted by DISM /Set-Edition. Convert with Microsoft’s generic KMS client key for your edition, restart, then install your own key with slmgr /ipk and activate with slmgr /ato.
Will converting from evaluation delete my data?
No. The conversion keeps your roles, settings and data, but it can’t be reversed. Back up the server or take a VM checkpoint first.
How long does the conversion take?
Usually 10 to 20 minutes, plus one or two restarts. The progress can sit at 10% for a while; don’t close the window.
Does this fix work on Windows Server 2019 and 2025?
Yes. The same DISM commands and edition names (ServerStandard, ServerDatacenter) work on Windows Server 2019, 2022 and 2025. Use a key for the version you’re running.
Is 0xC004F069 caused by a bad key?
Rarely. A bad or used key gives other errors, such as 0xC004F050 or 0xC004C008. 0xC004F069 almost always means the installed edition doesn’t match the key.