How to: Change your activation product key in Windows 8, Windows 2012 Server and MultiPoint Server 2012
How to: Change your activation product key in Windows 8, Windows 2012 Server and MultiPoint Server 2012
When you try to activate your Windows 8, Windows 2012 Server or MultiPoint Server 2012 sometimes you have a pre-set key (trial, etc.) which won’t let you activate your windows installation. There are other scenarios where you might want to change your product key (licensing, feature set, etc.) but unfortunately you can’t even though the system is throwing you errors that it can’t activate, etc. If you go to the System item in the Control Panel as before, you’ll see the “Change product key” link is not there anymore.
Fortunately there are other ways to get that Windows Activation // Enter a product key to activate Windows dialog box. Below are the two methods published by Microsoft on how to do this:
Method 1
- Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
- In the search box, type Slui 3.
- Tap or click the Slui 3 icon.
- Type your product key in the Windows Activation window, and then click Activate.
Method 2
- Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
- Type Command Prompt in the Search box.
- Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- Run the following command at the elevated command prompt:
slmgr.vbs /ipk <Your product key>
Note You can also use the Volume Activation Management Tool (VAMT) 3.0 to change the product key remotely, or if you want to change the product key on multiple computers.
Love
Can we use Let's Encrypt, the free and open certificate authority?
Hola! gracias por la info, me sirvió el comando sacandole el nombre del server. En mi caso, fue una migración…
Yes 3rd option helped me too. I removed the WC key Values from config file then started working.
I know this is from 2014. But really, thank you!