Paul wrote:

Emrys Davies wrote:

"Paul" wrote in message
news
Emrys Davies wrote:

Your Avast spam is back again!

I had disabled it and now I found that it is back again. I went to
its Menu again Settings un-ticked relevant box Clicked OK. We
will see what happens now.

When software is re-installed, or there is a major version
update, the settings can be reset.

It's not necessarily easy to see this, if the software is
sneaky in any case.

Paul


Sometimes I use 'Restart' to make sure that a disable or enable is
definitely effective. Could that cause a reset rather than reinforcing
the desired action?

I would think a new version of Avast installing itself,
would do this.

I just uninstall (well, actually never install) the superfluous Mail
module to eliminate any problems caused by it: inane spam signatures in
e-mail or newsgroups, timeouts between client and server due to
interrogation of e-mail and NNTP traffic, errors in the client when the
transparent proxy for the AV becomes unresponsive (user see errors in
the client but the problem is with the AV's proxy), etc. There is no
additional malware detection coverage by the Mail module which uses the
same engine as the on-demand (real-time) scanner. It's a means of an AV
vendor to bloat the feature set of their product: look, we cover this
infection vector, and that one, and this other one, and ...

New installs of Avast do not forcibly alter the current configuration;
however, you may need to perform a custom installation. Anyone clicking
through the installer's screens as fast as they can without reading
those screens gets whatever the software vendor wants that user to have,
and that means a lot of bloatware and possibly a lot of bundleware or
spamware, too.

I've done signature updates. That's just a database update. I've done
program updates. Those can affect the heuristics employed by the AV to
detect behaviors of events on the computer and add/delete/modify the
feature set. I've not had program updates alter which modules were
selected during the initial installation. The program updates have also
not affected my settings within each module; however, a module that gets
removed or replaced with something "better" means losing the old module
and its settings and having to configure its replacement. Only if I run
the full installer might it step on the existing configuration; however,
you should already know what if your current setup and use the custom
installation to select that same setup. Users applying a full installer
atop an existing installation should ALWAYS be selecting a custom
install option. Not allowing the clients to retain their existing
configuration when updating or reinstalling the program wouldn't just
**** off a lot of consumers but also a lot of corporate customers.