Skip to main content

Change Windows 7 Product Key

After imaging a Windows 7 machine so as to clone to multiple others I came across a slight hassle: how to change the product key on the newly cloned PC?


Previously under XP I would have used a key changer tool such as WinKeyFinder but I had thought that the "Change Product Key" option in System Properties would do the trick in Windows 7.


Unfortunately the "Change Product Key" link wasn't showing in System Properties.  Perhaps this is because this was an OEM version of Windows 7?  I'm not sure.  But here's how to do it:

  1. Open a Command Prompt
  2. Type "slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" where the xxxxx characters are your product key.
  3. Give it a minute and you should get a message saying that the product key has been updated.
  4. Then type "slmgr.vbs -ato" to active Windows with this new product key.
  5. You should then get a message saying that Windows has been successfully activate.
Hope this helps.

Comments

Unknown said…
This comment has been removed by a blog administrator.
20 June 2012 at 08:50
Unknown said…
I have seen your blog and read your content i think it's fantastic and i need for us to getting for knowledge.

Useful link- Linksys Router Setup
3 April 2013 at 17:28
Unknown said…
Thank you for sharing your blog. And i also recommend a site to you, hope to help you.www.vanskeys.com
27 November 2014 at 06:42
Post a Comment

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
11 comments
Read more

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS
Post a Comment
Read more

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition.  However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition.  This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell:  reagentc /disable If you get the error message "REAGENTC.EXE: Operati...
Post a Comment
Read more