Share this article

Improve this guide

FIX: DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10/11

4 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

DNS_PROBE_FINISHED_BAD_CONFIGerroris not that uncommon, and it can be seen on all versions of Windows, so it’s no wonder to see thiserroronWindows 10as well.

Fortunately for you, thiserroris quite easy to fix and today we’ll show you how to do it.

DNS_PROBE_FINISHED_BAD_CONFIGerrorappears in Google Chrome browser when yourinternet connectionis giving you problems and there are few simple ways how to fix it.

Table of contents:

How can I fix DNS_PROBE_FINISHED_BAD_CONFIG error?

Solution 1 – Restart your router

This is quite straightforward, just press the power button on your router, wait for a minute and turn your router back again. This should reset yourIP addressand fix the problem.

Solution 2 – Renew the IP address

But if simple restarting didn’t solve the problem with DNS_PROBE_FINISHED_BAD_CONFIG error, you can try with renewing yourIP address.

And if you’re not sure how to do that, just follow these instructions:

Solution 3 – Flush the DNS cache

The next thing we’re going to try is flushing the DNS cache. To do so, follow these instructions:

Solution 4 – Reset IP catalog

Solution 5 – Change the DNS servers

And if nothing from above helped, you can try to change the DNS servers, and see if theerroris solved. To change the DNS servers, do the following:

Solution 6 – Disable your antivirus

If nothing worked, try disabling your antivirus. If you’re using Windows Defender, here are the steps to follow to turn it off:

Once you have disabled your antivirus, do the same with yourfirewall.

Once you’ve disabled both your antivirus and firewall, check if the error persists. Don’t forget to enable both security solutions after you finished the test.

Solution 7 – Install the latest network drivers

If your network drivers are outdated or corrupted, this may explain why you’re getting the DNS_PROBE_FINISHED_BAD_CONFIG error.

Go to Device Manager, and update your network drivers and check if this solution worked for you.

Solution 8 – Disable website blocking software

If you’re usingwebsite blockers, temporarily disable these tools to see if this solution fixes the problem.

Some users confirmed that theerrordisappeared after they turned off their website blockers. Do test this solution to see if it works for you as well.

Solution 9 –  Check your browser and delete temp files, cache, and cookies

And finally, the last solution on our list: make sure that your browser is not actually the one causing theerror. Delete cookies, temporary files, and cache and check if this helps.

For more information on the steps to follow, go to your browser’s official support page.

That’s about it, I hope at least one of these five solutions helped you to solve the problem with DNS_PROBE_FINISHED_BAD_CONFIG error inWindows 10.

If you have any comments or questions, just reach for the comments section below.

More about the topics:internet connection errors,System Errors

Ivan Jenic

Windows Hardware Expert

Passionate about all elements related to Windows and combined with his innate curiosity, Ivan has delved deep into understanding this operating system, with a specialization in drivers and driver troubleshooting.

When he’s not tackling diverse driver-related problems, Ivan enjoys watching good movies and spending time hiking with his family and friends.

User forum

3 messages

Sort by:LatestOldestMost Votes

Comment*

Name*

Email*

Commenting as.Not you?

Save information for future comments

Comment

Δ

Ivan Jenic

Windows Hardware Expert

Ivan has delved deep into understanding the Windows OS, with a specialization in drivers and driver troubleshooting.