when im traying to activate my windows server STD 2022 im getting Error: 1605

YOUSUF Khalifa 0 Reputation points
2026-10-17T11:42:15.35+00:00

Hi

im using

DISM /Online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

Version: 10.0.20348.2849

Image Version: 10.0.20348.5622

Error: 1605

The specified product key is not valid for the target edition.

Run this command again with a product key that is correct for the target edition.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Error 0C004E016 on a computer running Microsoft Windows non-core edition, run Slui.exe 02a 0*C004E016 to display the error

my product key starting with PYXFW

Windows for business | Windows Server | Devices and deployment | Licensing and activation

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 2,540 Reputation points Microsoft External Staff Moderator
    2026-10-19T06:14:41.6333333+00:00

    Welcome to Microsoft Q&A!

    Thank you for providing the additional information.

    Based on your description, the key point is that you are trying to activate Windows Server 2022 Standard using a Windows Server 2025 Standard product key.

    While licensing rights and product activation are related, they are not necessarily the same thing. The activation method and product key must be appropriate for the Windows Server version, edition, and licensing channel installed on the server.

    For example, Microsoft publishes different KMS client keys for Windows Server 2025 Standard and Windows Server 2022 Standard.

    The errors you are seeing indicate that the supplied product key is not being accepted for the installed or target product:

    • DISM error 1605: "The specified product key is not valid for the target edition."
    • 0xC004E016 when attempting to install the key.

    As a first step, I recommend confirming exactly which edition and license type is currently installed. The following commands can check the current edition and whether the installation is an Evaluation edition:

    DISM /online /Get-CurrentEdition

    You can also run:

    slmgr.vbs /dlv

    If the server is already running the non-evaluation Windows Server 2022 Standard edition, you should not need to run /Set-Edition:ServerStandard because there is no edition conversion to perform.

    slmgr.vbs /ipk for switching between retail, volume-licensed, and OEM licensing while keeping the same Standard or Datacenter edition.

    In this situation, I recommend confirming that you have the appropriate Windows Server 2022 Standard key or activation method for your licensing channel.

    For volume licensing, volume licensing keys can be obtained through the Product Keys section for the applicable licensing agreement or through the Microsoft Activation Center.

    • If this is an OEM license: I would recommend checking with the server manufacturer or OEM that supplied the license regarding the applicable downgrade and activation options.
    • If you have already confirmed that you are using the appropriate Windows Server 2022 key and it is still being rejected: The next step would be to contact your license provider or the Microsoft Licensing Activation Center. They can validate the specific product key and licensing channel. It is a recommendation to contact the Activation Center when a MAK cannot be validated.

    I would also avoid relying on the PYXFW prefix alone to determine whether the key is appropriate for Windows Server 2022 Standard. The complete key and its associated licensing agreement/channel would need to be verified by the appropriate licensing provider.

    References:

    Downgrade Rights Licensing Guidance

    Convert Windows Server editions and license types | Microsoft Learn

    Troubleshoot Windows activation error codes - Windows Server | Microsoft Learn

    Key Management Services (KMS) client activation and product keys | Microsoft Learn

    Plan for volume activation | Microsoft Learn

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-17T11:43:57.6933333+00:00

    The two errors indicate that the supplied key does not match the currently installed edition, version, or licensing channel, so check the exact edition and supported target before attempting activation again.^1^

    1. Identify the installed edition and valid target

    Open Command Prompt as Administrator and run:

    DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
slmgr.vbs /dlv

    Check these fields:

    • DISM /Get-CurrentEdition: whether the edition is ServerStandard, ServerStandardEval, ServerDatacenter, or another edition.
    • DISM /Get-TargetEditions: whether ServerStandard is actually listed.
    • slmgr.vbs /dlv: the edition description, whether EVAL appears, and the current product-key channel.

    /Get-TargetEditions is authoritative for the available conversion paths. If ServerStandard is not listed, do not repeat the failing /Set-Edition:ServerStandard command.^2^

    2. Apply the matching branch

    If the current edition is ServerStandardEval

    First take and verify a backup of the server’s data and configuration, and ensure that a rollback or recovery plan is available. Edition conversion requires a restart.

    If ServerStandard appears under /Get-TargetEditions, use a genuine Windows Server 2022 Standard retail, MAK, or qualifying OEM key:

    DISM /online /Set-Edition:ServerStandard ^
 /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

    Restart when prompted, then check activation:

    slmgr.vbs /ato
slmgr.vbs /dlv

    There is an important Core installation restriction: Standard Core Evaluation cannot be converted to retail Standard Core. If ServerStandard is absent from the target list, a fresh installation of the required non-evaluation edition is necessary.^2^

    If this server is an Active Directory domain controller, Microsoft does not support converting an evaluation domain controller directly. Deploy another retail-licensed domain controller, verify replication, DNS and Global Catalog coverage, transfer the FSMO roles, and confirm a tested system-state backup before demoting the evaluation server.^2^

    If the current edition is already ServerStandard

    Do not use /Set-Edition; no edition conversion is needed. The failure from slmgr /ipk means the key still does not match the installed release/edition/channel or is otherwise unsuitable.

    Verify the key through the organization or vendor that supplied it. The prefix PYXFW alone is insufficient to establish that it is a Windows Server 2022 Standard retail, OEM, MAK, KMS-host, or KMS-client key. For volume licensing, obtain the assigned key from the Product Keys section for the applicable volume licensing agreement, or contact the Microsoft Activation Center.^3^

    After obtaining a confirmed matching key:

    slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr.vbs /ato
slmgr.vbs /dlv

    The expected result is “Installed product key successfully”, followed by License Status: Licensed.

    If the current edition is Datacenter

    A Server Standard key cannot activate Datacenter, and evaluation Datacenter cannot be converted to Standard. Use a matching Server 2022 Datacenter key or perform a fresh installation of Server 2022 Standard.^2^

    A fresh installation can erase applications, configuration, roles, and data. Create and verify a complete backup and recovery plan before proceeding.

    If this server should activate through KMS

    Only use this branch if the organization has a functioning KMS host. After the system is a non-evaluation Server 2022 Standard installation, install Microsoft’s Server 2022 Standard GVLK and activate:

    slmgr.vbs /ipk VDYBN-27WPP-V4HQT-9VMD4-VMK7H
slmgr.vbs /ato
slmgr.vbs /dlv

    That GVLK does not provide a license and cannot convert an Evaluation installation. It works only with a valid KMS host or Active Directory-based activation; it cannot activate directly against Microsoft as a retail key.^4^

    If a confirmed matching MAK/OEM/retail key is still rejected after the edition is non-evaluation and correct, contact the key supplier or Microsoft Activation Center for key validation rather than repairing the licensing store or reinstalling immediately.

    References

    1. Troubleshoot Windows activation error codes - Windows Server
    2. Convert Windows Server editions and license types
    3. Plan for volume activation
    4. KMS client activation and product keys
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.