Lately, nearly every Avast user I know - including me - has had issues with or after updating Avast versions within the GUI. Now I’m just not routinely updating Avast on machines I depend on, which in theory is potentially counter-productive but in practice, every time I update I waste heaps of time going back.
I did an update from the UI of and I didn’t get Skype and would have been well pi**ed if I did. If I ever wanted Skype then it would already have been installed.
I did get the usual Screen with the Google Chrome cr4p after install and restart, which I again declined.
When are avast going to honour the fact that I have declined Chrome on every install since the ark and continue to pre-check it on program updates, when it wasn’t on the previous program updates.
If you are going to offer Skype here would be a place to confirm, so you get the chance to opt-out if you have done a program update an not a custom install.
Red and Vladimyr,
You are both correct.
Since I didn’t get a chance to choose or reject this option using a simple custom install over the existing version,
I decided to do a clean install to find out where this added install was hiding.
For the past few years people have been writing on this forum that Chrome was being installed without giving them a chance to opt out, but other people just commented that this was not the case and the opt out option was missed on another screen that the user missed.
Now the same problem is being found with Skype.
Maybe the original complaints about Chrome were valid and should have been taken seriously as a bug or something with the install process?
Of course it is possible. The very post in front of yours shows how, the very first screen of a clean install has the option. Uncheck the Skype box and also click the Custom Installation button - not the big Blue one, but the small insignificant Grey one.
This gives the opportunity to uncheck many options and tools if you don’t require them.
Another point, if you that concerned/frightened about this, then running a beta version of avast may not be a good idea. Whilst the greatest majority beta testing in avast hasn’t had any major issues for me, you have to be aware of the risk in any beta testing on a live system, not a test system.
I used to have BETAs, but probably the fact that I did I clean installation when the .2214 came out (cleaning the registries/left overs with Revo Uninstaller) cancelled the “BETA settings” … I will wait still for tomorrow, then I’ll do it manually as you suggested if nothing shows up! 8)
You will only see it if you have previously taken part in beta testing, e.g. installed a beta build before (and not done a clean install at any point since then).