XP Won't Log-In; returns Me to Welcome Screen

B

bPstyles

Okay, the problem is: When I start my computer (laptop) it goes thru the
loading of Win XP, you know, the screen with the little bar. Then it shows
the welcome screen as normal, and since I am the only account/person on my
computer it goes right to my dsktop. Only now it shows teh desktop, or
rather just the wallpaper, for a split second and then goes to the welcome
screen and shows my account on there like it would if you have numerous
accounts or an account with a password. Not a big deal, so I click on it,
and it does the same thing. Shows the desktop for a split second and goes
back.
I've tried shutting it down, restarting it, putting it on standby. I've
tried starting it in safe mode, booting off the CD. I've tried it without
anything plugged in, I've tried pushing Ctrl+Alt+Del to get the 'old' style
of log in box, then I hit Cancel and it just goes back to the Win XP Welcome
screen.

So does anyone have any idea what is wrong and how I would fix it? I would
like to do it with out reinstalling windows and deleing my whole hard drive,
but I guess if it comes to that I have to do it.

Thanks.
 
B

bPstyles

Taurarian said:
http://support.microsoft.com/?kbid=313322
A User Logon Request Is Rejected Without Any Messages

http://www.winxptutor.com/wsaremove.htm
Quick Launch settings are not saved; Search Assistant Toolbar in Taskbar
Unable to logon to Windows after removing BlazeFind using a spyware removal utility?
Logon - Logoff loop, also caused by BlazeFind

Restore Winlogon\Userinit
http://www.kellys-korner-xp.com/xp_wel_screen.htm

Thank you...other than the Blazfind one, I haven't tried these.
 
L

Larry Samuels

Thanks go to Rick Rogers, MVP for the following instructions:

Did you run a spyware removal program 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.

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.



--
Larry Samuels MS-MVP (Windows-Shell/User)
Associate Expert
Expert Zone -
Unofficial FAQ for Windows Server 2003 at
http://pelos.us/SERVER.htm
 
B

Bubba

Thanks from myself also. You saved my kids system. I saw this once
before, and couldn't remember the fix.

Brian



Larry Samuels said:
Thanks go to Rick Rogers, MVP for the following instructions:

Did you run a spyware removal program 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.

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.



--
Larry Samuels MS-MVP (Windows-Shell/User)
Associate Expert
Expert Zone -
Unofficial FAQ for Windows Server 2003 at
http://pelos.us/SERVER.htm


bPstyles said:
Okay, the problem is: When I start my computer (laptop) it goes thru the
loading of Win XP, you know, the screen with the little bar. Then it
shows
the welcome screen as normal, and since I am the only account/person on my
computer it goes right to my dsktop. Only now it shows teh desktop, or
rather just the wallpaper, for a split second and then goes to the welcome
screen and shows my account on there like it would if you have numerous
accounts or an account with a password. Not a big deal, so I click on it,
and it does the same thing. Shows the desktop for a split second and goes
back.
I've tried shutting it down, restarting it, putting it on standby. I've
tried starting it in safe mode, booting off the CD. I've tried it without
anything plugged in, I've tried pushing Ctrl+Alt+Del to get the 'old'
style
of log in box, then I hit Cancel and it just goes back to the Win XP
Welcome
screen.

So does anyone have any idea what is wrong and how I would fix it? I
would
like to do it with out reinstalling windows and deleing my whole hard
drive,
but I guess if it comes to that I have to do it.

Thanks.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top