After temporary disabling https scanning, enabling doesn’t seem to get it working anymore, i see now the original certificates instead of the Avast ones. Restarting browsers or the PC doesn’t help. Using Windows 8.1, Avast Pro, MBAM, MBAE, ZoneAlarm Free, Antilogger Free.
- Remove ZoneAlarm completely.
- Reboot
- Enable https scanning
If that doesn’t solve it, perform a repair of avast and try again.
Thank you for your reply! Repairing Avast seems to do the trick, but after rebooting the PC it wasn’t OK immediately, first the original certificates were used again, but after restarting Firefox (again), the avast certificates are being used now I didn’t remove ZoneAlarm, I’ve used it with Avast for years without problems and it wasn’t updated recently.
Keep an eye on it.
ZoneAlarm isn’t only a firewall anymore and can conflict with avast.
After another restart of the PC, the issue returned >:( Maybe I will try removing ZoneAlarm, but I am only using the firewall part, why would this cause problems with Avast?
As I said, ZoneAlarm is not just a firewall anymore.
Components of the av are installed although you only select to use the firewall.
http://blog.kaspersky.com/multiple-antivirus-programs-bad-idea/
The antivirus part is not installed, see picture.
See reply #5
note the components part
Thanks, I didn’t read properly… Deinstalled ZoneAlarm, but it makes no difference. Https scanning seems to be enabled/disabled at random. Using Firefox or Chrome makes no difference.
Also de-installing Zemana Antilogger Free and disabling MBAM and MBAE didn’t work. But the https scanning setting does work perfectly for Internet Explorer! So I also tried a clean profile for Firefox and Seamonkey, but that had no effect. Guess I will not be able to use https scanning if I use Firefox or Chrome, which makes my computer less secure, unless I replace Avast for another AV.
What do you mean by enabled/disabled at random ???
When the setting for https scanning is on/enabled, it sometimes works (avast certificate is used) but on other (most) times it doesn’t work (original certificate is used). No problems in Internet Explorer, only in Chrome, Firefox and Seamonkey.