It logs me out

B

Braz

Help
When I sign into Windows XP Home on the welcome page it
flicks to my desktop then goes straight to 'saving your
settings....
I cannot get in
 
G

Guest

I am having the same problem. Does anyone have any
answer for this. I would really appreciate it!

Thanks
 
M

Mike

I too am having this same problem - I ran Adaware spyware
removal tool and i think it removed something important
because it does exactly what Braz refers to below: it logs
in and immediately logs out and saves settings. i have
tried to start in safe Mode to log on and the same occurs.

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

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