sodcalculator

10 Tech How-To

Change Product Key Not Working Windows Server? Fixes

Guide 10-54572 · Updated · Step by step

If the “Change product key” option is grayed out or fails on Windows Server, the fix usually involves using the SLMgr command-line tool or editing the registry, because the Settings app restricts product key changes on Server editions. This article explains why the option fails and provides step-by-step fixes that work on current Windows Server versions.

Why the Change Product Key Option Fails

On Windows Server, the Settings > System > Activation page sometimes shows a grayed-out “Change product key” button. This happens for several reasons:

  • Server Manager or Group Policy may disable activation changes.
  • The server is activated with a KMS (Key Management Service) client key, and the UI hides the change option.
  • The user lacks administrator privileges.
  • The Windows Server edition is evaluation or volume license, where the UI path is different.

Microsoft expects administrators to use the slmgr.vbs script for product key changes on Server, so the GUI limitation is by design.

Fix 1: Use SLMgr to Change the Product Key

The most reliable method is the command-line tool SLMgr (Software License Manager). Open an elevated Command Prompt or PowerShell (Run as Administrator) and run:

  1. Install the new key: slmgr /ipk <your-product-key> (replace with your actual key, dashes included).
  2. If you have a volume license key, you may also need to set the KMS host: slmgr /skms <hostname> (only if using KMS activation).
  3. Activate online: slmgr /ato.

If the key is valid, you should see a confirmation message. If you get error 0xC004F069, the key is for a different edition or channel.

Fix 2: Check for Group Policy Restrictions

If SLMgr also fails, a Group Policy might block changes. Open gpedit.msc and navigate to:

Computer Configuration > Administrative Templates > System > Software Protection Platform

Look for policies like “Disable online activation” or “Do not allow product key changes.” If any are enabled, set them to Not Configured and run gpupdate /force in an elevated command prompt.

Fix 3: Edit the Registry (Last Resort)

If the UI and SLMgr both fail, you can manually remove the existing key from the registry, then re-enter it. This is risky—back up the registry first.

  1. Open regedit as administrator.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform.
  3. Delete the KeyManagementServiceMachine and KeyManagementServicePort values (if present).
  4. Close regedit, restart the Software Protection service: net stop sppsvc then net start sppsvc.
  5. Try slmgr /ipk again.

If the problem persists, you may need to run slmgr /rilc to re-install licenses, then reboot.

Common Error Codes and Their Meanings

When changing a product key fails, you’ll often see an error code. Here are the most common ones:

  • 0xC004F050 – The product key is invalid or not for this edition.
  • 0xC004F069 – The key is a volume license key but the server is not volume-licensed.
  • 0xC004F012 – The Software Protection service is not running.
  • 0xC004F074 – The KMS host cannot be reached (if using KMS).

For each, verify the key matches the server edition (Standard vs Datacenter) and channel (Retail vs Volume).

When You Should Use the GUI vs Command Line

The Settings app works on Windows Server 2016 and later, but it is often unreliable for key changes. The GUI is fine for viewing activation status, but for actual key changes, the command line is the supported method. If you are comfortable with PowerShell, you can also use:

slmgr.vbs /ipk <key>

This is identical to the CMD version. Always run as administrator.

If You Are Switching from Evaluation to Full Version

If your server is running an evaluation edition, you cannot just change the key—you must first convert the edition. Run:

DISM /Online /Get-CurrentEdition
DISM /Online /Get-TargetEditions

Then use DISM /Online /Set-Edition:ServerStandard /ProductKey:<key> /AcceptEula. This process requires a reboot and preserves installed roles and features.

Frequently Asked Questions

Why is the “Change product key” button grayed out?

This usually happens because you’re not an administrator, or because a Group Policy restricts activation changes. Run the command prompt as administrator and use SLMgr instead of the GUI.

Can I change the product key on a domain controller?

Yes, but you must be a domain admin. The process is the same, but be aware that activation changes may require a reboot if the server is also a KMS host.

Will changing the product key affect installed roles or data?

No, changing the product key does not touch roles, features, or data. It only updates the licensing state. However, if you convert from evaluation to full, you must use the DISM method, which may require a reboot.

What if I don’t have a new product key?

You cannot change the key without a valid one. If you’re trying to switch from KMS to MAK, you need the MAK from your volume licensing portal. If you’re trying to activate with a retail key, ensure it matches the edition.

How do I check the current product key?

Run slmgr /dli to see the current key and activation status. For the full key, use slmgr /dlv (it may show the last 5 characters only).

Is there a way to change the key without rebooting?

Yes, for most key changes, no reboot is needed. Only edition conversions (evaluation to full) require a reboot. After running slmgr /ipk, activation is immediate.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →