MSAS and Norton Internet Security 2005

  • Thread starter Thread starter Stuart James
  • Start date Start date
S

Stuart James

If this question has been posted before, please accept my
apologies.

I hope that someone can help, I have NIS 2005 and
installed MSAS, after installing MSAS my firewall is
turned off and NIS requests my to reactivate my already
licenced copy. If I uninstall MSAS all is fine however
reinstall MSAS firewall is disabled and NIS requests
reactivation which having attempted numerous times
resulted in me contacting Symantec to get my product
reactivated.

I have tried this on 2 machines both running XP SP2 with
all the available updates with the same results,
according to Symantec they are aware of this problem and
have suggested not re-install MSAS at this time.

As everyone else on this newsgroup appears to have no
problem, could anyone help or offer advice please?
 
We're familiar with an issue where, upon removing spyware, the winsock LSP
stack is disrupted by the removal, necessiitating resetting of the LSP
stack, and, in some cases, reinstallation of third party software which uses
the LSP stack.

This is quite different from your situation in which you describe the simple
actions of installing and uninstalling as creating these symptoms, and
making them go away.

We've also had many other users of NIS 2005 post here, and I've tested a
beta version of this myself first hand--and haven't seen this issue.

So, I don't know what to make of your experience, which I'm not
doubting--hence at least a small part of the silence that is greeting your
post.
 
Hi Bill

Thank you for responding, fortunately neither of my
machines appear to have had any spyware, other than
cookies when needed. Although MSAS has not found anything
at all usage tracks and cookies have been found when
using Adaware SE Pro and Spybot, which obviously MSAS is
not designed to do in the Beta.

I like the features within MSAS and hope that this is
only a minor nug that can be located and rectified when
the full release version comes out.

Once again thank you for your response.

Regards
 
My experience on the vast majority of machines I administer is like
yours--but I have a particular small office which makes up for all the rest
in their ability to show the usefulness of Microsoft Antispyware as a
cleaning tool.

There will be an update of some sort before July 31. You might wish to try
that code to see whether it changes this behavior on your machine(s.) This
won't be beta2, and I've no reason to think that whatever is causing your
issue will have changed, but there will be some changes to the code, so I
think it'd be worth a quick check.

Folloing that, at some later date will be beta2. If your issue still exists
with beta2, it'd be important to try to get it replicated if possible.

Thanks again for your report, sorry it isn't working for you, and thanks for
testing

--
 
Once again Bill thank you for your response.

I will take your advice and await the update prior to
July 31st.

When I try the update I will email you to keep you
informed.

Thank you again.
 
Back
Top