If you always use Google Chrome when browsing the internet, then you might have come across an error saying, “This webpage is not available, DNS PROBE FINISHED BAD CONFIG”. If you do, then this problem certainly has something to do with the DNS since any error code which has “DNS” in it points out a network issue in the computer.
Getting the DNS_PROBE_FINISHED_BAD_CONFIG error indicates that your computer is not able to connect the website because the Domain Name Server or DNS wasn’t able to resolve the website name into IP address or it is not available at all. So in this guide, we’ll help you sort out this issue in Chrome on your Windows 10 PC.
The most obvious thing you can do first is to try checking if the network cables connected to your computer or router are properly connected or not. If it turns out that some network cables are not connected properly, then it’s probably why you’re getting the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome.
And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.
Flushing the DNS and reset TCP/IP could also help in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. To do so, refer to these steps:
After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.
You can also try to remove the Proxy as it might also help you in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error. Here’s how you can do it:
Note: If you are using a third-party proxy service, you have to disable it.
Try to use the Google Public DNS
If the first option didn’t work, you can try to use the Public DNS by Google and see if it can help fix the DNS error. You have to modify the DNS settings in your system explicitly and use the DNS IP addresses.
If your browsing data in Chrome hasn’t been cleared for some time now then that might be the reason why you’re suddenly getting the DNS_PROBE_FINISHED_BAD_CONFIG error when you browse the web. To fix this error, you need to clear your web browsing data. Refer to the following steps to do so.
In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser.
Recently Logitech has released a new line of ergonomic mouse products on market, strangely shaped and lifted on a vertical axis Logitech claims that these devices will fix your issues and ease your hand pains for prolonged use of the computer.
The first time I saw this mouse I was not really impressed with its looks and somehow I thought it will not feel good. This all changed when I actually started using it, surprisingly altho strange in looks it does feel much more natural and much less stressful on hand. Also, it felt like I have used it before, personally, I did not need any adjustment period in order to use it fully.
All of that being said I will admit that using it for gaming is still not an option for me, someone might find it ok, especially if they play some games that do not need to be responsive like strategies or similar but for RTS and FPS I will still stick to the typically shaped mouse. This might be just a habit for me but somehow I feel more responsive with the typical mouse, but for anything else, this is the mouse that will keep your hands stress-free.
Now in order to get the mouse to be really recommended it needs to have some good technical specifications as well, looks are not all. The less important detail is that the mouse comes in 3 different colors: Black, white and pink, and its technical specifications are:
Height: 71 mmWidth: 70 mmDepth: 108 mmWeight: 125 g
Personally, I would recommend this mouse for anyone who does work in front of the computer during the whole workday since it really does loosen grip and strain on hands.
Error Causes
Valve has officially announced that Steam Deck will be compatible with Windows 11 despite TPM 2.0 Microsoft requirements.
From the beginning, Deck was announced like a mini handheld PC device. Powered with new Steam OS 3.0 based on Linux. However, besides out-of-the-box OS it was also stated that Deck will be a personal device meaning that other PC-based operating systems could be installed on it and even run your typical applications in it.
Since Microsoft announced Windows 11 hardware requirements, specifically the TPM 2.0 requirement many users voiced concern that Steam Deck will not be able to connect to Windows 11
TPM 2.0 is something that Microsoft requires for every internal and hardware component that is to connect on a Windows 11 device. This is to ensure that only trusted devices would be included in the array of a PC setup and avoid any problems like malicious hardware injecting software into a system.
This would also minimize the compromise Windows would have, as unverified or untrusted devices connect to a Windows PC.
However, Valve and AMD are ensuring us that Deck will not have any issue connecting to a PC running Windows 11 or even if you wish to transform Deck itself into a Device running Windows 11. 
In the menu choose device manager and click on it.
When the device manager opens, expand the Imaging devices or Cameras section.
Right-click Integrated Camera or the primary webcam, and click Properties.
Go to the Details tab.
Under the Property section, click to select Matching device ID from the drop-down.
Right-click the value and select Copy
The next step is to download and install Windows Driver Kit (WDK)
$id = (Get-CimInstance Win32_PnPEntity |
where caption -match '<PRIMARY CAMERA>').pnpDeviceID
$ppid = "{0}{1}" -f '@',$id
Set-Location c:\<FOLDER>
Devcon status $ppid
Devcon disable $ppid
Devcon status $ppid
To enable the camera device, run the command below in PowerShell:
devcon enable $ppid
