Windows Xp Activation Wpa Kill Sp2

I replaced a dead eMachines motherboard with a very similar Asus motherboard. Almost the only difference is the BIOS, which is for an HP machine instead of an eMachines machine. Also, the onboard audio controller is different, but I think that's the only functional difference. Using the new motherboard with the the original hard disk drive, which has Windows XP Home + SP1 installed, it boots up to the Welcome/logon screen, but when I try to log on it says: [Windows Product Activation] This copy of Windows must be activated with Microsoft before you can log in. Do you want to activate Windows now?

[Yes] [No] I say yes, and it says: [Activate Windows] Windows Product Activation Windows is already activated. [OK] I click OK and it takes me back to the Welcome (log on) screen.

The only way to bypass the loop is to boot up in 'Safe Mode With Command Prompt.' Over three hours on the phone with Microsoft yielded no solution (nor even an admission that it is a bug for Windows to simultaneously insist that it needs to be activated and is already activated). The only useful thing I learned from that ordeal is that, remarkably, I can install a fresh copy of XP+SP1 on a clean hard disk drive using the eMachines Restore CDs (which use Norton Ghost), and activate it without a hitch using the Product Key from the sticker on the case.

As I installing my Windows XP SP2, I had a minor problem, I don't know how to activate my copy of. How to bypass WPA (Windows Activation) on Windows XP. Oct 19, 2006 - To make sure that you are able to activate your Windows XP; To make sure that you. The important file here, is the file called WPA_Kill.exe. Age of ultron download torrent. Jetzt helfe ich mir selbst vw polo 6n download video.

I'm really surprised that the eMachines restore CDs work on a machine that no longer has an eMachines BIOS. But I'd really like to re-activate the already-installed copy of Windows.

By booting in Safe Mode With Command Prompt, I can try various things to fix it. I've tried a lot of things so far, without success: changed HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion WPAEvents OOBETimer regsvr32 regwizc.dll regsvr32 licdll.dll replaced HKEY_LOCAL_MACHINE HARDWARE DESCRIPTION System with a copy saved from the fresh install. Deleted HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersio n WindowsUpdate IUControl deleted HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersio n WindowsUpdate OemInfo Replaced c: windows system32 WPA.DBL and c: windows system32 WPA.BAK with copies from the fresh install. I can't figure out why msoobe.exe thinks that windows is already activated. I assume that it is looking somewhere in the registry, but I can't figure out where. I even exported 'before' and 'after' copies of the registry, before and after activating the fresh install, and then I compared the two.reg files to try to discover what had changed. Unfortunately, a LOT changed, and I can't tell what is important.

Does anyone have any other ideas? Thanks, -Dave. I tried to use RegMon to monitor msoobe.exe, to see what registry entries it is looking at when it runs at log-on time and gives the 'already activated' error. I intended to start XP in Safe Mode with Command Prompt, and then run RegMon and use its 'Log Boot' option to make it run during the next boot, when the Welcome/log-on presumably runs msoobe.exe to activate Windows.