Warn when self-protection disabled?

[MikeBCda]

Twice a month or so, I like to trim down the setup logs so they don't get unreasonably big.  I always used to have to stop resident protection first, and found (which makes sense) that in 4.8 I also have to temporarily disable self-protection to get permission to save the edited log.

Could you add some kind of indicator that this protection isn't active, maybe similar to the red bar across the tooltray icon when resident protection is stopped?  Or even an addition to the mouse-over info?

Unless I'm missing something, right now the only way I can tell whether or not self-protection is active is to go into Troubleshooting and see if it's ticked there.  Obviously if I forget to turn it back on, that's potentially risky and there should be a warning of some kind.

[Lisandro]

Twice a month or so, I like to trim down the setup logs so they don't get unreasonably big.  I always used to have to stop resident protection first, and found (which makes sense) that in 4.8 I also have to temporarily disable self-protection to get permission to save the edited log.

You can open avast Log Viewer and clean all logs from there... just click the "X"...

Could you add some kind of indicator that this protection isn't active, maybe similar to the red bar across the tooltray icon when resident protection is stopped?  Or even an addition to the mouse-over info?

Mike... the self-defense module is bringing some (many) troubles... an indicator could mess the situation, imho.
Let it on and disable only if needed.

[alanrf]

I like to trim down the setup logs so they don't get unreasonably big

That means editing - not deleting.**

There really is no strong reason for the logs folder to be protected at all that I can see.

Logs should not, these days, be in the Program Files at all - that is what Application Data was created for and, lest we forget, avast is just an application - albeit a very valuable one.


If some of these issues can be overcome then I agree with Tech - it would be better for users not to have to think about whether the self defense (why did they choose a word spelled differently in US English and everybody else's English) is on.

** As tech reminded me in an earlier thread avast does give a log limit size in the log viewer to ensure that logs do not become too large.  But it is a one size fits all and is not ideal for those of us who do testing and sometimes need to create large email logs, debug level logs etc. 

[Vladimyr]

(why did they choose a word spelled differently in US English and everybody else's English)

That goes for you too Mr Gates! Minimise / Maximize 

[Lisandro]

That means editing - not deleting.**

Ok, you win

There really is no strong reason for the logs folder to be protected at all that I can see.

It would be good if they're on Application Data folder.