Activation wizard appears as follows: Select the option “activation by phone” and click on “Next”. In the next page click on “CHANGE PRODUCT KEY” button, enter a new valid product key, press OK and close the wizard. Reboot the computer. After the restart type the same command (as shown in step-5) in the “Run” box.
Reseting the Activation Trial: - In this example: Your activation period has expired, (past 30 days) and you need to get to Normal mode again. Turn On your PC 2. Press F8 repeatedly and go to Safe Mode 3. Logon as per normal (note: Administrator password is usually blank, but hopefully you know your password) 4. Allow the Desktop to fully load (answering 'Yes' to continue into Safe Mode) (note: This is just a long way of saying go to Safe Mode) 5. Click on Start - Run 6. Type in exactly: rundll32.exe syssetup,SetupOobeBnk (and click OK) (note: one space, after 'rundll32.exe ' also the Oo are two letter o's in 'oobe'; capitals and comma are important) 7.
Wait a couple of seconds (although you will Not see any change) 8. Restart your PC normally (Start - Shutdown - Restart - Ok) 9. You are now able to go to Normal Mode again (For another 30 days!!!) 10. Do whatever you like, you're back to Normal. This fixed it for me but took me a long time to find this and get it going, hopefully it works for you to. Hello, I was able to work around it by using psexec from sysinternals (free download). You'll need to install it on another computer that is on the same network as the one that need reactivated.
Boot the system that needs reset so that it's on the logon screen of XP (normal mode, NOT safe mode), then run the following command from another machine running XP that has psexec installed and is on the same network: psexec computername -u computername administrator -p password rundll32.exe syssetup,SetupOobeBnk where computername = the remote computer to be reactivated. Hope this helps someone. @ Bryan Concerning your second post (April 27, 2011 10:13am). Hello, I was able to get yet another work-around that took less steps than you following post.
![Windows Windows](https://i.ytimg.com/vi/OCT1arULR2U/hqdefault.jpg)
I had same problem as you described. I then decided to try booting into 'Safe-Mode Command Prompt' and entered the same exact command in the cmd window. Booting up in Safe Mode, even with networking enabled did NOT work. However, boot with Command Prompt Safe Mode did work. Press F8, Choose the Safe Mode 'Command Prompt' option. And then enter into the cmd window: rundll32.exe syssetup,SetupOobeBnk and hit the ENTER key.
You will NOT get any indication or feedback that it worked. But it DID work! Now try loading Windows XP again and then activate with correct key!:) Hope this helps someone just as this original post helped me while working with my client's computer that had Widnows XP Media Center Edition 2005 on it.
For most Windows XP installs, you’ll never need to worry about the validity of the product key assigned to your copy of the OS. However, software does tend to get installed without authorization, even in the most carefully managed shops, and so from time to time you may need to reset the XP product key. For example, perhaps a user installed a pirated copy of XP but now wants to go legal. Maybe you've been hired by an organization that installed 100 pirated copies of XP but now has a legitimate volume-licensing key (VLK). Perhaps an end user purchased an additional retail license for XP but needs to use his original CD to install the software. When situations like these arise, changing XP's product key is often the most practical—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. But if you're unsure, a quick way to tell is to install Service Pack 1. Shortly after 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 match either XXXXX-6-23XXX or XXXXX-6-23XXX, where X is any number. If you try to install SP1 and get the following error message: The Product Key used to install Windows is invalid. Please contact your system administrator or retailer immediately to obtain a valid Product Key' You are dealing with a pirated copy of Windows. For more information about obtaining a valid product key, see Microsoft Knowledge Base article.
You can also directly check the OS’sproduct ID by right-clicking on My Computer, clicking Properties, and selecting the General tab. The machine's product ID will be located under the Registered To section. If the ID matches either of the two models commonly associated with VLK fraud, you’ll need to obtain a valid XP product key before proceeding. None of the procedures described below will work without a legitimate product key. Two methods of changing Windows XP's product key You can change a Windows XP installation's product key either by editing the registry or by using one of two Windows Management Instrumentation (WMI) scripts. The registry editing method is outlined in Knowledge Base articles and and works on Windows XP Home, Windows XP Professional, and Windows XP Corporate Edition. The script method is outlined in article and is designed to work on Corporate Edition installations that use a VLK and do not require activation.
It may work on a Home or Professional installation, but I have not tested this scenario. The script method is the practical solution for changing the product keys on a large number of machines. Regardless of the method you choose, make sure to backup important data before changing a product ID, since an unexpected problem could render 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 cause serious problems that require the reinstallation of your operating system and possible loss of data.
TechRepublic does not support problems that arise from editing your registry. Use the Registry Editor and the following directions at your own risk. Editing the registry Begin by opening the Registry Editor and navigating to HKEYLOCALMACHINE Software Microsoft WindowsNT Current Version WPAEvents In the right pane, right-click the ODBETimer binary value and select Modify. Change at least one character of this value to either a number from 0 to 9 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’s time to reactivate Windows using your new product key. 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 like: C: windows system32 oobe msoobe.exe /a At this point, Windows will launch the Product Activation Wizard. When Windows reboots, your next step will depend on which Windows XP version you are using. If you have XP Home or Professional, you’ll be prompted to reactivate your copy of Windows through the normal activation process. If you have XP Corporate, no activation is required and your machine should have a valid product ID. You can verify this by running the%systemroot% system32 oobe msoobe.exe /a command 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 process is effective, it can be tedious and impractical if you need to change the product key on more than a few machines. So Microsoft provides two WMI scripts, one for XP machines with SP1 and one for XP machines without SP1. Copy the appropriate script's code into a text file and save it as either ChangeVLKey2600.vbs or ChangeVLKeySP1.vbs.
The scripts can act in conjunction with a valid product key as part of a login script to change the product ID on multiple machines. You can also execute the script from the command line to change the key on a single computer. For example, if you wanted to change the product key on an XP machine without SP1 and had already saved the script to root directory on the C: drive, you would click Start Run and enter the following command: C: changevlkey2600.vbs xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Of course, xxxxx-xxxxx-xxxxx-xxxxx-xxxxx in this scenario is a valid product key. The script should take only a few seconds to run and won't prompt you for further action unless there's a problem, such as an invalid product key. As with the registry editing method, you can verify that Windows is now using a valid product key by running the command:%systemroot% system32 oobe msoobe.exe /a The Product Activation Wizard will load and should tell you that your copy of Windows has already been activated.
Related Topics.