Re: Login Immediately Loggin Off
- From: sailmonsoon <bill@xxxxxxxxxxxxxx>
- Date: 9 May 2007 01:55:26 -0700
On May 9, 8:04 am, "Pegasus \(MVP\)" <I...@xxxxxxx> wrote:
"sailmonsoon" <b...@xxxxxxxxxxxxxx> wrote in message
news:1178692669.378957.177960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello to all my readers!
"All of a sudden" my system started loggin off immediately after I
login. The login message box says "loading settings" then quickly
changes to "logging off" then after awhile says "closing network
connections" then the login window returns.
A lot of people have reported having this problem. The only solution
offered by other poeple and websites is when this problem has been
caused by "wsaupdater.exe" replacing "userinit.exe" by a registry
setting change. This is caused by an obnoxious malware BlazeFind
related to Internet Explorer. (I don't use IE!) (The people who
distribute this should be ... punished.)
I am experiencing this problem, but none of the symptoms of
BlazeFind. None of the files associated with BlazeFind are located on
my computer, at least not in c:\windows or c:\windows\system32.
I can only access the hard disk by using the Recover Console.
No boot option changes the situation: Safe Mode, Admin Login ... is
there anything else?
The ntbtlog.txt doesn't show anything abnormal.
I have "played" with (renamed) the hive files in c:\windows
\system32\config (DEFAULT, SAM SOFTWARE, SYSTEM. SECURITY), but that
inhibited the boot process completely.
I tried to look at the FireFox install directory, located in c:
\Program Files, but the Recovery Console does not have access to that
folder. Is there a special way to go to that directory?
Does anybody know of another cause of this problem ... and the
solution? A lot of people are experiencing it, if a google search is
any indication. I would like to avoid reloading from a backup,
because it is about one month old, but if there is no joy I will.
My system is "Windows XP Pro sp2".
This post of long enough. I hope someone can help.
Cheers!
Bill Westphal in New Zealand
The "userinit" cause you mention is one of several possible causes, i.e.
- userinit.exe does not exist.
- userinit.exe is corrupted.
- the system drive letter has changed and userinit is not where Windows
expects it.
- the registry entry for userinit.exe is incorrect.
The cure is simple if the machine is networked, harder if you can
temporarily install its disk in some other WinXP/2000 PC and
very hard if neither of the above apply. What is it in your case?
It's networked (at home, not on a Windows Domain).
I checked for, and found "userinit.exe". I compared it to the copy of
it located in the c:\i386 folder, and it had the same file size and
date. I know, it can stil be corrupted. I will copy the i386 version
to the c:\windows\system32 folder.
The system in question is a laptop, and I don't have another Windows
XP machine here (I have several "other" machines; Solaris, Linux,
Tru64), but I could go to a location that does have more Windows
resources. What is the network "cure"? Is the machine still
accessable via the network even though a use is not logged in? How?
Terminal Services?
What is the cure in the 2nd case?
Thanks for your response.
Bill
.
- Follow-Ups:
- Re: Login Immediately Loggin Off
- From: Pegasus \(MVP\)
- Re: Login Immediately Loggin Off
- References:
- Login Immediately Loggin Off
- From: sailmonsoon
- Re: Login Immediately Loggin Off
- From: Pegasus \(MVP\)
- Login Immediately Loggin Off
- Prev by Date: Re: bios problem
- Next by Date: Regarding Registry setting!!!
- Previous by thread: Re: Login Immediately Loggin Off
- Next by thread: Re: Login Immediately Loggin Off
- Index(es):
Relevant Pages
|