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.
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
Unknown said…
Thank you for sharing your blog. And i also recommend a site to you, hope to help you.www.vanskeys.com

Popular posts from this blog

Evolution MK-249C MIDI Keyboard Mac OS X Problem

Mac OS X generally seems capable of dealing with just about anything you can throw at it. However upon connecting my trusty Evolution MK-249C MIDI keyboard up to my 2nd generation MacBook it steadfastly refused to play ball. This keyboard has always been instantly recognised by Windows XP and so it was surprising to encounter this. The M-Audio website (M-Audio took over Evolution it appears) offered no real assistance. There was no driver available for Mac OS X 10.4.9 as the keyboard is supposed to be "Class Compliant" which apparently means it doesn't need one... strange. Eventually after consulting some forums I found the fix. The problem seems to be related to Mac OS on the Intel MacBooks. There is a patch on the M-Audio site but only for MacOS 10.1.5. This must be downloaded and installed. Here is the link: http://www.m-audio.com/index.php?do=support.drivers&f=596 Upon restarting the OS the keyboard was recognised by Mac OS and GarageBand had no trouble tal...

XP Startup Issues - The Recovery Console

The Windows Recovery Console is a fantastically useful tool if you find yourself with a PC that will not boot Windows. There are many useful Windows startup tools such as Last Known Good Configuration and the many different flavours of Safe Mode but all of these rely on a bootable Windows system. System Restore is completely useless in this scenario since it relies on one being in Windows to use it. The kinds of things that could couse an unbootable Windows system could be: Corrupted boot files - e.g. NTLDR, NTDETECT.COM Corrputed Windows system files - NTOSKRNL.EXE, HAL.DLL The Recovery Console allows you to boot into an environment "underneath" that of your Windows installation (by using the Windows CD or by choosing it at boot time if you pre-installed it) and so you can perform major low level repairs to your Windows installation. Follow the link below to find out how to use the Recovery Console: http://support.microsoft.com/kb/314058/

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