We should do better communication about SafeZone Browser launch.
Silent option will be default. If you decide to change it to manual, we gonna keep this change for future releases.
With the launch of Safezone browser, I came really close to removing Avast from every single PC, and Android Phones, but so far trying to stick it out a little longer, still have to finish removing SafeZone browser on Windows 10 Desktop, left over folders and such. Not sure if keeping it on any other of the machines that got it or not.
So will this silent updating be for only Definitions in the future or Program updates or both?
I’m a bit puzzled ??? Having just shot oneself in one foot, Will shooting yourself in the other foot make things better ???
This almost sounds like a how to book on committing ones self destruction. 
Well the limp won’t be so noticeable having shot the other foot.
@ hectic-mmv
In all seriousness though, as I asked earlier:
What is the urgency/reason/benefit to even contemplate silent program updates ?
For most people they won’t like that as we have seen in the past. But my major concern is these updates invariably occur shortly after boot (seen instup.exe in task manager lots and it is a bit of a hog) for those that shutdown systems at night. There really has to be a reasonable delay after boot to let the system settle down.
Also if these silent updates come in and as it is now program updates require a reboot, how will this requirement be handled or will there not be a reboot requirement ?
I’m staying with 2245 until all this nonsense shakes out, one way or another.
People with Windows XP, Vista or 7 can’t install it if the system doesn’t support the SSE2 instruction set.
This means millions of users can’t use the latest avast version. 
I am still happy with an automatic update every 240 minutes.
Besides the SafeZone browser surprise all is working correctly.
polonus
I do wonder if the DNS resolver issues and stuck application threads were fixed 
cause I’m totally not sure … so let’s see
Certificate problem with avast 11.2.2257 in windows 10 build 14279.
No problem with avast disabled.
In a past we used to release new version each 3-4 version per year. Newly, we would like to release new version every month. Its inconvenient to ask for reboot so often so thats why silent updates are introduced. This brings us to opportunity to react on issues in a shorter time.
About reboot. Good point, update should be planned not immediately after reboot. To apply all the changes update requires reboot and there will be reboot request after certaion amount of time without reboot which is remotely configurable.
@ hectic-mmv,
Update as often as you need too but, give me the right to decide when that update will happen.
Notify me of a needed update. Since this is my computer and I know my workflow,
I should be the one who decides when that update will happen.
From update v2254 avast firewall not started and I can’t start it manually too.
Repair Avast:
- Control Panel → Add/Remove programs → Avast
- Click on ‘Repair’.
- Follow instructions.
- Reboot.
This really is a bad idea:
First, as you should have seen from the troubles with Safezone, many, many people do not like silent updates. This is even more true for something central to the security of their computer than it was for that browser.
Secondly, come the day that there is a bug in the package that wasn’t found in testing YOU will get the blame for breaking the user’s computer. There is a world of difference between on the one hand me as a user deciding to try the new release, and it failing , and on the other me turning on my PC and finding that YOU put on software that doesn’t work.
Thirdly, are you really sure that silent updates are lawful in all jurisdictions in which Avast is used? To be clear, you cannot over-ride national law by writing something into the EULA. I think that it is the law in the user’s country that applies, not where you are based.
You may say that you do silent updates already with emergency updates. I think that the context is different. I see a significant difference between patching a system that has a fault and putting on a major update.
The one saving grace in your proposal is that there will be an opt-out - and I will opt-out if I continue to use Avast, which is not a given. If you insist on staying with the idea of silent updates then my advice is to make the process an opt-in and see what happens.
First, the updates are (almost) never like the install of a new component like it was with the SafeZone Browser.
They are more about improvements of detection/blocking malicious things as well as about fixing issues.
Kinda like the streaming updates and vps updates as they are now.
Secondly, 100% certainty that something will work on all systems doesn’t exist even though a lot of people are participating in the beta testing.
It simply is not possible to test with all hardware/software/settings options.
There are 100.000.000.000’s of different possibilities.
Thirdly, yes it is legal in all countries to my knowledge.
I never heard/read anything otherwise in the many years it exists.
I bet if it wasn’t it would have been all over in the news already.
Thanks, it is fixed.
You’re welcome.
I think “Silent update system” shall be renamed into “No need to Reboot update system”
that makes more sense and stop the conspiracy crowd from chanting stuff about breach of privacy …
Right now it is more like “on need to base” or “if we tell you, we have to kill you”.
I am happy that Avast! think about that (This brings us to opportunity to react on issues in a shorter time.)But users should know what he/she installed and avast! should ask for a permission to do so 