MarkieVee

Hi, we have Windows 2016 running RDS as a VM Virtual Server - we installed MALWAREBYTES and since doing that the VMHOST has crashed twice. The client has a MWB4B license and that is the version we have installed. Are there any specific steps that need to be taken to install the software ? Regards MV.

thx YoKenny1 running that now .. it flashed up once but nothing registered on the CurrPorts ... I'll keep on keeping on Mark.

Malwarebytes pops up several times a day saying it has blocked access to 62.45.13.134 Is there any way of finding out what is trying to access that address? and/or what that address is being blocked for ? Regards Mark.

As I said, I fully understand and appreciate MalwareBytes good intentions. My concern is that as a paying customer, as Joe Bloggs sitting at his PC - your product is blocking me from accessing websites, blogs and IRC servers that I trust, and in my case, for whatever reason I received no notification that this was being done. From my view-point you are the ones blocking the access, and therefore the ones that I would take issue with. I have no dealings with the hosting companies who host these sites and services and nor should I have to (unless of course it is my own website / service being blocked). I am, as an end-user who wishes to protect the integrity of the security that MBAM provides, essentially unable to progress as I can't access the sites to inform the site/domain owners of the issue (other than by by-passing the IP Protection - which I am recommended not to do) this puts me, the blameless end-user in a catch-22 position, which could drive me away from your product. My extremely high regard for MBAM's faultless malware detection prevents me from doing so I would warrant most end-users of MBAM would not think "oh the website is being blocked, I'll email the owner to get him to speak to his hosting company about responding to MalwareBytes abuse reports", their response is more likely to be "oh I cant access the website, I'll just disable the IP Protection feature." My personal response has been to disable IP Protection, I hope purely for the time being, but which if carried out by an equally frustrated and sizeable enough percentage of your customer-base, would mean that MalwareBytes is investing in developing a product feature / technology that their customers don't use. I apologise if it feels like I'm being pernickety or overly critical - I love MBAM and recommend it endlessly to friends, colleagues and clients alike, I want to be secure in my use of the internet, but I also want some flexibility and control over the processes involved. Mark.

I have after much head scratching realised this IP Protection (which previously never worked on my PCs) has suddenly started working and just blocked a lot of (5) servers I use for different functions - it did not as I believed it would display a message bubble to tell me it was doing this. Hence a lot of scrabbling around checking DNS servers, network settings, firewall settings etc. I understand the well intentioned actions of MalwareBytes, and that this feature may be useful to those with less internet experience, however I feel that at present the criterion for being black-listed by MBAM is far too broad a spectrum, bordering I feel on some form of protectionism/black-mail (respond to our email or we will block all your sites) and where no white-listing or "ignore" option is available. I did not purchase MBAM for this feature, I purchased it for its Malware detection (which I can choose to white-list BTW) and so I have therefore decided the IP Protection feature is not for me and disabled it. Mark.