G
Guest
I have a (Dell Dim 8200) machine running XP Home SP2 with all critical
updates in place. When I start it, after the black logo splash screen, I get
a message that Windows could not log on to the administrator account because
the password or domain was incorrect (or words to that effect). I am
presented with an OK button and when I press it, I am presented with the
normal logon screen with my single user listed. From there, I can log on
normally. However, sometimes the error message (above) simply flashes with
an accompanying beep, and the machine goes to the blue "Starting Windows"
screen, where it hangs until the screen saver comes on (10 minutes). At that
point, if I move the mouse or touch a key to exit the screen saver I get the
normal logon screen and can proceed normally.
This machine was discussed with a Dell tech, and since has had a "repair"
install of XP. I have the feeling that this behavior is the result of a
hijack attempt that has been removed, but I cannot find it. Numerous scans
declare the machine clean at this time. I assume the behavior is the result
of a change in the logon instructions, but don't know where/how to repair it.
I'm comfortable with registry editing. Any suggestions?
updates in place. When I start it, after the black logo splash screen, I get
a message that Windows could not log on to the administrator account because
the password or domain was incorrect (or words to that effect). I am
presented with an OK button and when I press it, I am presented with the
normal logon screen with my single user listed. From there, I can log on
normally. However, sometimes the error message (above) simply flashes with
an accompanying beep, and the machine goes to the blue "Starting Windows"
screen, where it hangs until the screen saver comes on (10 minutes). At that
point, if I move the mouse or touch a key to exit the screen saver I get the
normal logon screen and can proceed normally.
This machine was discussed with a Dell tech, and since has had a "repair"
install of XP. I have the feeling that this behavior is the result of a
hijack attempt that has been removed, but I cannot find it. Numerous scans
declare the machine clean at this time. I assume the behavior is the result
of a change in the logon instructions, but don't know where/how to repair it.
I'm comfortable with registry editing. Any suggestions?