All problems with the "Resolving Hosts" issue have been remedied for all of my browsers! Update your Malwarebytes. I am using
Malwarebytes version 4.1.2.73; Update package version: 1.0.27793; Component package version 1.0.990
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
About 3 weeks ago I first saw 'resolving hosts' in Chrome when pages weren't loading, or were taking several minutes to load. The same thing was happening in Firefox and Edge at the same time. At that time a reboot seemed to fix it.
Since then it's happened frequently, every few days. I tried a number of things and at first these sometimes seemed to be working, sometimes with a reboot:
Now I'm encountering 'resolving hosts' almost every single day. Sometimes it happens when I first turn on the PC in the morning. Sometimes in the middle of the day when I'm working, it will suddenly start.
The only thing that now works reliably is typing this in a command window and rebooting:
netsh int ip reset
Can someone please help me get to the root of this problem? I'd never seen it before about 3-3.5 weeks ago.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
All problems with the "Resolving Hosts" issue have been remedied for all of my browsers! Update your Malwarebytes. I am using
Malwarebytes version 4.1.2.73; Update package version: 1.0.27793; Component package version 1.0.990
As of this afternoon, July 6th, the Malwarebytes support site states, “There is no fix at this time.”
I am proceeding cautiously with this issue, as there seems to be conflicting information floating around:
a) MWB has acknowledged that their Premium Home product causes a major system dysfunction on PCs updated to v.2004 Windows 10; and
b) there is no recommended solution at hand (for non-Techs).
Given that the Windows upgrade occurred a while ago, when the problem was first identified by users, it begs the question about quality control and what stress testing of preliminary beta versions, if any, was conducted. The seriousness of random system crashes would seem to be a major reputational crisis for any software company.
My subscription to MWB Premium stays in the recycle bin, quarantined, until it’s safe to come out. Seems appropriate to our new world, no?
The Domain Name Server’s IP address is stored as data. If it becomes corrupted Edge Chrome (or any other application attempting to access a website by its URL) will still send a request to the IP address on hand for the domain name server. It being an invalid address, no reply is given. I believe alternate Domain Name Servers are also listed then tried. Netsh is capable of clearing the DNS Server Table and repopulating it with valid IP Addresses for the Domain Name Server(s). Somehow this data gets corrupted.
After this issue occurs simply rebooting without executing the netsh command does not solve the problem. You must execute the netsh command and then reboot the PC. Then the problem is resolved.
Something overwrites the DNS Server data. This can happen with only Edge Chromium running. I believe Edge Cromium is a Microsoft product. I also believe DNS Server data should not be so easily overwritten or corrupted.
Regardless, it is in Microsoft’s best interest to resolve this problem.
A "host" in this situation is the web server that your browser is trying to reach; it is 'hosting' the web page you want to see.
"Resolving" means obtaining a numerical IP address from your ISP's DNS server.
If your web browser is having trouble resolving hosts, that means it's not getting a numerical IP address from your ISP's DNS server for the websites you want to visit
None of which has anything to do with Windows or Microsoft.
It is when the data is initially stored correctly then damaged while in the OS’s care.
Done - I will report back here if it happens again. Thanks!