Ad-aware...Unable to log on to Windows XP

Hi, Is anyone informed here if this is a real problem and has Lavasoft fixed it.. I have not used Ad-aware since I had been informed of this.
Lavasoft Knowledge Base Article 04060901
Unable to Log On To Windows XP After Removing
Wsaupdater.exe
After removing wsaupdater.exe from BlazeFind using Ad-aware 6 Build 181 and reference file 01R314 02.06.2004 or 01R320 19.06.2004, The ability to log on to the system may be compromised.

CAUSE
This file edits an area of the registry, and Ad-aware 6 Build 181 is unable to correct this registry change…………………………..

Has anyone had problems after using Ad-aware 6 after this date, I just have not been game enough to use it again.

 

Hi Hawk,

Yes, I've used it since - and have known about this. This was a specific issue and would have been identified as such on the scan. The lastest ref file now is 01R334 24.07.2004

You have a tool on the OS that quards the OS from most damage, System Restore. This sort of thing it certainly would have. If you haven't truned it off - or played with restore intervals, you should have restore points every 24 hours.

Regards - Charles

 

Old news May 27th
Provided the program is updated it will not couse any problems now,

as far I as know it simply leave this entrie alone(as seen in a Hiajckthis log)
F2 - REG:system.ini: UserInit=C:\Windows\System32\wsaupdater.exe,

But fix's this
O4 - HKLM\..\Run: [Windows SA] C:\Program Files\WindowsSA\omniscient.exe
and deletes that folder

Ad-Aware is a great program,, they fixed that problem I believe it was a day or two later.

 

Does anyone know the fix for this? This recently happened to my labtop. I can't log in. It's a continous loop.

Help!

M Byers

 

Hi monday27.

You need to post a new thread in whichever section of the forum matches your OS. It could be an ad-aware issue but also could be lot of other things.

The problem will get a better look if you make a new thread.

Describe the problem in as much detail as possible.

 

It's true that Ad-Aware does not complete the repair and you can be locked out until you fix the problem, either by a repair installation or by using the Recovery Console:

Boot to the Recovery Console and copy userinit.exe over wsaupdater.exe:

cd Windows
cd system32
copy userinit.exe wsaupdater.exe

You regain access to the machine after a reboot.
Then edit:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\userinit

C:\Windows\System32\wsaupdater.exe

back to it's default value of:

Value: C:\Windows\System32\userinit.exe

 

Correction:

The registry edit should be done from Safe Mode before trying to boot back into XP in normal mode.