Sorry, no - the topic is not yet closed - I fear I have to restart it with the explanation of that what happened ... see post #12 - that's the main subject of the thread:
Can you please explain how this can happen:
1st thing:
Date: 22.04.2011 - Time 21:45
- CURRENT STATUS: NOT YET REGISTERED
- this product must be registered within 0 days.
- Registration information:
Current registration will expire on: 20.05.2011 12:00:03
Date of Registration: 20.04.2011 12:00:03
2nd thing:
0) preferences is set to "manual updates" with announcement as soon as new virusdatabase is ready ("mid-position" in prefs); tray-icon has exclamation-mark ... this is an accepted setting that AVAST allows!
1) click on tray-icon (that has exclamation mark) - the avast-window opens and there is a problem reported: ATTENTION - your system is not fully protected; please use "fix now" button to start fully protection of system.
- there is an exclamation-mark at "auto-updates" reporting that auto-updates are turned off (not respecting that settings are "ask when an update is available").
2) then click on "fix now"-button - it is to assume that this should turn on auto-update of virus-database (as this is reported to be the reason why the system is not fully protected)
3) after that click on "fix now", all the shields are turned OFF (!!!) and you are told that protection is disabled and trial period is over (but you can read that it still lasts nearly a whole month) ... you cannot turn protection shields on again before registering
4) and: online-registering does not work (or is disabled) at that moment ...
and this happens after two days of use
Can you please explain why that behaviour occurs? (in short words: clicking on "fix now" turns AVAST-shields totally off) ...
Is that behaviour (telling you to activate full protection - and the result is total lack of protection) corresponding with your philosophy of security? I just cannot believe that!!! If AVAST wants to be a "serious software" (in the domain of security) and not only just a piece of crap, I assume you consider that behaviour at least as problematic, if not worse.
As explained: there was an inconsistency with time/clock with a dual boot so that the computer-clock was set 2hrs in advance by the other operating system and set back by that windows where AVAST is installed. This might just be an explanation of what the trigger of that strange behaviour could have been - not more and not less.