'Resolving Hosts' issue in Chrome and other browsers now occurs almost daily

I also want to chime in on this - I have 5 Windows computers/laptops at home, and this "Resolving Host" issue started happening to me ~2-3 weeks ago.  It may or may not happen to some browsers (i.e. Chrome, Edge, Firefox), and it would only happen to certain hosts also (i.e. it usually works fine with google.com but it would choke on bing.com).  When it happened, it would sit at "Resolving host" for a very very long time (talking about 30+ seconds or longer).  Sometimes the page would eventually load but other times it would not load at all.  Normally rebooting the problematic computer would fix it, but sometimes it would not.  Needless to say, this is a super annoying problem.  It only happened to some computers at my home that have Malwarebytes (MWB) installed

• but not all devices with MWB installed have this problem.

At first I thought it's a problem with a Disney Circle device that I installed last month.  I disconnected it altogether but then it didn't make any difference - the computers that have this issue were still experiencing the issue.  Then I thought it's a problem with my router - my router is configured with FamilyShield OpenDNS so I tried several other options (including using the Goggle public DNS or obtain DNS automatically through Verizon FIOS); rebooted the router and ONT, didn't make any difference - the problematic devices would still have issues from time to time.  I tried the ipconfig/netsh solutions posted on page 1 of the thread - it usually works but sometimes it would still fail after rebooting.  I would also point out that this behavior is also happening to a brand new laptop that I've just bought last week - with the latest BIOS, network drivers, Windows update and yes, MWB installed (and not much else installed other than Office and Chrome/Edge/Firefox).  At first I thought this is a problem with my new laptop but I did uninstall MWB after reading this thread just to try eliminating the problem, and indeed, I also have not experienced this issue anymore on my new laptop after uninstalling MWB.

I am a software engineer who is very familiar with computer networks and infrastructure (including how DNS works), but I still can't completely explain why this issue started happening to my other computers at home a few weeks ago.  But just with the timing of this issue starting to surface, and also happening with my new laptop with MWB installed, it suggests a possible conflict with one of the recent Windows Update having issues with MWB.  This is just my speculation and there's no proof of that, but it just happens that by eliminating MWB as one of the common factors of the computers that started having this issue, the problem hasn't come back yet.  I'll keep monitoring and hopefully it stays that way.

Hoping MS will make me happy but they will continue to disappoint me like they have going back to DOS days.

Their OS has got to be the worst out there. Clunky. Slow. Unreliable.

At least it doesn't crash as often as it used to.

You're determined to find a way to pin this on Microsoft, so make yourself happy.

I have 7 computers - 4 Chromebooks, 3 HP running Windows 10. All the W 10 computers (one desktop, two laptops) have current W 10 versions and Malwarebytes.

Don't have this issue on the Chromebooks.

Two of the W 10 computers (desktop and one of the laptops) don't have the "resolving host" problem.

Only one W 10 laptop is impacted.

MWB does not detect any problems on the affected laptop

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.