Jump to content

jayt12

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jayt12

  • Rank
    New Member
  1. maybe different software versions too. For us the files are "ren "%ALLUSERSPROFILE%\Malwarebytes\Malwarebytes' Anti-Malware\rules.new" rules.new.1.27.18". For us killing the mbabservice.exe and a hard reboot generally fixes it after 2-3 mintues on next boot. On troubled machines deleting the rules.new and rules.ref files seems to work. No easy way to hit all of the machines that have the issue though...
  2. For us it looks like killing the service hard booting the machine, logging in waiting 2-3 minutes and rebooting resolves the issue. Sometimes we kill the rules.new rules.ref files on problematic machines. About the support lines. How do we contact? It says M-F and a webform to submit a ticket. I submitted a ticket 4 hours or so ago.
  3. How do we got those machines to that DB version? It appears the issue is with 2018.01.27.02/03. None of the pc's can do anything on the network, so far just disabling and solved getting on the network, but not updating the DB. Only solution to uninstall? Can you verify exactly which db versions have the issue, I have a couple hundred at 2018.01.27.02 that appear to have issues, but I also have a few hundred of 2018.01.26.08 that are also offline. Are you going to open up your support lines?
  4. All of our win7 machines are still having issues from the bad dat. Rebooting doesn't search for new dats, trying to ping out on the affected machines receives general failure responses. We're running anti malware and anti exploit. The only solution seems to be to disable the malwarebytes services, after restarting them have same issue and it never updates. db info = 2018/01/27 10:30:31 -0500, think some also have an 11:57 one that doesn't work as well. All of the other solutions seem to say reboot/update fixes it, but not on ours. If we hit check for updates it says it's at the lat
  5. All of our win7 machines are still having issues from the bad dat. Rebooting doesn't search for new dats, trying to ping out on the affected machines receives general failure responses. We're running anti malware and anti exploit. The only solution seems to be to disable the malwarebytes services, after restarting them have same issue and it never updates. db info = 2018/01/27 10:30:31 -0500, think some also have an 11:57 one that doesn't work as well. All of the other solutions seem to say reboot/update fixes it, but not on ours. If we hit check for updates it says it's at the lat
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.