Does disabling QUIC have any other negative effects, though?
I donāt think so, I guess the browser will use other (default?) protocol, but updating avast solved the problem for me (25.4.10068a (build 25.4.10068.933).
Ok, because some people are still experiencing an issue even after updating.
Iāll re-run that update, because I was blaming other things, but figured about an hour ago that since updating Avast to that version the other day, Iāve had all of these issues.
And for me, it is the Google sites, but itās also that itās causing CloudFlare and human verification to fail. I donāt think those are Google sites, but something about them in Chrome is problematic with this Avast glitch. I tried to see if I switch to Firefox itās better and Iām passing the human verifications there with no issue.
Hopefully re-doing the recent update fixes it for me, but if not, your fix has worked for me. Thanks so much for posting it. Hadnāt even realized how many sites make use of the human verification check until I was failing it because it wouldnāt load properly.
Okay, update to my previous post. Updated Avast again and it did not fix the problem for me. So your disabling QUIC protocol is my solution until further notice. Glad the update fixed it for some, but Dinobot is correct, didnāt fix it for everyone.