Resolve Error 0xC004F069 on Windows Server 2019 Standard License Activation

3 minutes read

How do you resolve error 0xC004F069 on Windows Server 2019 Standard License Activation? You may have installed an evaluation copy of Windows Server 2019 Standard and after attempting to input your purchased Windows License Keys, you get error 0xC004F069.

Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC004F069’ to display the error text.

The actual error text is:

The Software Licensing Service reported that the product SKU is not found

Don’t panic. In this article, I will show you how to resolve the error without reinstalling Windows.

Solution to resolve error 0xC004F069 on Windows Server 2019

To resolve the error 0xC004F069 on Windows Server 2019 Standard, start by converting from Evaluation to Standard by running your original DISM command with the relevant GVLK key and not the new one you purchased.

Step #1

Follow the link to GVLK to get the GVLK Keys for Windows Server 2019 Standard.

Step #2

Run Windows PowerShell as an Administrator.

Go to Start Menu>Search for Windows PowerShell>Right click on it and “Run as administrator”

Step #3

Remove the existing key by running the command below on Windows PowerShell.

slmgr /upk

Step #4

Enter the command below to set the GVLK Key.

DISM /online /set-edition:serverstandard /productkey:GVLKkey /accepteula

Replace the GVLK with the Windows Server 2019 Standard Key you found in Step #1 above eg

DISM /online /set-edition:serverstandard /productkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /accepteula

Replace XXXX with your GVLK Keys.

You will receive a notification of successful application of the keys.

Step #5

Run the command below to replace the GVLK with your purchased license key.

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Replace XXXX with your purchased Windows Server 2019 Standard License Keys.

Step #6

Run the command below to activate Windows.

slmgr /ato

By following the steps above, you will be successful in your quest to resolve error 0xC004F069 on Windows Server 2019 Standard. It will apply your purchased license keys and activate Windows.

Software Licensing Management Tool (slmgr) PowerShell Commands

As you work to resolve error 0xC004F069 on Windows Server 2019 Standard License Activation, here are slmgr parameters you can use on PowerShell to make changes or get more information about your installation:

/dli (Shows license and activation information.)
/dlv (Shows detailed license and activation information.)
/xpr (Shows the expiration date of the license installed. It is useful when using a KMS key with a local KMS activation server on the network.)
/upk (Uninstalls the current license key. Be cautious when using it.)
/cpky (Removes license key information from the registry to prevent it from being stolen by malicious code. Be cautious when using it.)
/ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (Changes the license key to the entered one. Replace XXXXX with your license key.)
/ato (Attempts an online activation.)

Note that you should run Windows PowerShell as an administrator.

Deployment Image Servicing and Management (DISM)

The Deployment Image Servicing and Management Tool (DISM) is command-line executable tool available in Windows that repairs Windows image or modifies Windows installation media. It helps to resolve issues in the installed Windows Operating System.
We used the tool above to resolve error 0xC004F069 on Windows Server 2019 Standard by setting the Windows edition as per the supplied Product Keys.
Another example of use is to get the current edition of the installed Windows OS as shown below.
Command:

PS C:\Users\administrator> DISM /online /get-currentedition

Output:

Deployment Image Servicing and Management toolVersion: 10.0.17763.1697
Image Version: 10.0.17763.2452
Current edition is:
Current Edition : ServerStandardEval
The operation completed successfully.

PS C:\Users\administrator>

The tool is also used to mount Windows images in .wim, .vhd, and .vhdx format.

 

Share your Windows activation experience in the comments section below. If you need any help, get in touch using our contact page.