Forum Discussion
Greg Black
May 13, 2018Copper Contributor
Windows Server 2019 install product key not working
i Have tried both Standard and Datacenter product keys and get errors with both
Did you install, choose NOT to enter the product key, then after the install was done, try to enter and activate the key? if so, that does not appear to work. I ran into the same issue on 2 of my 2019 servers. I wiped them out and this time entered the key during install, and it successfully activated. if I were to guess, they made something in the install to take into account these testing keys, but the Activation function within Settings, has not been updated to reflect that, so it thinks you are activating a live version of Windows, and that is not a valid key there. That is entirely a guess on my part. I didn't bother running a wireshark or anything to see what kind of response I was getting when trying to activate from Settings.
Just as an FYI, based on the earlier response, the 2 machines I was seeing this issue on, were not upgrades, they were brand new installs on a blank hard drive. I have not gotten around to trying the in-place upgrade yet. I don't know if this will help your situation, but I can say that I saw exactly what you were describing, and if you enter the key during the actual install, it appears to work. I have not looked into the release notes to see if there is something that says Activation from Settings is not set up to work yet.
- sankar725Copper Contributor
https://www.yorkerspot.com/upgrade-windows-server-2019-evaluation-to-standard-full-version/
Our Office use Windows server 2019 ( 180 days ) Standard Evaluation operating system. After trail time will to finish with n weeks. So we purchased windows server Standard key we try to activate but we receive error
( on a computer running Microsoft windows non-core edition run ‘slui.exe 0x2a 0xc004f069 )
After We Upgrade Windows server Standard Evaluation to standard After We try to activate Successfully Activated. You faced this issue kindly follow the below Steps.
- Praveen KumarCopper ContributorI got the same issue and solved using command line
slmgr/ipk <KmsKey>
slmgr /ato
Example:
slmgr/ipk XXXX-XXXX-XXXX-XXXX - Julien LegerCopper Contributor
Greg Black I know this is a little late response, but what worked for me was to open up PowerShell or Command Prompt with admin rights, then entered the following to change the product key and it activated fine:
slmgr /ipk ADD-PRODUCT-KEY-HERE
- RHoutzCopper Contributor
Greg Black Having the same problem
I've called Microsoft 3x now and every time they attempt to transfer me to technical support.
Every time it gets disconnected except the last time we discovered it was because technical support was closed and now they've ask me to call back in 2 hours.
I can't believe this. We've paid almost 250 dollars for a server OS that won't even let us show all the icons in the tray.
And this is more than a year later from when Greg first posted this.
- remus25Copper Contributor
Solution
Find available target editions
DISM.exe /Online /Get-TargetEditions
Change your target editionDISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
Works with:
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019
- KRob527Copper ContributorThis worked after failure of cscript... command with error 0xC004F069
Thanks.
Ditto on the fact that this should definitely not be a problem after sooooo many years of this feature, WOW!
- MarktheThirdCopper Contributor
So far this is the best information I've found on this specific issue. So I wanted to post my update here.
I was able to follow step 6 and use slmgr to activate Windows as of 2-5-19. However, today I am getting a new error from that command line step that is preventing activation.
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F4069' to display the error
slui output: Code:0xC004F069 Description: The Software Licensing Service reported that the product SKU is not found.
I've tried using all of our MAK keys, including the new one that was purchased last week.
- Brentfor
Microsoft
What build are you using? If it is pre-release, they may have all expired.
- Chris JuttingCopper Contributor
Still an issue on a retail purchased license. Come on Microsoft! Cmd line allowed me to activate.
- mutanthostCopper Contributor
So, late to the game, but glad I was. May 13, and many moons later to find that the command line is still king, but the kingdom won't allow the masses to pay/activate their secret boxes so easily? Still waiting on 2019? Maybe in hindsight, 2020 would be an appropriate adoption year;)
- Tamás HavasCopper Contributor
I had Windows Server 2019 Insider Preview Build 17692 installed and activated on my SRV. Just downloaded the Windows Server 2019 Insider Preview Build 17713 ISO - mounted it, end started an update. Everything went good, but now, the OS isnt activated.
Windows activation not working. If i reenter the serial, the activation fails too.
- Dustin MarquessCopper ContributorI have the same exact problem :(
- Brentfor
Microsoft
Hi Folks,
We apologize for the frustration this has been causing. We have several bugs opened and are working through these. Here is a possible solution in the meantime. Since it is difficult to tell exact steps from this thread, here is our repro and workaround. Step #6 is the workaround. Hope this helps.
- Install RS_PRERELEASE 17692 (Standard Full)
- Mount RS5_RELEASE 17713 ISO
- Upgrade 17692 to 17713 (Standard Full)
- After upgrade check two issues that should repro.
- On the desktop there is no watermark for OS is not licensed
- When running from a command prompt, cscript c:\windows\system32\slmgr.vbs /dlv – OS shows as not licensed
- Try to activate from UI: Settings -> Update & Security -> Activation -> Activate
- This will error saying product key is not valid
- From a command prompt use cscript c:\windows\system32\slmgr.vbs /ipk <product_key>
- OS should activate
- Rod GrayCopper ContributorI have the same exact issue, but I have already installed twice now and not so thrilled that I may need to do it a 3rd time. I have ALWAYS installed windows by passing the key during install and just using my 10 Pro key from within settings. THAT has always worked for me on Windows 10 Pro.
So why that same exact thing doesnt work here is just crazy. It does however recognize that it is a Insider Build 17713 and it seems to run great. I just wish it would let me sign into my Microsoft account somewhere or at least let me Activate it using the Standard key that was given to everyone. I can't even find a Feedback Hub to give feedback as it tells me I need to install it. Jeez
Oh well... I should have just dumped Server and used Ubuntu Server, that is soooooooo much easier.
Rod