Archived from groups: microsoft.public.windowsxp.basics (
More info?)
Hi Marlene,
The problem is that the file is not there, but the logon routine is looking
for it. Copying the userinit.exe file as wsaupdater.exe creates a "fake"
file that allows the logon to finish. Then you can get in and fix the
damage.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org
"Marlene" <marlene_nv@yahoo.com> wrote in message
news:472d01c49fd9$80704ee0$a401280a@phx.gbl...
> Dear Rick,
>
> I have the same problem, but when I checked the system32
> directory, I don't have the wsaupdater.exe file. Any other
> fixes?
>
> I ran the norton antivirus 2004 to check for adwares, but
> it could not delete a LOT of the adwares it found. There
> were some I manually deleted, could that have caused the
> problem?
>
> Also, I cannot check the registry as I can only access my
> hard disk using the installer CD, then going to the dos
> prompt.
>
>>-----Original Message-----
>>Hi,
>>
>>Run a spyware cleaner lately? The userinit value may have
> been corrupted by
>>the removal of blazefind. It adds wsaupdater.exe to the
> logon value in the
>>system registry, sometimes appending it, sometimes
> replacing it. Running
>>Adaware or other cleaners detects and removes
> wsaupdater.exe, but doesn't
>>correct the registry damage. If this is the case, then
> you may need to load
>>the registry hive from another installation and change
> it. This is the key:
>>
>>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon
>>
>>Userinit string value should be:
>>
>>C:\WINDOWS\system32\userinit.exe,
>>
>>On the damaged installations it's one of these:
>>
>>C:\WINDOWS\system32\wsaupdater.exe,
>>C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32
> \wsaupdater.exe,
>>
>>"pcoc" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:281001c49f60$9d723180$a501280a@phx.gbl...
>>> One afternoon everything was working fine, now when I
> log
>>> in to any user at the welcome screen, it goes for 2-3
>>> seconds then says 'saving settings' and automatically
> logs
>>> off. Unsure how to proceed.
>>
>>
>>.
>>