Changing the XP Prdocut Key


Recommended Posts

First of all, I am not asking for keys, I am asking for help in changing some.

I am working on the task of documenting all the licenses we have and which are in use and so forth. In the process, I have been changing the installed key from the OEM key to the one actually on the case. There have been a total of three computers that I can not change the key on though and I am wondering if there are any other methods available to do this. I was change the OOBE timer and then running the activation wizard as was posted on Microsofts website (even though none of these are VLK keys it still worked on every single machine except these three). All three of these are XP Home, but it worked on others. The wizard just comes back up saying it has already been activated. I have also tried third party utilities to change it for me and they all fail as well. I am hoping someone else out there has experienced this and can help out. Thanks in advance for your feedback.

Link to comment
https://www.neowin.net/forum/topic/371099-changing-the-xp-prdocut-key/
Share on other sites

Inside the attached ZIP is a VBS script file.

Run it with the key as an variable, for example, going to Start > Run and typing:

C:\ChangeKey.vbs ABCDE-ABCDE-ABCDE-ABCDE-ABCDE

Can't promise this will work as you seem to be having a most bizarre problem, but I used this method yesterday for my PC and it worked, so it's another option you could try.

ChangeKey.zip

I was using the magic jelly bean key changer before. It does not work on these three systems though. I noticed that on most of the machines, the OOBETimer is the only key in WPAevents, but on these three there is a second key "LastWPAEventLogged". This key was also on 1 or 2 other machines that worked fine. Removing / changing either of these keys has no effect. With or without this second key I get "Windows has already been activated" and without the OOBETimer key the activation screen doesn't even come up (kind of expect that), changing it gives the already activated as well.

I tried the WMI scripts from the MS KB artickes, and I get an error that says Invalid Operation 0x80041016. Your script did the same thing.

Any other ideas? This has me baffled.

Those are the instructions from MS basically. However, I did not try:

Make sure you are logged in with the local administrator account, not just an account with Administrator privileges.

Try replacing the %systemroot% variable with the actual drive letter that your actual directory path, especially when dual booting, or if the system path is on a drive other than C:\

Well since it is Home Edition, you can only access the Administrator account via safe mode, and you can't activate Windows in safe mode, but the account I am using is an administrator on the PC. Explicitly defining the path didn't help either unfortunately.

Home Edition just gets lamer and lamer...

And how would you use sysprep to change the product key? I don't want to reinstall these systems if at all possible...

586514751[/snapback]

Run setup manager (i386, support, deloy.cab).

This creates an answer file for the sysprep. Put tyhe correct details in it.

Run sysprep.

PC restarts and does a mini install that takes about 10 minutes.

All done.

Well since it is Home Edition, you can only access the Administrator account via safe mode, and you can't activate Windows in safe mode, but the account I am using is an administrator on the PC. Explicitly defining the path didn't help either unfortunately.

Home Edition just gets lamer and lamer...

586514986[/snapback]

Just as an FYI, you can definitely access the administrator account in normal boot mode. If you are using the welcome screen to get in, just hold down Ctrl+Alt and hit the Del key 2 times. It'll take you to the classic login and you can login as administrator.

So many people don't know about this, and it's one of the biggest security risks on Home Edition installations. Since so many manufacturers don't assign a password to "administrator", pretty much anyone who knows this can access the account by doing what I just wrote.

Just as an FYI, you can definitely access the administrator account in normal boot mode.  If you are using the welcome screen to get in, just hold down Ctrl+Alt and hit the Del key 2 times.  It'll take you to the classic login and you can login as administrator.

So many people don't know about this, and it's one of the biggest security risks on Home Edition installations.  Since so many manufacturers don't assign a password to "administrator", pretty much anyone who knows this can access the account by doing what I just wrote.

586525674[/snapback]

That's true, but normally you'll get an error saying "Cannot log you on due to account restrictions" if you try to log onto a Home machine as Administrator on a normal boot

I hear ya. Even Microsoft talks about it with home edition. But I've just never had it happen to me where I couldn't login to the account from Normal mode on the Home machines that I've used. Then again, I barely ever use the home edition so my details could be a bit fuzzy...! :p

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed by Hamid Ganji Image via Apple Apple CEO Tim Cook confirmed in a recent interview that the company may have to raise prices on some of its products due to the ongoing memory shortage. While he did not elaborate on the scale of the price hikes, new estimates suggest that Pro iPhone models could become significantly more expensive this fall. The Wall Street Journal and research firm TechInsights have come up with an educated estimate of how much the upcoming iPhone 18 Pro could cost after its launch in September. The estimate is based on current increases in memory and storage chip prices. For starters, the iPhone 18 Pro base model is expected to feature 12GB of RAM and 256GB of internal storage. According to TechInsights estimates, 12GB of DRAM for the iPhone 17 Pro cost Apple $39 last year. However, for the iPhone 18 Pro, the cost of the same amount of DRAM could soar to $145. Likewise, 256GB of flash storage that previously cost $13 could now cost around $51. Producing a base iPhone 17 Pro reportedly cost Apple around $582, but TechInsights estimates that the production cost of the iPhone 18 Pro could rise to $726. If Apple wants to maintain the roughly 47% profit margin it enjoys on the iPhone 17 Pro, the base price of the iPhone 18 Pro would need to reach $1,371. After standard pricing adjustments, customers could end up paying around $1,299 for the base model. However, that may not be the end of the story. As we previously reported, the iPhone 18 Pro is said to feature a variable-aperture lens, which could cost Apple at least 50% more than the current camera system. The estimated $1,299 price tag does not include the additional cost of this upgraded camera hardware. Once that expense is factored in, the base model could cost at least $1,399. A $1,399 price tag for the base iPhone 18 Pro would represent a significant increase over the current $1,099 starting price of the iPhone 17 Pro. If Apple wants to keep its upcoming iPhones competitive, it may need to accept lower profit margins.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!