I love the software, but its claims to replace an anti virus seems to fall a bit short in my experience, can't always get it to work normally without disabling the above part. I've had issues with the home version before, disabling the web protection fixed every problem I've had. It's not something we support, but figured I'd dig for information on if anyone else has experienced it. I've just scripted an uninstall and pushed it out via our RMM tool to be rid of it. That's what makes me think it's messing with the DNS client, because sometimes you'll see NLA being broken as well and it defaults to public firewall. I've done the whole dns flush, winsock reset, set static IP/DNS, etc. Mapped shares via hostname are still accessible as well. You can ping by DNS locally, but nslookup times out whether it's internal or external and no web pages load. After a reboot, everything works for up to a few minutes and then DNS queries fail to resolve. Rather curious how they got on the workstations in the first place.Admin rights for end users perhaps?Potentially, but it fails under the local admin profiles too.
#Malwarebytes 3.1.2 anti virus trial
The ones I've seen today have all been the trial install. Honestly I think it's the free home version. Hard to convince an office of 3 that they really need a domain controller and server just to login to run a console session to an old RHEL server.
#Malwarebytes 3.1.2 anti virus download
I can confirm that the affected version(3.) is still the primary download from their website.ĮDIT Amplifying info: This only seems to occur on computers that aren't domain joined. I've heard, but haven't personally seen, that there is talk of this across other forums. Looks like an issue with their web filtering module. Removal and a reboot clears it up instantly. Different networks, different OSes, the only common trend is malwarebytes itself. We're now starting to see a second catastrophe that it looks like the version of MBAM installed Friday evening is breaking DNS resolution for my clients all over the city. (In short, I was ignored when bringing it up early on friday, and then someone panicked over the weekend and slung a few hundred patches at ALL of our managed servers, causing constant reboots and disk activity) So, after dealing with the fallout from a somewhat self-inflicted apocalypse from WannaCry.