Login logs off immediately

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.basics (More info?)

After running a round of Symantec antivirus, I found that
at the next reboot, whenever I click a user logo to login,
the user wallpaper flashes briefly, then logs off again.
No error message or any other indication occurs. This
happens for all 3 users. Help!

Thanks!
-- MBH
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.basics (More info?)

Hello Mark,

If it happened right after using Norton there is a SLIM chance that Norton
deleted something I wasn't suppose to, have you tried starting up in safe
mode? If you have try looking around on this site.
http://labmice.techtarget.com/windowsxp/TroubleshootingXP/startup.htm

--
-----------------------------------------
Michael Ortega

"Mark Hanson" <marsonkhan@aol.com> wrote in message
news:1f2701c4ac6d$25a4da30$a601280a@phx.gbl...
> After running a round of Symantec antivirus, I found that
> at the next reboot, whenever I click a user logo to login,
> the user wallpaper flashes briefly, then logs off again.
> No error message or any other indication occurs. This
> happens for all 3 users. Help!
>
> Thanks!
> -- MBH
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.basics (More info?)

Hi Mark,

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,

Another "quickie" method of resolution is to load the Recovery Console (see
below), copy userinit.exe as wsaupdater.exe from the command prompt, then
restart normally. Once in, go and change the registry value back to what
it's supposed to be and delete the copied file. To do this, use these
commands:

C:\Windows>
C:\Windows>copy C:\Windows\system32\userinit.exe
C:\Windows\system32\wsaupdater.exe

Then you can exit once completed.

HOW TO: Install and Use the Recovery Console in Windows XP [Q307654]
http://support.microsoft.com/?kbid=307654

This can also be done by using the 6 disk boot floppy set mentioned in the
above article, as it loads enough of the Recovery Console so that you can
copy the file. This is particularly useful if you have an OEM installation
that includes only a Restore CD, or no disk at all.

--
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

"Mark Hanson" <marsonkhan@aol.com> wrote in message
news:1f2701c4ac6d$25a4da30$a601280a@phx.gbl...
> After running a round of Symantec antivirus, I found that
> at the next reboot, whenever I click a user logo to login,
> the user wallpaper flashes briefly, then logs off again.
> No error message or any other indication occurs. This
> happens for all 3 users. Help!
>
> Thanks!
> -- MBH
 

gattu

Distinguished
Jun 2, 2009
1
0
18,510
I had the same problem with my Windows laptop. After struggling with it for an entire day (trying all variations of the solution posted above), I found out (using this Registry browser) that in the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

the Userinit string value was

C:\WINDOWS\userinit.exe

Copying my userinit.exe file from the WINDOWS\system32 folder to WINDOWS folder solved the problem for me.

I used the Knoppix Live CD (which has NTFS write support) for copying the userinit.exe file to the folder. I had to do this because, for some reason, I could not login to the administartor account in the Windows Recovery Console with my blank password.

Hope this helps.

--
Gattu