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

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

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.

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.

Has MS blocked this thread or just certain parties who have different opinions about MSN's inability or unwillingness to address and fix the problem?

Received notification of a response by yanjian that does not appear in this thread. Has yanjian been censored?

Yanjian occupation is listed as a software engineer.

I am also running MWB Premium. Removing MWB might fix this issue but creates a security and safety problem. If MWB is indeed the problem I would think Microsoft and Malwarebytes ought to get together and resolve it.

I should note that in the last three days there have been two separate MWB updates requiring a restart. You might want to try reinstalling MWB on your new machine.