Windows 8.1 Pro Activation error Error code: 0xC004F074 RRS feed

  • Question

  • Good Afternoon,

    I am unable to activate windows 8.1 pro. I keep getting the error 0xC004F074. I'm doing testing in a corporate environment and am unable to activate using any of the keys I was given. Here is the read out. I need more than a link to KB article which is what a lot of moderators seem to post. 

      <ProductName>Windows 8.1 Pro</ProductName>
      <TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone>
      <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription>
      <OemId>DELL  </OemId>
      <OemTableId>CBX3   </OemTableId>
      <Manufacturer>Dell Inc.</Manufacturer>
      <Model>OptiPlex 990</Model>

    Thursday, March 6, 2014 12:56 AM


All replies

  • this is means Key Management Service cant be connected.

    Try this TS


    try to activate again

    1) Go to start -> run ,then type Slui 3 (Slui 4 for phone activation)

    2) Enter Product key

    3) Click Activate

    Thursday, March 6, 2014 2:02 AM
  • I've personally used this solution (slui 3) to reenter a key when activation wasn't working, but we use MAK, not KMS, so YMMV. I think it may depend on exactly where in the chain things are going wrong.  
    This is an interesting bit from the link britishdhez posted (these are possible causes of this error message): 


    • 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."

    Also, I know you said no KB articles, but for completeness sake (for folks reading this at a later date who may be troubleshooting): 

    When trying to activate you get 0xC004F074 with description "The Key Management Server (KMS) is unavailable" -

    • Edited by AGrush Thursday, March 6, 2014 7:56 AM
    Thursday, March 6, 2014 7:53 AM
  • Your diag output suggests that you have the Pro edition, VL channel, configured with a KMSclient pkey.

    So, do you have a deployed+activated KMShost in your environment?

    Or, are you not wanting to use KMS?

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Thursday, March 6, 2014 8:37 AM