Cannot Logon

[Guest]

When I try to logon from the blue logon screen it starts logging on and then
automatically logs off before log in is complete. I just ran the microsoft
malicious software removal tool and restarted when prompted....any ideas I am
really stumped here. Thanks

 

[Pegasus \(MVP\)]

When I try to logon from the blue logon screen it starts logging on and then
automatically logs off before log in is complete. I just ran the microsoft
malicious software removal tool and restarted when prompted....any ideas I am
really stumped here. Thanks

There are a couple of reasons why this might happen. Here
is a simple method that will sometimes fix the problem:
1. Boot the machine with your WinXP CD.
2. Select Repair, then Recovery Console.
3. Type this command:
fixmbr

If this does not fix the problem then the cure depends on
your setup. Is the machine networked? Is it a desktop or
a laptop? Do you have ready access to another WinXP/2000
desktop PC?

 

[Guest]

Thanks for the suggestion....unfortunately it did not fix the problem. I do
have access to a laptop with win xp. not networked yet, getting ready to set
up wireless network. Any other suggestions? any help is appreciated

 

[Pegasus \(MVP\)]

Your problem could be one of the following:
- Incorrect system drive letter. To fix this you must edit the registry.
- Missing userinit.exe. To fix this you must gain access to your hard disk.
- Incorrect registry link to userinit.exe. To fix this you must edit the
registry.

All of the above are fairly easy for a networked PC and much,
much harder for a stand-alone PC, requiring specialised tools.
Unless you are experienced in such matters I recommend that
you ask someone who is suitably qualified to assist you.

I assume that you have already tried to boot in Safe Mode and
that it made no difference.

 

[Guest]

Thanks again...I will try accessing the computer when I get the wireless
network going. I'll let you know how I did, lol

 

[Michael D. Alligood]

As Pegasus suggested but in greater detail. Another solution that solved
this issue for me was simply doing a repair install of the OS.

1. Navigate to
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon"

2. If there is a key named "OldUserinit", delete the "Userinit" key and
rename the "OldUserinit" key to "Userinit".

3. The "Userinit" key should now say
"WINDOWS_PATH\system32\userinit.exe,"

"WINDOWS_PATH" is relative to where you have your windows installed.
Mine would be "C:\WINDOWS\system32\userinit.exe,"

You could also do:

1.- Get into the recovery console (with boot disks, you can get them
from microsoft page).

2.- Get the file userinit.exe from another NOT INFECTED computer.
(located in windows/system32 folder)

3.- Overwrite the userinit.exe original file (from the infected
computer) with the new one (use a cd or disk to transport it) (COMMAND:
COPY e:/userinit.exe c:/windows/system32/userinit.exe)

4.- Rename the userinit.exe to wsaupdater.exe


--
Michael D. Alligood,
MCSA, MCDST, MCP, A+,
Network+, i-Net+, CIW Assoc.,
CIW Certified Instructor

 

[Pegasus \(MVP\)]

I can't quite see how you can get wireless networking going unless
you can log into your PC . . .

 

[Pegasus \(MVP\)]

As Pegasus suggested but in greater detail. Another solution that solved
this issue for me was simply doing a repair install of the OS.

1. Navigate to
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon"

2. If there is a key named "OldUserinit", delete the "Userinit" key and
rename the "OldUserinit" key to "Userinit".

3. The "Userinit" key should now say
"WINDOWS_PATH\system32\userinit.exe,"

"WINDOWS_PATH" is relative to where you have your windows installed.
Mine would be "C:\WINDOWS\system32\userinit.exe,"

Mmh. If a repair installation fixes the OP's problem then he
won't need to edit the registry. If he does NOT perform a
repair installation then he can't edit the registry. Your instructions
are good but I cannot see how the OP could use them.

 

[Michael D. Alligood]

Yeah I see how that could be confusing. I was really just continuing
with your train of thought and what has worked for me in the past. After
looking through my Tech Journal that I keep, it seems that the PC
license may be deactivated. I the past, there was an issue with the
OOBE. Again, the only way I was able to fix this particular issue was to
do a repair install. Sorry for the confusion!

--
Michael D. Alligood,
MCSA, MCDST, MCP, A+,
Network+, i-Net+, CIW Assoc.,
CIW Certified Instructor