XP sends me back to the login screed after I login

[Guest]

I'm running XP Home Edition, SP2, on a Sony Vaio

For the last few months, whenever I login, I can see my desktop for a few
seconds, and then XP sends me back to the login screen. When I login the
second time, I'm in for good. This doesn't happen all the time, just most of
the time.

I seldom logout, I simply have the screen saver reauthenticate me, so its'
probably the authentication that I'm logging into first.

Is there any rational explanation for this behavior, or any fix?

Cheers, Eric

 

[WTC]

I'm running XP Home Edition, SP2, on a Sony Vaio

For the last few months, whenever I login, I can see my desktop for a few
seconds, and then XP sends me back to the login screen. When I login the
second time, I'm in for good. This doesn't happen all the time, just most
of
the time.

I seldom logout, I simply have the screen saver reauthenticate me, so its'
probably the authentication that I'm logging into first.

Is there any rational explanation for this behavior, or any fix?

You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

--OR--

The problem may be an incorrect system drive letter. With a networked
machine, open the registry and connect to the problematic machine and
navigate to:

[MACHINE_NAME\HKLM\SYSTEM\MountedDevices]

and delete all values that look like this:

\DosDevices\C
\DosDevices\D
\DosDevices\E
and so on

When finished, make sure you disconnect the machine from the registry. There
are other ways to gain access to the registry if you cannot connect to the
problematic machine via networked Registry. Please let me know if you need
information on how to gain access to the Registry if you cannot by a
networked registry.

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/?kbid=223188

 

[Guest]

--
Eric Kolotyluk
Software Developer

I'm running XP Home Edition, SP2, on a Sony Vaio

For the last few months, whenever I login, I can see my desktop for a few
seconds, and then XP sends me back to the login screen. When I login the
second time, I'm in for good. This doesn't happen all the time, just most
of
the time.

I seldom logout, I simply have the screen saver reauthenticate me, so its'
probably the authentication that I'm logging into first.

Is there any rational explanation for this behavior, or any fix?

You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

--OR--

The problem may be an incorrect system drive letter. With a networked
machine, open the registry and connect to the problematic machine and
navigate to:

[MACHINE_NAME\HKLM\SYSTEM\MountedDevices]

and delete all values that look like this:

\DosDevices\C
\DosDevices\D
\DosDevices\E
and so on

When finished, make sure you disconnect the machine from the registry. There
are other ways to gain access to the registry if you cannot connect to the
problematic machine via networked Registry. Please let me know if you need
information on how to gain access to the Registry if you cannot by a
networked registry.

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/?kbid=223188

Theres a bunch of entries from \DosDevices\A: to \DosDevices\J:

I'm kind of reluctant to modify registry entries unless I know what they are
for. Why are they there in the first place?

Cheers, Eric

 

[WTC]

message

I'm running XP Home Edition, SP2, on a Sony Vaio

For the last few months, whenever I login, I can see my desktop for a
few
seconds, and then XP sends me back to the login screen. When I login
the
second time, I'm in for good. This doesn't happen all the time, just
most
of
the time.

I seldom logout, I simply have the screen saver reauthenticate me, so
its'
probably the authentication that I'm logging into first.

Is there any rational explanation for this behavior, or any fix?

You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

--OR--

The problem may be an incorrect system drive letter. With a networked
machine, open the registry and connect to the problematic machine and
navigate to:

[MACHINE_NAME\HKLM\SYSTEM\MountedDevices]

and delete all values that look like this:

\DosDevices\C
\DosDevices\D
\DosDevices\E
and so on

When finished, make sure you disconnect the machine from the registry.
There
are other ways to gain access to the registry if you cannot connect to
the
problematic machine via networked Registry. Please let me know if you
need
information on how to gain access to the Registry if you cannot by a
networked registry.

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/?kbid=223188

Theres a bunch of entries from \DosDevices\A: to \DosDevices\J:

I'm kind of reluctant to modify registry entries unless I know what they
are
for. Why are they there in the first place?

Did you try the first article? This is mainly the cause of the system
immediately logging off when you log in.
You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

The "DosDevices" registration values are records of the drive letter for
partitions and drives including floppy and CD/DVD drives. Sometimes when you
clone/image the System drive (usually the C drive) to another hard disk, the
drive letters on the cloned/imaged hard disk are not correct which will
immediately log you off when you try to log in.

When you delete the "DosDevices" entries, the system will re-create the
"DosDevices" entries with the correct system drive letter when the
problematic computer is rebooted.

Also take a look at this article it might apply to your situation as well.
http://windowsxp.mvps.org/peboot.htm

Ramesh uses BartPE in this case to resolve the problem but you can use
Network Registry also to resolve the problem of immediately logging off when
you try to log in.

I have many documented posts that was corrected when the System boot drive
has somehow changed drive letters.

