Share via

How to activate windows server 2019 key

Prem Kumar 0 Reputation points
2026-03-10T05:23:33.22+00:00

We have taken windows server 2023 and after that we downgrade to windows server 2019.

During that period my vendor has not shared the ms activation key.

Now I had changed the host name into my server and after that now asking about windows key, and I'm adding my windows key but it's still not activated.

Windows for business | Windows Server | Devices and deployment | Licensing and activation
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Harry Phan 15,915 Reputation points Independent Advisor
    2026-03-10T07:36:32.0266667+00:00

    Hi Kumar, well I'm pretty sure there is no product called Windows Server 2023, so the system was most likely installed with a newer release (for example evaluation or a later build) and then replaced with Windows Server 2019 media. If the server hostname was changed and activation now fails, the most common cause is that the installed edition (for example Standard Evaluation or Datacenter Evaluation) does not match the retail/VLSC key you are entering. Check the current edition with DISM /online /Get-CurrentEdition; if it shows an Evaluation edition, convert it first using DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula. After the edition matches the purchased license, run slmgr /ato to activate. If activation still fails, verify the key type (MAK/KMS/OEM) because OEM keys will only activate on the original hardware they were issued with.

    I hope it's helpful. If it is, please give it a thump up or an accept answer, appreciate it :)

    Harry.

    0 comments No comments

  2. Q&A Assist
    2026-03-10T05:23:50.0966667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Windows Server 2019 must be activated with a valid, matching product key or via a proper volume activation method. A downgraded installation from Windows Server 2022/2023 does not automatically provide a separate 2019 key, and generic or mismatched keys will not activate.

    Based on the description, there are two likely scenarios:

    1. Retail/OEM key scenario
    • If the vendor sold a retail or OEM license and never provided the key, the key must be obtained from the vendor or from the appropriate Microsoft licensing portal/account.
    • Windows cannot be activated with a generic or KMS client key if there is no corresponding licensed KMS host in the environment. KMS client keys (GVLKs) are only for volume licensing and do not work as standalone retail keys.
    1. Volume Licensing / KMS scenario If the environment uses volume licensing (KMS):
    2. Ensure there is a working KMS host
      • A KMS host must be created and activated with a valid KMS host key (CSVLK) for Windows Server.
      • Install the Volume Activation Services role on a supported Windows Server (for example, 2019 or 2022):
             Install-WindowsFeature -Name VolumeActivation -IncludeManagementTools
        
      • Configure the KMS host using the Volume Activation Tools wizard:
        1. Run vmw.exe.
        2. Select Key Management Service (KMS) and point to the server (for example, localhost).
        3. Under Install your KMS host key, enter the organization’s KMS host key and Commit.
        4. Activate the KMS host online or by phone.
    3. Verify KMS host can activate Windows Server 2019
      • The KMS host must be running a supported OS and key combination that can activate Windows Server 2019. For example, a “Volume License for Windows Server 2019” or “Volume License for Windows Server 2022” CSVLK on a supported host OS can activate Windows Server 2019 and earlier versions.
    4. Ensure the 2019 server is a KMS client
      • Volume-licensed editions of Windows Server are KMS clients by default and use a GVLK (KMS client key). If the server was converted to another key type, reapply the correct GVLK from the KMS client key list and then run activation against the KMS host.
    5. Check DNS and connectivity to KMS
      • If activation fails with errors like 0xC004F074 (no KMS could be contacted), verify:
        • The _VLMCS._tcp SRV record in DNS points to the correct KMS host.
        • The host (A) record for the KMS server has the correct IP.
        • TCP port 1688 is open from the client to the KMS host (firewall rule SPPSVC-In-TCP enabled on the host).

    If the current “Windows key” being entered is a KMS client key without a corresponding licensed KMS host, or a key for a different edition/version, activation will continue to fail. In that case, the correct action is:

    • For retail/OEM: obtain the proper Windows Server 2019 product key from the vendor or licensing portal and activate normally.
    • For volume licensing: ensure a valid KMS host key is installed and activated on a KMS host, then let the 2019 server activate as a KMS client.

    If the vendor has not provided any valid key or licensing details, the only supported resolution is to contact the vendor or the appropriate Microsoft licensing/support channel to retrieve the correct license or key; there is no supported workaround using scripts or third‑party KMS servers.


    References:

    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.