Avast blocks wikipedia, cdburnerxp, Invalid certificate bug

Hi

I’ve registered because of annoying Avast bug that SHOULD BE fixed in latest version: 10.4.2233, but it’s not.
Many other users have this bug so I’m not the only one.
https://forum.avast.com/index.php?topic=174202.30
https://forum.avast.com/index.php?topic=177221.0

Avast blocks wikipedia saying that certificate is invalid, but it’s up to date 2017-02-19 so it’s valid.
Everytime I want to go to wiki I must turn https scanning off.

  1. Turning off https scanning helps but I don’t want to surf unprotected.
  2. Adding wiki site to exclusion doesn’t fix it.

Second site is cdburnerxp site
https://cdburnerxp.se/
Avast blocks it too.

I’ve uninstalled Avast, run Avast cleaner in safe mode, installed Avast but it don’t help.

Please fix this bug.

Win XP SP3 32bit
Firefox 41.0.1
Avast 10.4.2233

That’s really strange because I have Avast Free 10.4 on Windows XP sp3 and I can go to the cdburner site. All my shields are on and I haven’t put in any exceptions.

I found out that if you disable the Mail Shield Wikipedia.org works again. So adding an exception for WIkipedia on the webshield won’t even work.

Ok I disabled the mail shield and was able to connect to Wikipedia.org. I went and turned mail shield back on and now I can go to wikipedia.org even with the mail shield on now.

The mail shield checks your email not your Web activity ???

I know. This Avast Free is full of weirdness. Frankly I spend more time dealing with false positives and troubleshooting Avast than it catches viruses.

Thanks for reply.

Disabling Mail Shield doesn’t help in my case and I’m not the only person who have “invalid” certificate bug.

Devs could you look how Avast treat certificates in https?

Anyone could help me please?

Hello,
Win XP sometimes cannot handle new certificates because they use new standards. We are working on our own authentication without using Windows API (maybe in v.2016 R2 or R3). If you don’t want to see this message disable https scanning in settings.

Milos

Thanks. It’s fixed now in 2016v