gunter

To MWB's credit - the browsing history collected is limited and does seem to be for the purpose of detecting exploits. Nonetheless - MWB needs to make such data collection free of the ability to trace back to the submitting user.

Honestly you are starting a debate. It's bad enough that you know who I am when submitting data - it's far worse that you claim the right to share my private information. The litigation against Facebook, Google and other huge software companies - along these same lines - and honestly with far less concerning infractions should serve as a wakeup call.

Maybe I'm a staunch Republican - living in a Democrat area in the USA - or vice versa - my browsing history reflects this. Bad enough that MWB knows this - but you're allowed to share this information as well. Or maybe I'm a devout Muslim - but very worried about reprisal against my religion. My browsing history reflects this. And I've just disclosed to MWB my religious beliefs. Or maybe I'm GLBT - or for/against abortion - or for/against gun/rights - or for against whatever - the point is, MWB has no reason to trace this information back to me. And certainly has no right to share this information with others.

Given the above... quite honestly... why on earth would I ever, ever consent to using this tool?

Well, it seems that you've covered yourself from lawsuit... I suppose... maybe. But quite honestly this isn't good enough. If you must track any information such as this, you should do so in the following fashion: MWB may collect information about the sites you have visited. However, all data collected by MWB is annonomized - and is completely untraceable to an IP address or any other datum capable of identifying the submitting user. Instead, you have a wall of text which allows the collection of such information - and get this - you're allowed to share this information with others.

WRT privacy - my browsing history is private to me. If I am sending this information to you it should be clear that I am doing so. I do not recall having given permission for this information to be sent when using the FRST tool (but I may be mistaken and would be happy to be corrected). WRT inability to replicate a problem experienced by numerous users - unacceptable. And quite honestly unbelievable. You know the machine specifications for machines that are affected; you know the timeframe when the bug occurred; you know the symptoms for the bug. Worst case, you could have (prior to covid-19 outbreak) sent an engineer with kernel debugging tools to one of your customers with the bug - now with covid-19, is there a possibility of remote kernel debugging with one of your customers? - I haven't kept pace with dev tools so maybe or maybe not this is possible. In any event, completely unbelievable to me that this hasn't been addressed.

@jamalot71 >> With all due respect to everyone at Malwarebytes, this is totally unacceptable. I too am extremely disappointed with Malwarebytes response to this bug. There's been little to no insight into what developers are doing to resolve the bug (some posts indicate that they cannot reproduce the issue); instead, the support advice has been largely boilerplate. Do the usual x-y-z stuff to make sure you haven't got a bad install - then delete your install and try again - submit logs - and if everything else fails, disable the web protection feature or go back to a previous version. I was nearly at patience's end - having experienced this bug for months on end - but I thought - OK - I'll go ahead and submit the requested logs. I ran the support tool once the host resolving issue occurred - it hung. Fine... I rebooted my machine and ran the log gathering tool again. I was about to submit the logs - but then I thought... hang on, just what am I sending. So I examined the log files with a text editor. It turns out that the logs contain a list of some of the sites you have visited. To me, this a huge privacy concern issue. That was the last straw. I've been a loyal Malwarebytes customer for many years and have benefited from the product and especially from the free support for removing malware provided in other parts of this forum. But inability to diagnose a severe problem ongoing for months on end with numerous users complaining about the issue, support tools sending information that you might not want to be shared for privacy reasons, the same boilerplate response to everyone complaining about the bug, very little insight into what developers are doing to address this bug, no list of known bugs (that I can find), and so on... I gave up and installed a competing product.