http://groups.google.ca/group/microsoft.public.windowsxp.general/msg/5084ece45db278b2?&hl=en

http://groups.google.com/group/micr...87c2f/6608ccf114e836fc?tvc=1#6608ccf114e836fc

http://groups.google.ca/group/micro...cd938/84215e5e04ffaf8b?hl=en#84215e5e04ffaf8b

And many more.

 

[Guest]

--
Eric Kolotyluk
Software Developer

message
I'm running XP Home Edition, SP2, on a Sony Vaio

For the last few months, whenever I login, I can see my desktop for a
few
seconds, and then XP sends me back to the login screen. When I login
the
second time, I'm in for good. This doesn't happen all the time, just
most
of
the time.

I seldom logout, I simply have the screen saver reauthenticate me, so
its'
probably the authentication that I'm logging into first.

Is there any rational explanation for this behavior, or any fix?

You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

--OR--

The problem may be an incorrect system drive letter. With a networked
machine, open the registry and connect to the problematic machine and
navigate to:

[MACHINE_NAME\HKLM\SYSTEM\MountedDevices]

and delete all values that look like this:

\DosDevices\C
\DosDevices\D
\DosDevices\E
and so on

When finished, make sure you disconnect the machine from the registry.
There
are other ways to gain access to the registry if you cannot connect to
the
problematic machine via networked Registry. Please let me know if you
need
information on how to gain access to the Registry if you cannot by a
networked registry.

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/?kbid=223188

Theres a bunch of entries from \DosDevices\A: to \DosDevices\J:

I'm kind of reluctant to modify registry entries unless I know what they
are
for. Why are they there in the first place?

Did you try the first article? This is mainly the cause of the system
immediately logging off when you log in.
You cannot log on to Windows XP after you remove Wsaupdater.exe
http://support.microsoft.com/?kbid=892893

The "DosDevices" registration values are records of the drive letter for
partitions and drives including floppy and CD/DVD drives. Sometimes when you
clone/image the System drive (usually the C drive) to another hard disk, the
drive letters on the cloned/imaged hard disk are not correct which will
immediately log you off when you try to log in.

When you delete the "DosDevices" entries, the system will re-create the
"DosDevices" entries with the correct system drive letter when the
problematic computer is rebooted.

Also take a look at this article it might apply to your situation as well.
http://windowsxp.mvps.org/peboot.htm

Ramesh uses BartPE in this case to resolve the problem but you can use
Network Registry also to resolve the problem of immediately logging off when
you try to log in.

I have many documented posts that was corrected when the System boot drive
has somehow changed drive letters.

http://groups.google.ca/group/microsoft.public.windowsxp.general/msg/5084ece45db278b2?&hl=en

http://groups.google.com/group/micr...87c2f/6608ccf114e836fc?tvc=1#6608ccf114e836fc

http://groups.google.ca/group/micro...cd938/84215e5e04ffaf8b?hl=en#84215e5e04ffaf8b

And many more.

The first article is not the problem, I checked the registry key and it's
correct.

I haven't cloned the systed drive (ever).

I'm not saying I can't login at all. I can definately login when I need to.
It's just that after my screen saver has kicked in and I need to
reauthenticate myself, most of the time the system starts logging me on, I
can see my desktop, and then wham, I'm back at the login screen. It never
fails to login on the second try.

I really appreciate you help, and especially quick responses, but I think
there's something flakey with the screen saver authentication. Are there any
problems you know of related to that?

Cheers, Eric

 

[WTC]

[ ]

The first article is not the problem, I checked the registry key and it's
correct.

I haven't cloned the systed drive (ever).

I'm not saying I can't login at all. I can definately login when I need
to.
It's just that after my screen saver has kicked in and I need to
reauthenticate myself, most of the time the system starts logging me on, I
can see my desktop, and then wham, I'm back at the login screen. It never
fails to login on the second try.

I really appreciate you help, and especially quick responses, but I think
there's something flakey with the screen saver authentication. Are there
any
problems you know of related to that?

Cheers, Eric

I should have read your first post in more detail. Look in the Event Viewer
for any clues. The Event Viewer is located in the Administrative Tools
folder in the Control Panel (Classic View).

Does this happen in all the user accounts? Could you create a temporary new
user account and see if the problem exist in this account??

 

[Guest]

--
Eric Kolotyluk
Software Developer

[ ]

The first article is not the problem, I checked the registry key and it's
correct.

I haven't cloned the systed drive (ever).

I'm not saying I can't login at all. I can definately login when I need
to.
It's just that after my screen saver has kicked in and I need to
reauthenticate myself, most of the time the system starts logging me on, I
can see my desktop, and then wham, I'm back at the login screen. It never
fails to login on the second try.

I really appreciate you help, and especially quick responses, but I think
there's something flakey with the screen saver authentication. Are there
any
problems you know of related to that?

Cheers, Eric

