Re: Stuck in logoff loop

message from Locke Nash Cole on 07 Jun 2004
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon

There has be a string value under there "Userinit" and it should be
C:\WINDOWS\system32\userinit.exe

I dont know if you can fire up XP's recovery console via the CD and use
regedit or not to fix it.. I use a tool called ERD Commander which is
basically Win XP on a cd you can boot from to fix non-working systems...
good luck!

-L

"Gregg Cattanach" <gcattanach-SKIP-@prodigy.net> wrote in message
news:5GNwc.24601$Ab1.23218@newssvr31.news.prodigy.com...
 
Gregg Cattanach replied to Locke Nash Cole on 07 Jun 2004
Where can I get this ERD Commander? I'm still stuck. The XP recovery
console doesn't seem to give me access to regedit.exe .

Gregg C.

"Locke Nash Cole" <junkmauler@hotmail.com> wrote in message
news:vjOwc.18751$%F2.3374@attbi_s04...
 
Diogenes replied to Gregg Cattanach on 07 Jun 2004
No, it doesn't. It's not a Recovery Console command. Maybe the instructions
in "Part One" of this link to repair the registry will help.
 
Diogenes replied to Diogenes on 07 Jun 2004
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545

(Oops!)
 
roger replied to Gregg Cattanach on 06 Jun 2004
Hi
From a recent post:

"Blazefind changes the following registry-key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\userinit.exe,"

in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\wsaupdater.exe,"

Used Lavasoft Adaware to get rid of the pest ----> removed blazefind
and
with it the wsaupdater.exe

==> next time i tried to logon my computer the system tries to run
wsaupdater.exe which it couldn't find ! FAILED LOGON -> LOGOFF

I first tried to find ways to change the registry from within the
recovery console but i did not succeed (ERD commander will probably
work, but since i wasn't sure that this was the problem i thought it a
little bit too expensive)...
Then i thought of this:
just copy userinit.exe as wsaupdater.exe !! It's as simple as that....

YES!! it works again... and blazefind is gone (it seems.... :-) )"

Using the recovery console employ the command

copy C:\Windows\System32\userinit.exe
C:\Windows\System32\wsaupdater.exe

(this is one line separated by a space, supposing the partition where
windows is installed is C, and supposing blazefind caused this)

Good luck
 
Gregg Cattanach replied to roger on 07 Jun 2004
This worked excellently!! Much easier than all that complicated stuff about
booting into Linux. It was the blazefind spyware that goofed up the
registry, so that let me get booted up then I could fix the registry from
there.

Ad-aware deletes the wsaupdater.exe file, but DOESN'T correct the registry
change made, so it tries to boot up with a nonexistant exe file.

Gregg C.
 
roger replied to Gregg Cattanach on 07 Jun 2004
Hi,

I'm glad it worked :-)
Now you can use regedit to repair the registry entry so that it points
to the correct userinit.exe

HTH
 

Archived message: Re: Stuck in logoff loop (Microsoft Win XP)