Problem with Antispyware Beta1

  • Thread starter Thread starter Dwaggie67
  • Start date Start date
D

Dwaggie67

I installed Antispyware Beta1 two months ago and ran it with no problems.
And then when May rolled around when I start Antispyware Beta1 it
keeps putting up the setup assistant everytime I start it up.
I did a clean uninstall of the software and deleted all traces of it from my
machine, then I downloaded a new copy of Antispyware Beta1
and it still dose the setup assistant everytime I start it. And it keeps
saying the Antispyware AutoUpdater In-active. I keep turning it on.
But as soon as I restart my computer and try to run Antispyware Beta1
I have to do it all over again. and that setup assistant comes up again too
And it keeps saying Antispyware AutoUpdater In-active.Then I enable it once
more.Then when I restart my computer the next time,I have to do it all over
again. Quite frankly I think you have a bug in your
Antispyware Beta1 software that needs attention. So what's going on?

~ Dwaggie67
 
I'm running Windows XP Home Edition (SP2)
Windows XP firewall and Sygate Personal Firewall.
Spybot S&D (I got the latest updates)
AdawareSE (I got the latest updates)
Norton anti-virus (I got the latest updates)
I have all the windows updates installed

~ Dwaggie67
 
Dwaggie67 said:
when I start Antispyware Beta1 it keeps putting up the setup assistant
everytime I start it up.
Click to expand...

This is normally a problem with the Installer configuration, not of
AntiSpyware itself.

What is the "setup assistant" trying to do when it starts up? This is
important to know.

You might find this helpful:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
but beware that you will have to resintall something if you clean up its
installation configuration.
 
Since you are running Sygate PF, turn off XP firewall.
Sometimes running 2 different can cause problems
possiblely the setup problem you are having.
 
Interesting--thanks blkwlnt64--and thanks for letting us know. I know that
running the two firewalls will sometimes obscure the source of traffic, or
of an alert--but this is the first time I've really seen it as an issue that
caused a significant problem. Were you blocking traffic from ALG--the
Application Layer Gateway service?
 
Back
Top