For most Windows XP installs, you'll never demand to worry almost the validity of the production key assigned to your re-create of the OS. However, software does tend to get installed without authorization, even in the most carefully managed shops, and and then from time to time you may need to reset the XP production primal.

For example, perhaps a user installed a pirated copy of XP just now wants to get legal. Maybe you've been hired past an arrangement that installed 100 pirated copies of XP but at present has a legitimate volume-licensing key (VLK). Perchance an end user purchased an boosted retail license for XP just needs to apply his original CD to install the software. When situations like these arise, irresolute XP's product cardinal is often the most applied—or only—solution.

Determining if you have a valid product ID
Hopefully you already know if you're dealing with a pirated copy of XP. Merely if you lot're unsure, a quick manner to tell is to install Service Pack 1. Shortly later on releasing Windows XP, Microsoft realized that most pirated XP installations were using two specific VLKs, the most popular of which begins with "FCKGW." These VLKs produce product IDs that friction match either XXXXX-640-0000356-23XXX or XXXXX-640-2001765-23XXX, where 10 is any number.

If y'all effort to install SP1 and go the following error bulletin:

The Product Central used to install Windows is invalid. Please contact your system ambassador or retailer immediately to obtain a valid Product Primal…"

You lot are dealing with a pirated re-create of Windows. For more information about obtaining a valid product fundamental, run across Microsoft Noesis Base commodity 326904.

Yous can also direct cheque the OS'sproduct ID past right-clicking on My Reckoner, clicking Backdrop, and selecting the General tab. The auto'due south production ID will be located under the Registered To section. If the ID matches either of the 2 models commonly associated with VLK fraud, you'll demand to obtain a valid XP production cardinal before proceeding. None of the procedures described beneath will work without a legitimate product central.

Two methods of irresolute Windows XP'southward product key
You can change a Windows XP installation'southward product key either by editing the registry or past using one of 2 Windows Management Instrumentation (WMI) scripts. The registry editing method is outlined in Noesis Base of operations manufactures 321636 and 328874 and works on Windows XP Home, Windows XP Professional, and Windows XP Corporate Edition. The script method is outlined in article 328874 and is designed to piece of work on Corporate Edition installations that use a VLK and do not crave activation. Information technology may piece of work on a Home or Professional person installation, merely I have not tested this scenario.

The script method is the practical solution for irresolute the product keys on a large number of machines. Regardless of the method you choose, make sure to backup important data earlier changing a product ID, since an unexpected problem could return the machine unbootable and necessitate a complete reinstallation of Windows.

Warning


The following instructions involve editing your system registry. Using the Windows Registry Editor incorrectly can crusade serious problems that require the reinstallation of your operating arrangement and possible loss of information. TechRepublic does non support problems that arise from editing your registry. Use the Registry Editor and the following directions at your ain take chances.

Editing the registry
Begin by opening the Registry Editor and navigating to
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Electric current Version\WPAEvents

In the right pane, right-click the ODBETimer binary value and select Modify. Modify at least 1 grapheme of this value to either a number from 0 to ix or to a letter from A to F, then click OK and close the Registry Editor. This renders the current product key invalid and deactivates Windows.

Now, it'south fourth dimension to reactivate Windows using your new production cardinal. Click Start | Run and enter the command:
%systemroot%\system32\oobe\msoobe /a

where %systemroot% is your Windows directory. In many cases, this command will look similar:
C:\windows\system32\oobe\msoobe.exe /a

At this point, Windows will launch the Production Activation Wizard.

Figure A

Select the option to telephone a Microsoft customer service representative to activate Windows, as shown in Figure A, and click Next. At present, select the Change Production Cardinal option and enter your new production key every bit shown in Figure B. Finally, click Update and close the window. If Windows returns you to the previous screen, just select the Remind Me Later on choice. When the wizard is finished, reboot the system.

Figure B

When Windows reboots, your side by side step will depend on which Windows XP version yous are using. If you have XP Home or Professional, y'all'll be prompted to reactivate your re-create of Windows through the normal activation procedure. If yous have XP Corporate, no activation is required and your automobile should have a valid production ID. You tin verify this by running the %systemroot%\system32\oobe\msoobe.exe /a control again. When the wizard loads this time, you should see a message indicating that your copy of Windows has already been activated.

Using a WMI script
Although the registry editing procedure is constructive, it can be tedious and impractical if you need to change the product key on more than a few machines. Then Microsoft provides two WMI scripts, ane for XP machines with SP1 and i for XP machines without SP1.

View the code for the WMI script, ChangeVLKey2600.vbs, designed for use on XP machines without SP1.

View the code for the WMI script, ChangeVLKeySP1.vbs, for XP machines with SP1 already installed.

Copy the appropriate script's lawmaking into a text file and save information technology equally either ChangeVLKey2600.vbs or ChangeVLKeySP1.vbs. The scripts tin act in conjunction with a valid product primal as function of a login script to change the product ID on multiple machines. Y'all tin can too execute the script from the command line to change the key on a single estimator.

For example, if you wanted to change the production primal on an XP machine without SP1 and had already saved the script to root directory on the C: drive, you would click Get-go | Run and enter the post-obit command:\
C:\changevlkey2600.vbs xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Of class, xxxxx-xxxxx-xxxxx-xxxxx-xxxxx in this scenario is a valid production key.

The script should have only a few seconds to run and won't prompt you lot for further action unless at that place'southward a trouble, such every bit an invalid product key. As with the registry editing method, y'all can verify that Windows is at present using a valid product key by running the control:
%systemroot%\system32\oobe\msoobe.exe /a

The Production Activation Wizard will load and should tell you that your copy of Windows has already been activated.