0xC004F069: Product SKU Not Found When Stepping Up to Enterprise

Fix it now

Microsoft publishes 0xC004F069 as SL_E_MISMATCHED_PRODUCT_SKU, “The product SKU is not found.” The key you have names an edition this installation has no description for, so there is nothing for it to attach to. Find out what the installation can become before you try another key.

slmgr /dli
DISM /Online /Get-TargetEditions
slmgr /rilc

1. Read the slmgr /dli description and compare it with winver. That tells you what edition is installed and what channel it is licensed on.
2. Read the target editions list. If the edition you want is not in it, the image does not carry it and no key will make it appear.
3. slmgr /rilc reinstalls the licence files from the known-good copies at %SystemRoot%\system32\oem and %SystemRoot%\System32\spp\tokens. Restart the licensing service with net stop sppsvc then net start sppsvc afterwards, and re-run the target editions check.
4. On Windows client, apply the step-up as a product key: Settings, System, Activation, Change product key, or slmgr /ipk <key> followed by slmgr /ato.
5. On Windows Server, the documented online route is DISM /Online /Set-Edition:<edition> /AcceptEula /ProductKey:<key>.

Install the intended key over the top with slmgr /ipk rather than removing the old one first. Microsoft’s own licensing repair guidance says not to use /upk, and /ipk replaces an existing key anyway.

If that fixed it you can stop here. If not, the next section explains what decides which editions an installation can become, and which of the six codes here are actually published.

Why it happens

Windows does not work out what edition it is from the key. Every edition the installation is capable of being is described by a licence file in the licensing store, and the key selects among the descriptions that are present. A step-up matches the key to the target edition’s description and applies it over the base. 0xC004F069 is that match failing because the description is not there, which is exactly what Microsoft’s published text says: the product SKU is not found.

That is the only code in this record Microsoft publishes. The other five – 0xC004F055, 0xC004E01A, 0xC004E026, 0xC004E02A and 0xC004E02D – have no meaning on learn.microsoft.com or support.microsoft.com, and the descriptions attached to them in earlier versions of this article were guesses that happened to fit the story. They are kept here because you may see them, but treat them as identifiers to quote in a support case rather than as diagnoses. Your machine will print Microsoft’s own text for any of them if you run slui.exe 0x2a followed by the code.

There are three ordinary ways to arrive at a missing SKU description. An in-place upgrade or an interrupted feature update can leave the store half rewritten. A trimmed or repackaged image may have had edition licence files stripped during customisation. And media that simply does not carry the target edition – a single-edition OEM image, or an LTSC build – will never list it as a target however healthy the store is.

One correction worth having before you start typing commands. DISM /Online /Set-Edition is documented as the way to change an online Windows Server operating system to a higher edition, using /AcceptEula and /ProductKey. It is not the documented route for a Windows client step-up. On a Windows client the supported move is a product key or a subscription entitlement, and reaching for DISM there is how people end up with a machine in a state nobody planned for.

Full reference

Which of these codes are actually published

The commands that matter, and what they really do

Edition change is one-way. Microsoft’s documentation states that you cannot set a Windows image to a lower edition, and that the lowest edition does not appear in the /Get-TargetEditions output. It also advises against using /Set-Edition on an image that has already been changed to a higher edition. Decide before you run it, take a full backup on anything you cannot afford to rebuild, and be certain you hold the entitlement for the target.

Reading the target editions list properly

1. Run DISM /Online /Get-TargetEditions from an elevated prompt.
2. An empty or unexpectedly short list on a general-purpose image points at the licence store, so run slmgr /rilc and repair the component store before concluding anything.
3. A list that matches the media you used, and simply lacks your target, points at the media. No key changes that.
4. A list containing your target, with the step-up still failing, points at the key or the entitlement rather than the image.

When the store itself needs rebuilding

Microsoft publishes a tokens.dat rebuild for licensing store damage: stop the Software Protection service, rename tokens.dat under %windir%\system32\spp\store\2.0, start the service, run slmgr /rilc, restart twice, then install the product key with slmgr /ipk. The same page is explicit that you should never use the /upk switch to uninstall a product key, and should install over the existing one instead. That is worth carrying into every licensing repair, not just this one – it is the difference between a machine that keeps working while you fix it and a machine that is unlicensed until you find the key.

If the step-up is meant to come from a subscription

A device that is supposed to reach Enterprise through subscription activation should never have an Enterprise key typed into it. Typing one creates a second licensing state that competes with the entitlement and makes the eventual diagnosis harder. Confirm the user holds an assigned seat, confirm the device is Microsoft Entra joined or hybrid joined, confirm the base edition is Pro, and let the mechanism do its work.

Every code this article covers

Confirm the fix worked

1. winver shows the edition you intended.
2. slmgr /dlv reports a licence status of Licensed for that edition, on the channel you expect.
3. DISM /Online /Get-TargetEditions reflects the new base rather than the old one.
4. Reboot and confirm both the edition and the activation state survive the restart.
5. On a subscription device, Settings, System, Activation reports activation through the subscription rather than through a key.

Questions people ask about this