This error doesn’t mean you won’t be able to access other web pages. Still, it also doesn’t guarantee this, so it depends on a lot on users system configuration as to why the error ‘DNS Probe Finished Bad Config’ is occurring on their system. Anyway, without wasting any time, let’s see how to fix this error with the below-listed troubleshooting steps.

dns_probe_finished_bad_config error [SOLVED]

Make sure to create a restore point just in case something goes wrong.

dns_probe_finished_bad_config error [SOLVED] Method 1: Restart your Router Method 2: Flush DNS and Reset TCP/IP Method 3: Change DNS Settings Method 4: Disabling Firewall and Antivirus Method 5: Clear Browser’s Cache Method 6: Use Chome Cleanup Tool

Method 1: Restart your Router

Sometimes this error can be resolved by restarting your Wifi modem or router and again trying to visit the page earlier showing the error ‘DNS Probe Finished Bad Config’ and if you’re able to access the website than your error is resolved but if not then continue.

Method 2: Flush DNS and Reset TCP/IP

  1. Right-click on Windows Button and select “Command Prompt(Admin).”

  2. Now type the following command and press Enter after each one: ipconfig /release ipconfig /flushdns ipconfig /renew

  3. Again, open Admin Command Prompt and type the following and hit enter after each one:

  4. Reboot to apply changes. Flushing DNS seems to Fix dns_probe_finished_bad_config error.

Method 3: Change DNS Settings

The point here is, you need to set the DNS to automatically detect IP address or set a custom address given by your ISP. Fix dns_probe_finished_bad_config error arises when neither of the settings has been set. In this method, you need to set your computer’s DNS address to the Google DNS server. Follow the given steps to do so:

  1. Right-click the Network icon available on the right side of your taskbar panel. Now click on the Open Network & Sharing Center option.

  2. When the Network and Sharing Center window opens, click on the currently connected network here.

  3. When you click on the connected network, the WiFi status window will pop up. Click on the Properties button.

  4. When the property window pops up, search for Internet Protocol Version 4 (TCP/IPv4) in the Networking section. Double click on it.

  5. Now the new window will show if your DNS is set to automatic or manual input. Here you have to click on the Use the following DNS server addresses option. And fill the given DNS address on the input section:

  6. Check the Validate settings upon exit box and click OK. Now close all windows and launch Chrome to check if you’re able to Fix dns_probe_finished_bad_config error.

Method 4: Disabling Firewall and Antivirus

Sometimes the Antivirus program can cause dns_probe_finished_bad_config error, and to verify this is not the case here. You need to disable your antivirus for a limited time so that you can check if the error still appears when the antivirus is off.

  1. Right-click on the Antivirus Program icon from the system tray and select Disable.

2.  Next, select the time frame for which the Antivirus will remain disabled.

Note: Choose the smallest amount of time possible, for example, 15 minutes or 30 minutes. 3. Once done, again try to connect to open Google Chrome and check if the error resolves or not. 4. Search for the control panel from the Start Menu search bar and click on it to open the Control Panel.

  1. Next, click on System and Security then click on Windows Firewall.

  2. Now from the left window pane click on Turn Windows Firewall on or off.

  3. Select Turn off Windows Firewall and restart your PC.

Again try to open Google Chrome and visit the web page, which was earlier showing the Aw Snap error. If the above method doesn’t work, please follow the same steps to turn on your Firewall again.

Method 5: Clear Browser’s Cache

  1. First, click on the three dots on the top right corner of the browser window and select Settings. You can also type chrome://settings in the URL bar.

  2. When the Settings tab opens, scroll to the bottom and expand the Advanced Settings section.

  3. Under the Advanced section, find the Clear browsing data option under Privacy and security section.

  4. Click on the Clear browsing data option and select “All time” in the Time range dropdown. Check all the boxes and click on Clear Data button.

When the browsing data is cleared, close, and relaunch the Chrome browser and see if the error is gone.

Method 6: Use Chome Cleanup Tool

The official Google Chrome Cleanup Tool helps in scanning and removing software’s that may cause the problem with chrome such as crashes, unusual startup pages or toolbars, unexpected ads you can’t get rid of, or otherwise changing your browsing experience.

Recommended:

Fix Error Code 0x8007000D when trying to activate Windows How to Fix Application Error 523 How to fix 502 Bad Gateway Error Fix The application failed to initialize properly

That’s it you have successfully Fix dns_probe_finished_bad_config error, but if you still have any queries regarding this guide, then please feel free to ask them in the comment’s section.

dns probe finished bad config error  SOLVED  - 43dns probe finished bad config error  SOLVED  - 68dns probe finished bad config error  SOLVED  - 53dns probe finished bad config error  SOLVED  - 67dns probe finished bad config error  SOLVED  - 2dns probe finished bad config error  SOLVED  - 37dns probe finished bad config error  SOLVED  - 55dns probe finished bad config error  SOLVED  - 45dns probe finished bad config error  SOLVED  - 81dns probe finished bad config error  SOLVED  - 49dns probe finished bad config error  SOLVED  - 82dns probe finished bad config error  SOLVED  - 77dns probe finished bad config error  SOLVED  - 55dns probe finished bad config error  SOLVED  - 4dns probe finished bad config error  SOLVED  - 97dns probe finished bad config error  SOLVED  - 96dns probe finished bad config error  SOLVED  - 75dns probe finished bad config error  SOLVED  - 64dns probe finished bad config error  SOLVED  - 27dns probe finished bad config error  SOLVED  - 76dns probe finished bad config error  SOLVED  - 76