Auto logoff after login

[Martin]

We have the same problem as many others, when logging in to WIndows XP
(prof) it says "logging on" and a few seconds later "logging off" and
"saving settings" sending us back to the welcome screen.

I have been able to verify which files are in the system32 and there
are NO wsaupdater.exe.
But I haven't so far been able to check the registry, but since there
are no wsaupdater.exe that should not be the problem.

No user can login, not even the administrator, not in normal mode, nor
in safe mode.

So, I do not think the problem is due to wsaupdater.exe, do you have
any other idéas to this?

Thanks in advance

Regards
Martin Rådbo
Teknologia

 

[Jason Marshall]

We have the same problem as many others, when logging in to WIndows XP
(prof) it says "logging on" and a few seconds later "logging off" and
"saving settings" sending us back to the welcome screen.

I have been able to verify which files are in the system32 and there
are NO wsaupdater.exe.
But I haven't so far been able to check the registry, but since there
are no wsaupdater.exe that should not be the problem.

No user can login, not even the administrator, not in normal mode, nor
in safe mode.

So, I do not think the problem is due to wsaupdater.exe, do you have
any other idéas to this?

Thanks in advance

Regards
Martin Rådbo
Teknologia

Start professional setup from the CD, get to the repair stage and run
a repair.
Jason Marshall
Australian Unemployed IT Technician/ASP Web Developer.
Email me: (e-mail address removed).

ATTN: Help Others: Please keep all replies to my posts in the newsgroup.
Failure to do so can result in your message not being answered.

 

[Rick \Nutcase\ Rogers]

Hi,

The problem is that wsaupdater doesn't exist, and the userinit is looking
for it. This is because of the registry modification done by the spyware
that added that file to the system32 directory. Now that you have removed
the file (presumably because you ran adaware or some other cleaner), the
userinit fails when it can't find that file. The solution is to copy
userinit.exe as wsaupdater.exe in that folder as a temporary workaround.
Then you will be able to load a user folder and fix the registery entry
causing it. I wrote this short discussion on it that should help:
http://rickrogers.org/fixes.htm#Blazefind

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org