Get logged out immediately after logging in

[LarryBoy]

No users on my daughter's XP machine can log in without
the system immediately automatically logging them back
out. You pick a user, type the password, hit enter, see
that user's wallpaper for a fraction of a second, then
see "saving settings" and you're back at the main XP
login screen. I tried it with her account, with guest,
and with local administrator. I also tried booting in
safe mode, but always saw the same symptoms.

Someone else had a similar problem and it was attributed
to a log filling up, and having too big a number in
the "purge after N days setting". They were able to fix
it by logging in as administrator, but I can't even do
that.

TIA for any suggestions if only how to rescue data before
flattening and rebuilding.

 

[Taurarian]

http://www.winxptutor.com/wsaremove.htm
Quick Launch settings are not saved; Search Assistant Toolbar in Taskbar
Unable to logon to Windows after removing BlazeFind using a spyware removal utility?
Logon - Logoff loop, also caused by BlazeFind

Restore Winlogon\Userinit
http://www.kellys-korner-xp.com/xp_wel_screen.htm



or look at the previous newsgroup posting:
http://groups.google.com/groups?hl=...=1&[email protected]

 

[LarryBoy]

Thanks a million!! That article on winxptutor.com was
exactly what I needed. A related article in LavaSoft's
knowledgebase says essentially the same thing, but seems
to be suggesting that the problem occurs specifically
with Ad-Aware signature files from last June. This
obviously bit us while using a much more recent signature
file. I don't know exactly which one we were using any
more, but it had to be from this month.

Thanks again!

-----Original Message-----
http://www.winxptutor.com/wsaremove.htm
Quick Launch settings are not saved; Search Assistant Toolbar in Taskbar
Unable to logon to Windows after removing BlazeFind

using a spyware removal utility?

 

[Taurarian]

You're welcome.
Kaylene

Thanks a million!! That article on winxptutor.com was
exactly what I needed. A related article in LavaSoft's
knowledgebase says essentially the same thing, but seems
to be suggesting that the problem occurs specifically
with Ad-Aware signature files from last June. This
obviously bit us while using a much more recent signature
file. I don't know exactly which one we were using any
more, but it had to be from this month.

Thanks again!

using a spyware removal utility?