Re: Login Immediately Loggin Off
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Thu, 10 May 2007 08:56:32 +1000
"sailmonsoon" <bill@xxxxxxxxxxxxxx> wrote in message
news:1178748053.441391.163210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 9, 6:37 am, sailmonsoon <b...@xxxxxxxxxxxxxx> wrote:
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
PROBLEM SOLVED ... CAUSE STILL UNKNOWN.
The solution was to copy in an older version of the Registry Hive. The
steps taken were somewhat frustrating.
1. Boot to a Recovery Console. Navigate to %Systemroot%
\system32\config. Rename the files DEFAULT, SAM, SECURITY, SOFTWARE,
AND SYSTEM, eg. add ".bad" extension to each name.
2. Reboot the system to a Recovery Console. This time the console
should NOT ask you for an administtrator password. If you do not
perform step #1 then you will not have access to the "c:\System Volume
Information" folder. Navigate to the "c:\System Volume Information"
directory. There should be a folder here whose name begins with
"_restore{" . It's a very long folder name, unique to every system.
Change to this folder and Copy these files to c:\windows
\system32\config: _RESTORE_MACHINE_SAM, _RESTORE_MACHINE_SECURITY,
_RESTORE_MACHINE_SOFTWARE, _RESTORE_MACHINE_SYSTEM, and
_RESTORE_USER_.DEFAULT. Then navigate to c:\windows\system32\config
and rename the copied files to SAM, SECURITY, SOFTWARE, SYSTEM, and
DEFAULT, respectively.
3. Reboot your system normally. It should proceed as it did before
the problem occurred. I haven't noticed any missing files or
different settings.
MY next step is going to be to make a current, FULL backup. Then I
will make a bootable, rescue CD.
Thank you, Pegasus, for responding.
I would shure like to know what caused this, but I have no time to
investigate. Is there any way to look at the registry entries in the
BAD Hive? Without enabling it or making it live?
Cheers!
Bill Westphal
"Go, Team New Zealand. Bring back the America's Cup!"
Thanks for the feedback.
Regedit.exe lets you open an off-line registry hive.
I recommend a Bart PE boot CD as a rescue CD. It's worth the
effort to make it.
On my machines I have a scheduled job that runs once each week.
It invokes regback.exe (Windows Resource Kit) so that I have at
all times thre copies of my registry files: The live copy, the most
recent backup copy and the one before. This lets me resolve your
type of problem within a few minutes.
.
- References:
- Login Immediately Loggin Off
- From: sailmonsoon
- Re: Login Immediately Loggin Off
- From: sailmonsoon
- Login Immediately Loggin Off
- Prev by Date: Re: Send to mail recipient
- Next by Date: Re: Login Immediately Loggin Off
- Previous by thread: Re: Login Immediately Loggin Off
- Next by thread: Re: Login Immediately Loggin Off
- Index(es):
Relevant Pages
|