Hi
I am having the same certificate verification problem with AVAST HTTPS scanning module and the Skype website… As I can See it, Avast is using a SHA1 coding for it’s certificate and Chrome is rightly flagging this as a security risk on Secure sites. (When a site works correctly, the coding is the newer SHA256 - Why are Avast still using SHA1 on some sites???)

SHA1 is a universally recognised WEAK(COMPROMISED?) coding platform that is being phased out of existence. It surprises me that a SECURITY COMPANY would choose to use this certificate format for one of it’s most critical modules.

I am a relative newbie here on the forums, but consider myself above average on PC matters and fairly clued in on aspects of security etc.