fwiw, I've learned this is not the only optional tool that they silently installed.
Passwords has been silently installed on some systems.
Having a new program version introduce new features is to me a lot more acceptable than what happened in the SafeZone Browser case. There, the Avast program version before and after were (are) the same. I had automatic program updates turned off. In fact, while I have notification enabled, I only use it to find out the program has a new update available. I then come to the forum here to grab the offline installer and use that. I always do a custom install, and it has become necessary to be hyper-alert for pre-checked side installs because I've been bitten by having past faith in Avast in that area. Pretty much I want to control when program updates happen and have the prior version handy to go back to. This is safer, but is not free; most people are happy to not have the bother and let Avast take care of keeping itself current.
Partly because of this approach, I knew when Passwords was added and could decide if I wanted to let it be enabled. The Safezone Browser, simply appeared out of the blue (in a very visible way) despite all that.
-Dave
Hate to burst your bubble but Avast will do a program update and ignore the "manual" setting. This has happened many times in past.
Granted, this is exception not the rule but they have done this.......and it is not just the emergency update but their desire to move customer base from one revision to next.
So, to keep beating this now 18 page dead horse........Avast can market and bundle all they want.......go for it.
However, forcing an update that either does it's own PC reboot or a reboot required SHOULD NOT HAVE ANY NEW options/feature/packages force/auto opt-in/silent installed.
Go ahead and add the option/feature/package in the installer but allow the user AFTER the successful reboot to go into MODIFY and select the new "item" to install.
Avast can market/announce these item via pop-up/forum/blog/etc.....and I'm sure a lot of takers.
This is a VERY simple thing for Avast to do and it protects their user base as well as achieves their goal to push new offering.
However, I don't believe Avast will implement this policy because this has come up over and over with program updates, GrimeFighter, NG and now SafeZone.
Bottom line, Avast has shown and continues to show if you install their A/V they will do what they feel they want to your PC without consideration of impact.
There are some questions I saw from Avast saying effectively "we don't understand what we did wrong guys"........really, come on.......Avast is not stupid and this thread alone if one of many....and now 18 pages. Avast knows exactly what they are doing and the game is simple #s.....their EULA voids any liability to the impact of their software on your PC and they are betting they can make more money off the folks that try-then-buy from their "push-ware" than the loss of folks they tick off.
Perhaps, though I find it a little hard to believe I wouldn't have noticed anything fishy in the past, especially considering any spontaneous reboot or reboot request would be very odd the way I set things up. And I haven't previously to this.
In this case, the update neither did its own reboot nor required one that I observed.
I've always observed when going through the custom installs, everything is checked, I have to remember which ones I don't want, and sometimes there are new ones.
-Dave
It happens.......glad you were not bit by it.
Avast does fine with customers doing clean install and going to CUSTOM (I advise take a picture and save because it changes) and opt-in/out of wanted components.
For me in example, I only want the shields.....nothing else....no matter what is offered.
Avast has a great A/V......I just personally don't want/need the other utils.
The "issue" is when Avast does a "update" (not VBS database) for the program or if they push an update for new "features/packages".
The installer just installs and whatever they have as default installs without a user choice.
Regardless if a reboot happens by Avast's execution, asks you for a reboot, or no reboot......the next time the PC reboots that unknown and possibly unwanted software has been installed.
So, is the crime that you may not want it ? ......no, not really. In theory you should be able to go into MODIFY and uncheck the new "module" and it will be uninstalled.
The issue that everyone is having, and I think a HUGE threat to customers PCs, it that Avast installs software without the user's ability to backup and/or manage that install.
Avast is making assumption that the install will have no ill affect to the PC....and there are many cases where user's PC have become un-bootable.
Is this Avast's fault ? ........a point you can argue both sides to death. The point is Avast cannot test all the possible conflicts to their "assumption" all is OK on a silent install is absolutely on Avast's part an act that borders on Malware practices. Couple that with Avast is a "security" company makes this way past the line of acceptable.
I don't know how long you've been around but AVG did this years ago going from one version to another and an overnight PUSH bricked ten of thousands of PCs.
It is a very real issue and sadly one Avast could easily mitigate by a simple policy of all new software modules being by default opt-out in the installer and marketing notices to customers to go into MODIFY to install. The fact they don't "understand" this means either they are the dumbest group of people on this earth (which they are not) or they frankly do not care.
