Share via

error code 0xc004c008

eric perez 0 Reputation points
2026-04-23T13:14:41.5666667+00:00

I tried issuing a KMS key for one of my customers but he keeps getting an error code 0xc004c008. Is it there a way I can fix what ever issue is causing It with your help?

Windows for business | Windows Server | Devices and deployment | Licensing and activation
0 comments No comments

1 answer

Sort by: Most helpful
  1. Brian Huynh 2,880 Reputation points Microsoft External Staff Moderator
    2026-04-24T02:16:32.8033333+00:00

    Hello eric perez, thank you for posting in the Microsoft Q&A community. I understand your customer is encountering error code 0xC004C008 when attempting to activate a machine using a KMS key.

    Error 0xC004C008 translates to "The activation server reported that the product key has exceeded its unlock limit." When dealing with Volume Licensing and KMS keys, this typically happens for a few specific reasons:

    1. The KMS Host Key (CSVLK) has genuinely exceeded its activation limit. Microsoft usually limits KMS Host keys to 6 activations on different host servers to prevent abuse.
    2. The customer is mistakenly applying the KMS Host Key (CSVLK) to an end-client machine instead of using a KMS Client Setup Key (GVLK).
    3. The key is actually a Multiple Activation Key (MAK) that has depleted its available activation count.

    If your customer is setting up a dedicated centralized KMS host server and has hit the installation limit for the CSVLK, they will need to contact Microsoft Volume Licensing Service Center (VLSC) Support to request an activation limit increase for that specific product key. 

    Alternatively, if the customer is just trying to activate a standard Windows client or server OS to authenticate against an already existing KMS host on their network, they should not enter the KMS Host Key you issued. Instead, they must install the generic KMS Client Setup Key (GVLK) applicable to their specific OS version. They can do this by running the following from an elevated Command Prompt:

    slmgr.vbs /ipk <Insert-Applicable-GVLK-Here>
    slmgr.vbs /skms <Insert-KMS-Server-IP-or-FQDN>
    slmgr.vbs /ato
    
    

    To pinpoint the exact cause and give you the best path forward, could you please have the customer run the following command on the affected machine from an elevated Command Prompt and share the output with us?

    slmgr.vbs /dlv
    

    Note: Please ensure no sensitive personal data is included in the screenshot.

    I will follow up on this thread to ensure your VMs are upgraded successfully. If the guidance provided helped you navigate to this solution, please consider clicking 'Accept answer'. This officially marks the thread as answered and greatly helps other community members who are searching for a solution to this exact same problem.

    Official Microsoft References:

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.