I am having the same issue with every website I try to open. I have identified the VPN I purchased and installed last night. When the VPN is one, it takes like 15 seconds to load any page, and the same amount of time to change pages or follow links. With the VPN off, all is good again.
I am requesting a refund for the VPN. I cannot figure it out, and no one else seem to know anything. It’s doing it on mine and my wifes phones as well.
I have same problem on Chrome and Microsoft edge. I bought anti virus last wednesday and soin after i started having problems. When i disable the shield everything works fine. I am reallu upset. I cannot find where i contact avast
Nearly every website loads (or begins to load) then freezes/sputters within 2 seconds. After about 5 seconds the site seems usable in terms of images, links, etc.
I began experiencing issues with Google Chrome after the December update. For about a month I assumed it was something on Chrome’s end, but the next Chrome update didn’t help the freezing/lagging issues. I checked the forums and found this thread. I disabled QUIC/HTTP3 scanning, which improved performance but it’s still not at “normal” speed.
Recently it’s seemed to creep into Firefox as well. I don’t want to disable anymore features, and I don’t want to switch AV as I’ve been using Avast for well over a decade.
I don’t understand. We got an update on the program today, yet Webshield making browsers hang (both Edge and Chrome in my case) is still not fixed. After three months?
I’ve been having the same issue for a few weeks on several computers at home (different make and models, all W10 20H2).
This applies to all Chromium based browsers (Chrome, Opera, Edge, … updated to the latest version) who freeze when Avast is active.
In addition, when I close the frozen browser, a unkillable process remains in Task Manger.
Disabling Web Shield fixes the issue and terminates the leftover process.
Disabling QUIC/HTTP3 Scanning with Web Shield on also fixes the issue.
If it helps, I submitted a support file (ID: AJ7EX) with Avast Debug Logging enabled.
There is no permanent fix yet.
The temporary solution is disabling HTTP3/QUIC scanning in Web Shield settings.
Could you also double-check if the provided support file id is correct, please?
I have this same problem on Firefox, Win 7 64 bit, Avast Premium Security. Both applications up to date.
The behaviour is the same: it hangs for 5-20 seconds and then starts loading again. It can happen on any URL. If HTTPS or QUIC/HTTP3 scan is disabled, everything works fine again.
It’s been going on for about a month now and it’s quite frustrating.
Chrome is working fine, apparently. Could you people who had this issue be so kind to give me some feedback on Google Chrome? Is it working now? (because, after reading this thread, I’m wondering if the problem has been fixed only on Chrome, and not on Firefox).
I hope to hear from you soon.
Thanks a lot for any kind help you can provide
I’m having this issue as well with Firefox. I see it was asked, but didn’t see an answer, what protection is being lost by disabling quic/http3 scanning?
Thanks for the suggestion; I will do a research on how to do it on Firefox.
However, it does not really solve the problem, because I shouldn’t have to disable anything to make things work as before. And, more important, I’d really rather not do it, as I don’t know what security features I may disable by turning off QUIC protocol.
Maybe the issue got a little better in the last days (it seemes that the hangs are occurring a little less often than before, but they’re still present). I’ll keep doing tests whenever I can.
Please let us know about any updates with this issue. Meanwhile, thanks very much for your work and for any help you can provide.
QUIC or HTTP/3 is still in development. If deactivated the browser will switch back to the widely used HTTP/2.
Disabling it as a temporary solution while keep Avast security components enabled.
In Firefox you can find it in the advanced settings.
Since your post, I have checked all ''NEW Avast Version 21. ( 2021)" posts from July through December 2021, but none of them mention this problem/bug.
This problem already exists since at least the beginning of this year and it is not feasible to install and test each and every update to check whether or not this problem has been solved.