I have been using Avast Free for months without issues.
The problems started a week or so ago (not sure why) with WebShield blocking all internet traffic. (Chrome/Edge/IE11)
I can’t even browse to the Avast website without disabling WebShield.
I am using Win10 20H2 64Bit with latest updates.
I tried repair/uninstall with no luck.
Today I used the Avast uninstall tool and re-installed Avast …same problem.
Turning off WebShield defeats a large benefit of having this software installed.
Any idea how I can fix this?
I think your problem may be related to the use of 21H2 which is in essence beta software. (Insider preview build)
Current latest final release is 21H1.
If I have Web Shield = ON and I untick the “Scan HTTPS” and then restart the browser, then it seems to work properly.
If I don’t restart the browser, the browser doesn’t seem to always notice I changed the Avast setting.
While this is a BIG improvement to not having any WebShield on, this would mean many sites would not be scanned as more and more sites are migrating to HTTPS.
Does this help narrow down the root cause since I am assuming that if there is such a function to “Scan HTTPS” there should be a way to have it enabled and work without blocking many sites(including the Avast main site) ?
There must be a difference in the code between Omni and the Free version.
I tried a full reboot just to be sure everything is cleared from mem and I can’t even get to Avast.com if I have HTTPS scanning enabled.
I keep my system pretty “vanilla” so I don’t think there is something else conflicting.
Maybe there is a bug in the Free version that doesn’t show up in Omni.
I am also using Win10 64Bit regularly updated. Since yesterday I have been blocked from logging into the comments section of a British broadsheet newspaper “The Daily Express” by an Avast alert to the effect of “Avast has blocked an URL Phishing attempt”, claiming that the Cpmment platform was infected. Other posters have no problem logging in. Nor am I prohibited from commenting. The error # on Firefox was 1ecta7416535 , on Chrome it was Error 04bc52c48db0 …