I should have read your first post in more detail. Look in the Event Viewer
for any clues. The Event Viewer is located in the Administrative Tools
folder in the Control Panel (Classic View).

Does this happen in all the user accounts? Could you create a temporary new
user account and see if the problem exist in this account??

Yes, I can see some login failures in the Security section of the event
viewer.

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: eric
Source Workstation: KOLOTYLUK
Error Code: 0xC000006A

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp

When I check out the events.asp link it says Event ID 680 is unknown. I also
get

Logon Failure:
Reason: Unknown user name or bad password
User Name: eric
Domain: KOLOTYLUK
Logon Type: 2
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: KOLOTYLUK

and the events.asp link says Event ID 529 is unknown. I'm prety sure it
wasn't the password because I never got notified of a bad password.

My wife doesn't seem to have the same problem, but then she doesn't have a
password set on her account.

Cheers, Eric

 

[WTC]

message

[ ]

The first article is not the problem, I checked the registry key and
it's
correct.

I haven't cloned the systed drive (ever).

I'm not saying I can't login at all. I can definately login when I need
to.
It's just that after my screen saver has kicked in and I need to
reauthenticate myself, most of the time the system starts logging me
on, I
can see my desktop, and then wham, I'm back at the login screen. It
never
fails to login on the second try.

I really appreciate you help, and especially quick responses, but I
think
there's something flakey with the screen saver authentication. Are
there
any
problems you know of related to that?

Cheers, Eric

I should have read your first post in more detail. Look in the Event
Viewer
for any clues. The Event Viewer is located in the Administrative Tools
folder in the Control Panel (Classic View).

Does this happen in all the user accounts? Could you create a temporary
new
user account and see if the problem exist in this account??

Yes, I can see some login failures in the Security section of the event
viewer.

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: eric
Source Workstation: KOLOTYLUK
Error Code: 0xC000006A

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp

When I check out the events.asp link it says Event ID 680 is unknown. I
also
get

Logon Failure:
Reason: Unknown user name or bad password
User Name: eric
Domain: KOLOTYLUK
Logon Type: 2
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: KOLOTYLUK

and the events.asp link says Event ID 529 is unknown. I'm prety sure it
wasn't the password because I never got notified of a bad password.

My wife doesn't seem to have the same problem, but then she doesn't have a
password set on her account.

Do you have Service Pack 2 installed? I found this info but the KB article
states that this has been fixed in Service Pack 2.

Security Event 529 is logged for local user accounts
http://support.microsoft.com/?kbid=811082

And the following KB article is for EventID 680 with an error code of
0xC000006A

Failure Events Are Logged When the Welcome Screen Is Enabled
http://support.microsoft.com/?kbid=305822

Hope this helps you help, about the best I can do for you.

 

[Guest]

Do you have Service Pack 2 installed? I found this info but the KB article
states that this has been fixed in Service Pack 2.

Security Event 529 is logged for local user accounts
http://support.microsoft.com/?kbid=811082

And the following KB article is for EventID 680 with an error code of
0xC000006A

Failure Events Are Logged When the Welcome Screen Is Enabled
http://support.microsoft.com/?kbid=305822

Hope this helps you help, about the best I can do for you.

Yes, I have SP2 installed and I have automatic update, so everything is
up-to-date. Both those links recommend updating to SP2 as a resolution, so it
doesn't look like there's much left to do.

Anyway, that again for the heroic measures at troubleshooting. I can live
with the problem, but I was curious if there was a specific reason for the
problem.

Cheers, Eric

 

[WTC]

Yes, I have SP2 installed and I have automatic update, so everything is
up-to-date. Both those links recommend updating to SP2 as a resolution, so
it
doesn't look like there's much left to do.

Anyway, that again for the heroic measures at troubleshooting. I can live
with the problem, but I was curious if there was a specific reason for the
problem.

If you create a new temporary user account and log into that account, does
the symptoms still occur?

 

[Guest]

--
Eric Kolotyluk
Software Developer

If you create a new temporary user account and log into that account, does
the symptoms still occur?

No, I can't seem to recreate the problem with another account.

Cheers, Eric

 

[WTC]

No, I can't seem to recreate the problem with another account.

Cheers, Eric

Maybe you would like to perform these actions.

How to copy data from a corrupted user profile to a new profile
http://support.microsoft.com/?kbid=811151

 

[Guest]

No, I can't seem to recreate the problem with another account.

Maybe you would like to perform these actions.

How to copy data from a corrupted user profile to a new profile
http://support.microsoft.com/?kbid=811151

I read the article, but it seems to be more trouble than it's worth. Thanks
for all your ferreting around for answers, but I'm not really suffering
because of the problem.

Cheers, Eric

 

[WTC]

I read the article, but it seems to be more trouble than it's worth.
Thanks for all your ferreting around for answers, but I'm not really
suffering because of the problem.

You're welcome Eric.