@AdvancedSetup: >> You need to help us help you Let me turn this on its head. I'm a software developer with decades of experience, developing both user-mode and kernel-mode applications. I've worked first hand with QA/testing personnel/customer support to resolve numerous bugs. At this point, >> You need to let me help you. How so? 1) Bring this bug forcefully to the attention of the Malewarebytes development team. 2) It's hard for me to believe that the development team cannot reproduce this bug - but if so, some sort of remote debugging may be called for. When the bug next appears on my computer I'm more than willing to let a Malewarebytes employee debug my machine. === If you're still reading... You should know that I completely unintalled Malewarebytes and then resinstalled using your support tool. That didn't fix the problem as I was almost certain that it would not. I'm now running your support tool in an attempt to collect logs. Unfortunately, the tool is now stuck for hours on end in the "Run FRST" portion of troubleshooting. If the tool completes within the next 10 to 12 hours (it's already run for about 8 hours) I'll post those logs. If not, I'll need to reboot and run the tool again - against a system that is free of the bug - for whatever that's worth - likely worthless as you've received numerous such logs already. === I'm pretty sure that at this point I'm not going to use MWB anymore. Final feedback - this volunteer bug support forum without recourse whatsoever to the development team and/or elevated bug response is a huge disappointment. I would not switch products if I knew that development were actively pursuing a fix to this bug or that development was directly asking for my help. This is not to diminish the help provided by volunteer support - I really appreciate your contribution. However, at some point the development team itself needs to be brought into the loop. That point, for this bug, has long, long since passed.

The problem I'm having is that over time, host name resolution becomes slower and slower, eventually to the point where resolving host names is so slow that a reboot is required. I've eliminated the possibility that this is a DNS issue - as host resolution using the command line tool nslookup provides instant name resolution, with no delay whatsoever. This problem has been going on for several months now. I don't want to install a previous version of Malewarebytes nor do I want to risk disabling web protection. I really have liked using Malewarebytes up until now and I've used the support forums to help me out with some maleware that made it onto my computer. In spite of this, I'm in a predicament - either I have to live with rebooting my computer every 2 or 3 days (sometimes I can't do this as I've long running programs that can't be terminated), or disable website protection - I really don't like that idea - or, ultimately, look to another product for maleware protection.

Hello: Can you please let us know when (or if) the problem with website protection will be addressed. As far as I can tell there's no open post currently in the forums discussing plans for the next beta.

Would it be possible for you (or me?) to check with the development team about this? For those of us affected, it's probably a deal breaker with respect to continued use of MWB. I'm more than happy to help troubleshoot this problem if necessary - but if it's already reproducible, I'd rather not make the unnecessary effort. Thanks for your help on the forums.

If no fix becomes available, MWB is unusable for me. Based on your request, MWB is unable to reproduce this problem? Is this correct?

Apparently the resolving hosts issue is a known bug. I've no idea when this might be addressed though as I can find no mention of plans for the next beta.

Hello: I've been having this same issue for several months. The symptoms/observations I have are as follows: 1. After several days, I have trouble accessing the internet due to extremely slow "resolving host" issues. 2. Host resolution occurs when using my browser (chrome), as well as when I use the "ping" tool from a command prompt. 3. However, if I use nslookup, host resolution is immediate. 4. To resolve the problem, I simply reboot and it goes away for several days only to eventually resurface. 5. Just to completely rule out some sort of DNS server issue, I've changed from comcast dns to google and it does not help. ======= Conclusion: Either a Microsoft update has somehow affected by computer. However, due to the apparent absence of this issue on Microsoft Forums and google searches, I think that this is unlikely unless the issue is specific to a small set of computer configurations. As I read this article, it seems more likely that the culprit is Maleware bytes - but I've done no testing of this theory. Anyhow, I too have a slow host resolution problem and I welcome help in trying to overcome the issue.

I wanted to address this threat as soon as possible. I hope you don't mind... I took the liberty of examining the resolution of this issue as described in several other posts. I carefully followed the remedy listed there (i.e., temporarily disable anti-virus and run zoek.exe with the script and then re-enable AV). After taking this remedy I ran a Malewarebytes scan and it came up clean. Please close this issue as it seems to have been resolved.