0xC004F050 error code

Verify the installed Windows Server 2025 edition and licensing channel, then install a key that matches both; error 0xC004F050 means the Software Protection Service considers the submitted key invalid for the current installation or activation method.^1^

1. Identify the installed edition and channel

Open Command Prompt as administrator and run:

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

Check for:

• ServerStandard, ServerDatacenter, or their Eval variants.
• EVAL in the detailed license output.
• Whether the channel is Retail, MAK, or KMS client.

slmgr.vbs /dlv displays detailed activation information, while DISM identifies whether the installed edition is an evaluation edition.^2^^3^

2. If the edition includes Eval

An evaluation installation must be converted to an available retail edition before switching to another licensing channel.

First, list supported targets:

DISM /online /Get-TargetEditions

Use only an edition returned by that command. Then convert it with the corresponding valid product key:

DISM /online /Set-Edition:ServerStandard /ProductKey:<25-character-key> /AcceptEula

For Datacenter, use:

DISM /online /Set-Edition:ServerDatacenter /ProductKey:<25-character-key> /AcceptEula

Restart the server when prompted, then activate:

slmgr.vbs /ato
slmgr.vbs /dlv

If the required edition is not listed by /Get-TargetEditions, Microsoft requires a fresh installation of that edition. An evaluation domain controller also cannot be converted directly; migrate AD DS and FSMO roles to a retail installation first.^3^

3. If it is already a non-evaluation installation

Confirm that the purchased key matches the installed edition:

• A Standard key must be used with Server 2025 Standard.
• A Datacenter key must be used with Server 2025 Datacenter.
• A Retail, MAK, OEM, KMS host key, and KMS client key serve different activation roles.

Install the matching key and request activation:

slmgr.vbs /ipk <25-character-key>
slmgr.vbs /ato
slmgr.vbs /dlv

/ipk checks whether the key is valid and applicable to the installed operating system; an inapplicable key returns an error. Run it from an elevated Command Prompt.^4^

If the installed edition itself is wrong, Standard can be converted to Datacenter when /Get-TargetEditions lists ServerDatacenter:

DISM /online /Set-Edition:ServerDatacenter /ProductKey:<datacenter-key> /AcceptEula

The reverse conversion from Datacenter to Standard is not listed as a supported conversion path; reinstall Standard if that is the licensed target.^3^

4. If using KMS

Install the Windows Server 2025 Generic Volume License Key matching the edition:

• Standard: TVRH6-WHNXV-R9WG3-9XRFY-MY832
• Datacenter: D764K-2NDRG-47T6Q-P8T8W-YP6DF
• Datacenter: Azure Edition: XGN3F-F394H-FD2MY-PP6FD-8MCRC

These are KMS client keys, not purchased MAK or retail keys.^5^

slmgr.vbs /ipk <matching-kms-client-key>
slmgr.vbs /ato
slmgr.vbs /dlv

The KMS host must have a Windows Server 2025 CSVLK and the updates required to support newer clients. Microsoft documents that this CSVLK can be hosted on Windows Server 2025, 2022, or 2019; KMS normally uses TCP port 1688.^6^

If a matching, authorized key still produces 0xC004F050, provide the /dlv output—excluding the full product key—to the volume-license provider or Microsoft Support so they can verify the key type and entitlement.

References

1. Troubleshoot Windows activation error codes
2. Monitor activation
3. Convert Windows Server editions and license types
4. Slmgr.vbs options for obtaining volume activation information
5. KMS client activation and product keys
6. Key Management Services (KMS) activation planning