Hi I have this same problem.

I log into Win XP, but it immediately logs out All mo des including safe mode do this. I enter Recovery console and do the COPY USERIN IT.EXE WSAUPDATER.EXE in system32, but that doesn t work either. I know it copies the file and I am doing everything correct. I searched all over the net and have found NO other solution if the wsaupdater replace doesn t work. Does anyone know any useful nformation to help me fix this problem? Thanks in advance Any help is g reatly appreciated FOR THOSE OF YOU THAT CANNOT GET THE COPY USERINIT.EXE WSAUPDATER.EXE TO WORK > P LEASE READ THIS OK, I read an old post from annoyances.org, way back in 2004, it is practically the only one that differs from all the others, THIS worked for me, where the cop y userinit.exe wsaupdater.exe did NOT: Article post: NOTE I am modifying the post to how it worked for ME http://www.annoyances.org/exec/forum/winxp/1096561524?s 1) Use the XP disk and go into the Recovery Console 2) We need to replace the software hive with a previous good backup. a.) type cd system32\config enter b.) type ren software software.old enter This renames the current software hive to software.old c.) type copy C:\windows\repair\software enter It should say 1 file(s) copied d.) type exit this will leave recovery console 3) Hit F8 before Windows starts to enter Safe Mode You should hopefully be able to log in now 4) Now we need to Fix the registry a.) Start >Run > type regedit, enter b.) Select/Highlight HKEY_LOCAL_MACHINE c.) Hit File >Load Hive d.) Find where you saved the software.old file (C:\windows\system32\config\soft ware.old) e.) Just name it test 5) THIS IS WHERE MY FIX Differs from the previous post a.) Navigate to test\software\microsoft\windows nt\currentversion\winlogon b.) Look for the Userinit field c.) Mine was blank which was causing the log off loop, others had wsaupdater.ex e in this key - Double click on the ky and type C:\windows\system32\userinit.exe, Note: if anything differs repeat step 5 with HKEY_LOCAL_MACHINE\software\micros oft\windows nt\currentversion\winlogon 6) Restart and log back into Recovery Console 7) Restore the original hive now a.) type cd system32\config enter b.) type del software enter c.) type ren software.old software enter d.) type exit enter Log back into Windows normally. This worked for me and I hope you find that it also works for you! Thanks, good luck ========================================================================= Option 2: re: I can t log in! Thursday, September 30, 2004 at 9:25 am

Windows XP Annoyances Discussion Forum Posted by Norm Marks (1 messages posted) This is apparently a relatively new problem and I just found an awesome post up on the Ad-Aware website that corrects this problem. I and a lot of others have use d this and it works perfectly. There s a peice of spyware called the usaupdater.exe which apparently comes from Blazefind. When Ad-Aware removes Blazefind is when the problems occur. Hope this works for you! Norm HERE S THE POST: I haven t tested this. I used a similar method on a customer s computer and it worke d. Second NOTE: Most of these steps assume that Windows is installed to C:\windows. If your installation is not in C:\windows, then please change the paths in my i nstructions to where your installation is. OK, I just had a customer that had this problem and here is how I resolved it. I limited the steps some to (hopefully) make it easier. First things first get to recovery console using previous methods provided. If y ou are unsure of how to get to recovery console look at the previous methods of re solving this problem and they explain it. OK, now that we are at recovery console, we need to replace the software hive wi th a previous good backup. It should look something like this: C:\windows>cd system32\config C:\windows\system32\config>ren software software.old This renames the current software hive to software.old C:\windows\system32\config>copy C:\windows\repair\software It should say 1 file(s) copied NOTE: After the next step you will want to remove the cd, then boot into safe m ode. If you do not boot into safe mode in Windows XP it may prompt you to reactivate and you may not be able to get into Windows. C:\windows\system32\config>exit Now hit the F8 key and boot into safe mode. Logon to the administrator account w hen you reach the welcome screen. Hopefully you will be able to logon. Now we need to edit your old registry to change the path to the userinit.exe fil e: open regedit.exe Highlight HKEY_LOCAL_MACHINE (note: this is important, if you do not highlight this the next step will not work) goto file load hive

Now select your old registry file which should be in C:\windows\system32\config \software.old It will ask you what to name it, if you don t understand, just type test . Now navigate to the following: HKEY_LOCAL_MACHINE\\microsoft\windows nt\currentversion\winlogon. Look at what the userinit value is. On my customer s machine it was %system32%\us erinit.exe which is invalid. NOTE: If you can, post what your value is when you look at this. Next change the value to read C:\windows\system32\userinit.exe Now close the registry editor, and we need to go back to recovery console to put your original registry back which should look like this: C:\windows>cd system32\config C:\windows\system32\config>del software C:\windows\system32\config>ren software.old software C:\windows\system32\config>exit This (in theory) should get you back into Windows. Please post here what your results are so that we can have some good feedback on the solution. My theory is that Adaware SE is fixing the wsaupdater.exe problem, but it is set ting the value in the registry to %system32%\userinit.exe which does not work on all systems.