Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Windows activation error 0xC004F050: "The Software Protection Service reported that the product key is invalid"

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Error 0xC004F050 means Windows rejected the product key that was installed or typed. Microsoft's volume activation page gives the message as "The Software Protection Service reported that the product key is invalid." and names the causes: a typo, or a Beta key used on a generally available version of Windows. It also says to make sure you are installing the correct KMS key on the corresponding version of Windows.

The fix is to read what is installed, find out which of those causes applies, and install the right key with slmgr. Installing a key silently replaces the one already there, and a Multiple Activation Key (MAK) can be activated only a limited number of times, so find the cause before you try more keys.

What the error means

The code sits in Microsoft's "Troubleshoot Windows activation error codes" page, which covers Multiple Activation Key (MAK) and Key Management Service (KMS) volume activation. Its table lists 0xC004F050 against three activation types: MAK, KMS and KMS client. That makes it a key problem on the computer, not a problem reaching a KMS host. Compare 0xC004F074, which is about reaching a KMS host: "No Key Management Service (KMS) could be contacted".

Microsoft's cause line for 0xC004F050 reads: "You can encounter an issue if there was a typo or if you try to use a Beta key on a generally available version of the operating system." The solution reads: "To resolve this issue, make sure you're installing the correct KMS key on the corresponding version of Windows. Make sure you've entered the correct characters and numbers. If you're copying and pasting the key, make sure the Clipboard didn't replace the hyphens with em-dashes."

Microsoft's separate Windows 10 page for the same code is written for Windows 10 itself and gives three reasons: the key "can't be used to activate Windows", activation servers were busy after an upgrade from Windows 7 or Windows 8.1, and a free-upgrade Windows 10 that is not activated after a reinstall. The volume page above is the one written for MAK and KMS keys on servers.

Three kinds of key come up in Microsoft's Slmgr.vbs page. A KMS host key or a MAK makes /ato attempt online activation. A Generic Volume License Key (GVLK) makes /ato attempt a KMS activation. Which kind you hold decides which activation route follows the install, and a key for the wrong Windows version is the situation the 0xC004F050 solution describes.

Microsoft describes the slmgr.vbs /ipk <ProductKey> option as one that "Tries to install a 5×5 product key" and "confirmed valid and applicable to the installed operating system." The page adds that if it is not, an error is returned. So the same check that produced the error runs again each time you install a key.

Likely causes

Cause What you see How to confirm
Typing error in the key 0xC004F050 right after the key is entered Compare the key character by character with the licence record
Pasted key has em-dashes in place of hyphens The key looks correct on screen Paste the key into a plain text editor and look at the separators; Microsoft names this case
Beta key on a released Windows Key came from a pre-release programme Check where the key was issued
KMS key for a different Windows version Key is valid, but not for this version Match the key's product to the installed Windows version
Consumer or client case (Windows 10 page) Error after an upgrade or reinstall Microsoft's Windows 10 page lists these; check licensing history

Prove the cause before changing anything

All of these only read. Run them in a command prompt on the affected computer. Microsoft's Slmgr.vbs page says /dli and /dlv do not need elevated privileges.

Display the licence information for the installed edition:

slmgr.vbs /dli

Display the detailed licence information:

slmgr.vbs /dlv

Display the activation expiry date. Microsoft says it is "primarily useful for KMS clients, because MAK and retail activation is perpetual":

slmgr.vbs /xpr

Write down what the commands show, including the Windows edition. Then check the key you intend to install: its product (the Windows version it is for), where it came from, and how it was transmitted. A key sent in an email or a document and copied into the command prompt is the case Microsoft's em-dash warning is about.

Example (illustrative): at contoso.com.au a new server rds01 is built, and the administrator pastes the licence key from a PDF into the activation screen. 0xC004F050 appears. Pasting the key into a plain text editor shows that the separators between the groups of five characters are em-dashes, not hyphens. That is the case Microsoft warns about, so the next step is to retype the key with plain hyphens, not to ask for a new key.

Fix

Install the correct key, then activate. Use a key that you have checked against the Windows version installed and typed with plain hyphens.

Before you change it, make sure you have the output of slmgr.vbs /dlv above, and make sure you hold the key that is installed now, in your licence records. Microsoft's Slmgr.vbs page describes no command that shows the whole installed key, so your own record is the only way back to it.

Risk: the next command replaces the product key installed on this computer. Microsoft's page says "If a key is already installed, it's silently replaced." Run it only for the right computer and the right key, and run it in an elevated Command Prompt, as Microsoft requires for this option.

slmgr.vbs /ipk <5x5 key>

Microsoft's page adds that, "To prevent instability in the license service, the system should be restarted or the Software Protection Service should be restarted."

To undo it: run the same command again with the key you recorded before. If you do not hold the previous key, there is no way back from the replacement.

slmgr.vbs /ipk <previous key>

Microsoft says the system should be restarted or the Software Protection Service restarted after the key is installed.

Disruptive step: restarting the computer, or restarting the Software Protection Service, interrupts the services and sessions on this server for the time it takes. Choose a quiet period. Microsoft's pages give no steps for restarting the Software Protection Service on its own, so restart the computer. Nothing needs undoing; the computer comes back as it was.

Restart the computer now, then continue.

Before you activate, keep the earlier /dlv output: it is the record of the state before activation.

Risk: the next command asks Windows to activate with the installed key. For a MAK, Microsoft's page says "By design, you can only activate a MAK a limited number of times", so a successful activation counts against that key. Do not run it repeatedly while you are still guessing which key is right.

slmgr.vbs /ato

Microsoft's page says /ato makes retail editions and volume systems with a KMS host key or a MAK try online activation, and systems with a Generic Volume License Key (GVLK) attempt KMS activation. There is no way back from an activation counted against a MAK with the commands in Microsoft's slmgr page.

If the error persists with a key you have confirmed, Microsoft's page for another MAK error says to contact the Microsoft Licensing Activation Centers to check the key. Its text for 0xC004F050 gives no contact route.

Confirm the fix

  • Run slmgr.vbs /dli again. The licence information should show a licensed state for the edition you installed.
  • Run slmgr.vbs /xpr and read the result against the activation type: perpetual for MAK, an expiry date for a KMS client.
  • Open Settings and check the activation status on the computer.
  • Check the first error is gone. A new error code is a different fault: look it up by its code in Microsoft's table.

What to watch afterwards

  • KMS clients: the expiry date from /xpr, which Microsoft describes as primarily useful for KMS clients. A KMS client that cannot reach a KMS host can report 0xC004F074, a different error.
  • The number of activations used on a MAK. Microsoft's table includes 0xC004C020, "The activation server reported that the Multiple Activation Key has exceeded its limit."
  • A key that is refused as blocked. Microsoft lists 0xC004C003 for a MAK and 0xC004F051, "The Software Protection Service reported that the product key is blocked", with the solution "get a new MAK or KMS key, install it on the system, then try activating again."
  • 0x80070490, "The product key that you entered didn't work." Microsoft gives a MAK that was not valid, or a known issue in Windows Server 2019, as its causes, and a workaround that installs the key from an elevated command prompt. It is a different code from 0xC004F050.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's volume page gives no list of which key belongs to which Windows version and no way to read back the full key installed. Microsoft's pages do not describe how to keep the key out of the command line or its history. For licence terms and entitlements, check the current Microsoft licensing pages and your agreement.

Sources