Windows Server 2019: Activation fails on a freshly installed server!

Running build 1809 of Windows Server 2019, the server still have activation issues, IF you did not specify the product key, during installation.

If you use the GUI, it will fail, no matter what, stating that it cannot reach the company licensing activation server (KMS), but hey, I did not ever specify a KMS key, I have a MAK πŸ˜‰

The solution is to use the old SLMGR.VBS script, this works..luckily πŸ˜‰

Just open a command prompt and type:

“cscript c:\windows\system32\slmgr.vbs /ipk <product-key>”

πŸ™‚

39 Comments

  1. Mark Tillman

    I had been hitting my head against a wall for a time with this activation. Found your tip and it worked immediately. Thank you!

    Reply
    1. Martin (Post author)

      Thanks for writing back πŸ˜‰

      Reply
  2. Nico

    you saved my day !!!

    Reply
    1. Martin (Post author)

      Glad to hear that πŸ˜‰

      Reply
  3. Julio

    it works, Thanks !!

    Reply
    1. Martin (Post author)

      Glad to hear πŸ˜‰

      Reply
  4. Mark

    Well… i have a windows server 2019 and with this method of activate mine doesn’t work…. any ideas on how to have it fixed.

    Reply
    1. Martin (Post author)

      Are you using correct key (standard / datacenter) Do you run commands as admin in command prompt? πŸ™‚

      Reply
  5. Jim Soya

    Thanks so much!!! I don’t why Microsoft couldn’t post this on the VLSC site when you download open license key???

    Reply
  6. Alexander Jernejcic

    Thank you! MS Support could not provide a solution…

    Reply
  7. Steve Oke

    Thank you so much, I have been looking for a fix for hours!

    Reply
  8. JuanChoRois

    Amazing.. out of the box I got that error and I get errors joining this 2019 to my domain as well. I guess there will never be a bug free Server edition from Windows.

    Reply
  9. Alfonso Irizarry

    mine install succesfully but doesnt activate. any ideas?

    Reply
    1. Martin (Post author)

      You installed the server successfully?

      You have to run the commands for successfull activation, and of course, have a license key?

      πŸ™‚

      Reply
  10. Gersom Hideo Otsu

    Very Good….save my job!

    Reply
  11. Courtney

    This completes successfully but does not result in activation.

    Reply
    1. Martin (Post author)

      Just refresh, it will work πŸ™‚

      Reply
    2. Martin (Post author)

      Try to close and open the window, often the GUI does not update accordingly πŸ™‚

      Reply
  12. J. M. De Moor

    Just another thank you. I did an in-place upgrade from 2012 R2 to 2019. This little VBS script was the ticket.

    Reply
    1. Martin (Post author)

      Thanks πŸ™‚

      Reply
  13. James N

    I did an in-place upgrade from 2012r2 to 2019 std… ran the cscript and it says it activated but it does not work still… I have ran updates but still nothing… rebooted… tried the trouble shoot and it give and this error “something interrupted our trouble shooting… make sure you are connected to the internet (0xd0020017).
    I have an internet connection… so firewall is open at the moment. so I am stuck.

    Reply
    1. Martin (Post author)

      Hi James,
      Are you using latest ISO?
      Also I read somewhere that you can try to type in the code, when you install windows, and not after.

      have you typed in the commands in a command prompt in admin-mode?

      regards
      Martin

      Reply
  14. Rivod

    Hi, I tried this and failed. It says;

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

    slui.exe says;
    The Software Licensing Service reported that the product SKU is not found.

    Also I have same problem with James N (We can’t reach activation servers right now. Make sure you’re connected to the Internet . ..)

    Reply
  15. Pradeep Garg

    Hi,
    I am having same activation issue, and after running command I am getting below error.

    Error: 0xC004F075 The Software Licensing Service reported that the operation cannot be completed because the service is stopping

    Any help ??

    Thanks

    Reply
    1. Pradeep Garg

      Note that I installed a fresh copy of Windows server 2019 Essential.

      Reply
    2. Martin (Post author)

      Hi Pradeep, have you installed the KMS version af Windows and nok the MAK?

      Reply
  16. chris Kendrick

    Worked like a treat for me…Thanks a million

    Reply
    1. Martin (Post author)

      Glad to hear that – thanks πŸ™‚

      Reply
  17. Paul O'Rorke

    Martin, you are my new hero!

    not only did your suggestion work, it wasn’t buried in a wall of unnecessary fluff!

    I’d buy you a beer if you were here!

    Reply
    1. Martin (Post author)

      Hi Paul, glad to hear, anyways πŸ™‚

      Reply
  18. Ron

    Brilliant! I had this issue, and none of the microsoft solutions worked… this fixed it!

    Reply
    1. Martin (Post author)

      Thanks πŸ™‚

      Reply
  19. Eric

    Saved my day!

    Reply
    1. Martin (Post author)

      Glad to hear πŸ™‚

      Regards Martin

      Reply
  20. chet zurawski

    On a new server with a new Server 2019 I mistakenly installed and activated the Standard version not the datacenter desktop version of Server 2019. So I wiped it out and reinstalled the datacenter version but now it will not activate. Can I do anything?

    Reply
    1. Martin (Post author)

      They key you are using, is it KMS or MAK maybe?

      Reply
  21. Manoj Kumar

    THanks you sharing.

    Reply
    1. Martin (Post author)

      Thanks πŸ™‚

      Reply
  22. Sudo

    This worked. So frustrating. I tried calling into MS for activation and the robot said to go to help.microsoft.com and pay for support….. to activate windows. Then the call just disconnects.

    This worked a treat. Thanks

    Reply

Leave a Reply to Martin Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close