Getting error 0xC004F074 when activating against KMS server

Getting error 0xC004F074 when activating against KMS server

  • Comments 51
  • Likes


This error code is a very generic output to a KMS client having problems activating. To view your output, run slmgr.vbs –ato

When troubleshooting this problem, we checked the following details – if any were a problem, they would generate this error code:

  • DNS record not published at _VLMCS._tcp.client.domain. This must be an SRV record, which the KMS server will automatically register. If you have disabled this, you will need to use a GPO on the clients to point them to the correct KMS server to use
  • No network connectivity from the KMS client to the MS server on the KMS port (tcp/1688 by default). Install telnet on the client and run telnet KMS.Server.Name 1688 and make sure the screen goes blank
  • Not more than 4 hours time difference between KMS server and client. Check that your time zones are correct. If using server core, run timedate.cpl
  • No major hardware changes to the KMS server. If the KMS server is a VM and you have added a number of new devices, CPUs, memory etc, or P2Ved you will need to reactivate your KMS license
  • The KMS service must have the keys to issue for the KMS client requesting a license. For example, if the KMS server is Windows Server 2008 and you are trying to activate Windows 7, you will need an update installed on the KMS server AND the correct KMS key for Windows 7.

And the last one was the problem we hit: Our KMS server was Windows Server 2008 R2, just as the KMS clients. We’d crossed the threshold of 5 servers. But they still would not activate. The problem was that there are different license “channels” for Windows Server. They are described here:

Our servers which were having problems activating were all Windows Server 2008 R2 Datacenter Edition, and we had a “B Channel” KMS license installed on the KMS server.

We followed these steps on the KMS server to install the correct channel license:

  1. slmgr -upk
  2. slmgr -cpky
  3. slmgr -ipk <KMS Host Product Key - channel C>
  4. slmgr -ato

After doing the above, we ran slmgr -ato on the Windows Server 2008 R2 Datacenter Edition servers. Note that “Channel C” is able to active all lower level channels.

  • Thank you for your information!!!


    I could solve a issue using your information!!!!

    Fabio, Brazil.

  • Hai i got syntax error

  • @vikky : can you paste the entire text of your command prompt window here so I can see where the error is. Thanks.

  • nice.. worked for me too

  • How do you open the command for KMS server? Is it in Command Prompt?

    More detailed steps for amateur users please

  • @David: The command slmgr is a vbs script located at C:\windows\system32

    You can simply run the commands above, or if you'd like the output to the screen (instead of pop-ups), then open a command prompt (as administrator if needed) and change to c:\windows\system32 then run:

    cscript.exe slmgr.vbs with the switches stated above.

  • Hi David,

    I'm having the same issue with Windows 8, and I was wondering if you could help me in any way at all? I have tried every available solution online, such as putting my Product Key through slmgr.vbs /ipk and Slui 3 and resetting the KMS timezone and fixing corrupted files on my computer, but to no avail.

    Any help would be appreciated, I'm all out of options.

    Thank you!

  • Hi Craig* I mean, I'm really sorry, I read the wrong name!

  • @Brendan. Sorry, you'd need to get support through your normal channel as this needs troubleshooting beyond what a blog comments section can provide.

  • hie Craig how do activate my windows 8 pro using slmgr.vbs/ato to activate and update KMS client information

  • @Tatenda: Windows 8 Pro can be installed in one of 2 ways: Retail or Volume License. Retail means OEM or via a box you buy from a shop. This is not compatible with KMS. You need to install Windows 8 Pro using Volume Licensing ISO file you download from your Volume Licensing website subscription. This will come with a well-know key in to instructing it to look for a KMS server. You can see these keys here:
    You can also use your MAK keys from your VL website subscription to active these.
    The only supported way to go from a Retail version to a VL version is to reinstall Windows.

  • thanks a lot . . . it wiped my cd key and i don't even have that anymore

  • @Jim: Not sure what you mean. It sounds like you ran these commands on a retail version of Windows? This instruction was clearly intended for the KMS server.

  • what helped for me was the clock issue.
    in case the machine is in workgroup there's no sync to NTP server, so syncing the clock helped.
    any recommendation how to sync machines which are part of groups with the clock?

  • @Even: I'm not 100% sure what you are asking. But to sync a clock you run this command: w32tm /resync [/computer:] /nowait
    Where the /computername field is optional and means the computer whose clock should be synchronised using the existing settings defined on that computer. If you leave out this field, it means to sync the clock of the local machine. Domain joined machines automatically sync their clocks using the AD domain hierarchy to discover the closest DC.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment