Member Avatar for Highcap56

Greetings Folks - My 20 year old forgot his password for our main XPPRO Desktop (I could have logged in as Admin, but NO ..) and used some hacked up "change your password" product that has wreaked havoc on this OS.

Now, it does not recognize windows as registered, and prompts for activation on every boot. No matter how many times we enter the verification key it will not accept it.

I am fairly comfortable working in the registry and can do a Safe Mode Command Prompt login.

Obviously something has to be changed there, yet I have no clue and have a way too much to lose to simply wipe it and start over.

If someone has a suggestion of how to handle this it will be greatly appreciated.

Thanks!

Bob

  • 3 Contributors
  • 2 Replies
  • 116 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by MartyMcFly

Dani AI

Generated

For — a focused, low-risk checklist to try before a full reinstall. is right that a repair/reinstall can work, and 's point about preserving documents is important; the steps below try to fix the activation/registry damage that most often causes repeated activation prompts.

Try these in order (you can do them from Safe Mode with Command Prompt):

  • Verify the install key on the COA sticker matches the XP edition installed (Home vs Pro, OEM vs Retail).
  • Inspect and protect the activation file: look in C:\Windows\System32 for wpa.dbl (and any wpa.bak). Back up that file before changing it. If wpa.dbl is missing or clearly corrupted and wpa.bak exists, renaming the backup to wpa.dbl often restores activation state.
  • Check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion for ProductId and DigitalProductId. If those values are present but activation still fails, check the key permissions (make sure SYSTEM and Administrators have Full Control) — some password tools change ACLs and block the activation wizard from writing.
  • Force the activation UI and retry (online or by phone) after any file/permission fixes. If system files are damaged, run SFC from Recovery Console or consider the repair install only after these steps.

Example command sequence to run from a Safe Mode command prompt:

cd \windows\system32
dir wpa.*
copy wpa.dbl wpa.dbl.bak
if exist wpa.bak ren wpa.bak wpa.dbl
%windir%\system32\oobe\msoobe.exe /a

Cautions: back up the files you touch (or image the disk) before altering registry hives or system files. Avoid cracks/keygens — they make recovery harder. If activation still rejects the COA key, use the activation-by-phone option and have the COA and installation details ready.

Recommended Answers

All 2 Replies

Member Avatar for J_Search

Highcap56,

To me, it sounds like you're dealing with two issues. 1. The changes made by your havoc program, and 2. XP Copyright control measures (which are no picnic).

Although you can't perform a clean install, why don't you attempt to install over the current copy. Perhaps you'll get lucky. Otherwise, think about backing up your data for a clean install. You may spend hours upon hours trying to perform an impossible fix.

J_

Member Avatar for MartyMcFly

I disagree, you are one of the lucky people that when faced with a full reinstall, get the opportunity, (at a risk maybe in this case) to save all of you needed documents.

If you do, just make sure to Virus check them, before sticking them back on the new build.

good luck, mmf

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.