I am not really sure what a nag screen is, could you elaborate? I do not
have spy catcher and do believe it was just the security update for Microsoft
that caused this problem. I am the only user and usually catch many problems
before they arise. If you could let me know what you did to the two machines
that didn't have spy catcher (my brain is very slow these days so please
"talk" slowly)
thanks in advance for your help.
Regards,
Steve
"Shell" wrote:
> Hi Steve,
>
> I never did get a response, but I did find two causes and depending on the
> cause, I found two fixes. First the cause, then fix.
>
> The first cause I found was due to a very good anti-spy program from
> Tenebril called SpyCatcher (SC). On many of the problem computers, SC was
> installed. On those comps where I could get to Safe Mode, I would uninstall
> SpyCatcher. This caused SC to replace any "Ask" or some disabled things, like
> anything the user was prompted for right after an automatic update by
> Windows. A reboot and everything was back to normal, including some spyware.
> SpyBot beat them off.
>
> On two comps, there was no SpyCatcher. I suspect the user disabled something
> or the security update botched it and mistook a legit XP for a illegal one,
> tried to run the nag screen and without it, jumped back to the logon screen -
> sort of like the Shutdown on Win98/SE wouldn't shutdown if it couldn't find a
> sound file or splash screen. In the XP case looks like it can't find the nag
> screen.
>
> That aside, on the other two comps, I UNinstalled the and it's anti-spyware
> too. Then I did a non-destructive restore, after a lot of grief backing up
> all pertinent files. Whether the anti-spyware played a roll - who knows.
>
> IMPORTANT NOTE: I doubt it was coincidence that SpyCather and loopy-logon
> co-habitated. I did talk with Tenebril and they asured me a new version was
> out and that the information I passed along went to their techies. I have
> since re-installed their SpyCatcher and haven't had any grief since.
>
> S
>
>
>
> "Steve" wrote:
>
> > hi,
> > I was wondering if you ever got an answer that resolve this problem. I now
> > have the exact same problemand of courseHave not backed up recently.
> >
> > Thank you for your help.
> >
> > Regards,
> > Steve
> >
> > "Shell" wrote:
> >
> > > This scenario is the same on 7 computers (9 now) - all XP of course. That,
> > > without
> > > rhyme or reason, when the computer is booted and clicking on a User icon to
> > > login, no password box appears, and instead, the message "Loading your
> > > personal settings" appears, the desktop, the default one, blinks on for 3
> > > seconds, off and back to login screen where the message "Saving your personal
> > > settings" appears and then nothing. The same can be repeated on a computer
> > > with multiple users, one user and in the case where there was never a login
> > > screen, suddenly there is a login screen using the Owners name - with same
> > > login results, a loop.
> > >
> > > I have seen this on 7 computes over the last 4 weeks. My sons, daughters,
> > > mine, and some friends. Each comp is a either Dell, a Compaq, and 1 Gateway.
> > >
> > > None have shared files, except a couple with email but no attachments except
> > > for a jpeg. Of note is that several occurred right AFTER a security patch
> > > notice to upgrade, and they did. Completed some tasks and shut down the comp.
> > > On boot up next day, the loopy login appeared.
> > >
> > > As a semi-expert, I did all the necessary spyware tests using Spybot,
> > > Spycatcher, and Hijackthis and Adaware. Did anti-virus scans, and anti-Trojan
> > > program scans.
> > > I followed some articles online about replacing kernel32 from Org CD,
> > > getting in via command panel, removing users rebooting, creating new users
> > > and all the such.
> > >
> > > On each, I can get in via Safe Mode Admin. I can get the command prompt.
> > >
> > > There is ONE article on the net suggesting that MS latest security patch
> > > looks to see if the OS is cert or not and if not, does the login loop. If
> > > this be the case, MS should fix the patch cause it's making mistakes BIG time!
> > >
> > > Else - what is causing this looping login? Help please TIA
> > >
> > >