Xp log-on then log-off

I was able to fix the issue by using the Load Hive method ..

The problem was in the "Software" hive...

The userinit key was pointing to a file called xwushzh.exe which of course
no longer existed...

problem solved..

By the way the issue came from My Space web site

Just a note this little file deleted the userinit.exe file itself.. and
changed the key... when Norton stopped it, it had already done some damage.
After Norton deleted the file xwusuhzh.exe, the registry key remained...
thus when trying to log-on, it would immediately log off... even though the
file .exe was no longer there, replacing only the userinit.exe file with a
known good one it still wouldn't work... could not get into any repair
mode... had to slave drive into another PC using the USB-Sata adapter, then
open the hive on the bad drive and edit the line in the software key... as
mentioned...

Thanks for the help...

"JF" <JF@-> wrote in message news:%23R8y5tfBJHA.3496@TK2MSFTNGP03.phx.gbl...
> *Bonjour John John (MVP) * !
> <news:#StyM$eBJHA.4108@TK2MSFTNGP05.phx.gbl>
>
>> JF wrote:
>
>> > Try with no path
>>> HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
>>> Userinit=userinit.exe
>
>> There is a comma missing in your registry edit, this will cause userinit
>> to fail.
>
> It works without the comma but the use is to keep it.
> So you can start other programs with :
> userinit=userinit.exe, goodprogram.exe, badvirus.exe,
>
>
>> I don't know what removing the path will do, maybe you know something
>> that I don't.
>
> Simply that it works without the path.
> So you eliminate a possibly mistake as explained here
> http://support.microsoft.com/kb/249321
>
>
> Remember Pegasus said :
> "Windows is unable to locate userinit.exe,
> probably because your system drive letter has changed"
>
>
>
>> Typically the value should be:
>> C:\WINDOWS\system32\userinit.exe,
>
> Yes, typically Windows is on C:\ and is called Windows.
>
>
>> There are other causes for this reboot loop or boot failure, Pegasus will
>> no doubt review the different causes and suggest appropriate measures to
>> fix things.
>
>> John
>
>
> Since Tim said "the 'Windows NT' key only had 3 entries in the key" the
> only thing possible seems to get a better hive from the SVI, or repare
> Windows.
>
> Also a simply CHKDSK /R from the Recovery Console is not a bad idea.
>
> --
> Regards, Jean-François
>
>

*Bonjour Tim_S * !
<news:eGRBLzJCJHA.3496@TK2MSFTNGP03.phx.gbl>

> I was able to fix the issue by using the Load Hive method ..

> The problem was in the "Software" hive...

> The userinit key was pointing to a file called xwushzh.exe which of course
> no longer existed...

> problem solved..

> By the way the issue came from My Space web site

> Just a note this little file deleted the userinit.exe file itself.. and
> changed the key... when Norton stopped it, it had already done some damage.
> After Norton deleted the file xwusuhzh.exe, the registry key remained... thus
> when trying to log-on, it would immediately log off... even though the file
> .exe was no longer there, replacing only the userinit.exe file with a known
> good one it still wouldn't work... could not get into any repair mode... had
> to slave drive into another PC using the USB-Sata adapter, then open the hive
> on the bad drive and edit the line in the software key... as mentioned...

> Thanks for the help...

Thanks for the feed back.
Bravo et Félicitations ! ^^

--
Regards, Jean-François