Fix: ”0x86000c09 err_quic_protocol_error” in Google Chrome
It’s hard to be at the top for so many years, especially if you’re referred to as ”resource-hogging monster” or ”private data collector for Google”. But Chrome still is the most used web browser on multiple platforms. It would be even better if there are fewer errors that occasionally plague users, like the ”0x86000c09 err_quic_protocol_error” error we’re addressing today.
If you have had a hard time with repetitive slowdowns in loading followed by the error prompt, look no further. The solution for your problem is below.
How to address the ”0x86000c09 err_quic_protocol_error” in Google Chrome
Solution 1 – Clear Browsing history
The first step you should take concerns the stored browsing data. Especially, the cache that can pile up quickly and cause performance drops and similar issues. Chrome is already acknowledged as one of the most resource-hogging browsers, and the abundance of cache is making things even worse. It can, like in this scenario, cause an error or two, as well.
Follow the instructions below to clear the Chrome browsing data:
- Open Google Chrome.
- Press Ctrl + Shift + Delete to summon the Browsing data dialog box.
- Check the ”Cached images and files”, ”Cookies”, and ”Download” history boxes.
- Under the ”Clear the following items from” drop-down box, select the ”the beginning of time”.
- Finally, click on the ”Clear browsing data” button.
Solution 2 – Disable VPN or proxy and check the connection
Connection issues are commonly related to a large variety of Chrome errors, including the one we’re referring to today. In order for everything to work in a seamless manner, you’ll need to ensure that your connection is stable. In addition, it’s strongly advised to temporary disable VPN or Proxy and look for changes. Occasionally, they can cause the stall within Chrome, or even invoke crashes and errors.
The best way to confirm that everything is working fine is by using the alternative browser. If the alternative browser works without issues and you’re still stuck with the Chrome error, make sure to check the remaining step.
Solution 3 – Disable QUIC protocol
The innovation-wise, Chrome is right at the top, with an abundance of experimental features tested on a daily basis. However, some of those can occasionally cause issues with the browser itself. That just may be the case with the QUIC (Quick UDP Internet Connections) protocol. Even though the initial thought behind this protocol is to speed up the internet browsing, it can be quite unstable at times. That can, consequently, lead to slower loading times or even the ”0x86000c09 err_quic_protocol_error” error.
For that purpose, we advise you to disable it, and you can do so by following the instructions below:
- Open Chrome.
- Copy-paste chrome://flags/ in the address bar.
- Press Ctrl + F to open the search bar.
- In the Search bar, paste Experimental QUIC protocol and press Enter.
- Now, once we successfully located the QUIC protocol, click on the contextual box below the protocol and choose Disable instead of Default.
- Relaunch browser and you should be good to go.
That should do it. In case you have any additional issues or a suggestion on how to address this Chrome error, make sure to tell us in the comments below.
RELATED STORIES YOU NEED TO CHECK OUT:
- Google Chrome, Mozilla Firefox market share declines, while Edge’s increases
- Downloading proxy script on Google Chrome
- ‘Class not registered’ Chrome error on Windows 10, 8, 7
- Fix: Google Chrome could not move extension directory into profile
- Chrome slow? 9 great tips to help you speed up Google’s browser
“A picture is worth a thousand words” is a popular English idiom and the quote perfectly describes digital marketing or marketing strategies in general that […]
While the winter arrives with the joy of Christmas, it also brings the freezing weather along. Of course, there’s the fireplace to warm you up, […]
Recent comments on Reddit would suggest that Microsoft is still not playing the game when it comes to collecting data on its users. This is […]