Jump to content

Merik2013

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Just reinstalled and things seem to be in working order again. I appreciate you comments in regards to the resolution of this situation and trust you'll follow through with the stricter protocols.
  2. I second this. I don't want a simple "It's fixed now, please update" response. I demand a full explanation and apology here. This is inexcusable.
  3. Yeah, I couldn't remember how to do this at the time. The whole mess had me too distracted so I just went for what I thought was the easiest solution.
  4. What the heck did you code monkeys do now? Malwarebytes is acting like a damn virus. You've turned an antimalware program into a trojan. Great job there guys. My computer just had a meltdown because of this. Every time I'd kill the process the damn thing just started back up again and started climbing up the process list taking with it every once of free RAM until the entire system hung. Stopping the service didn't help at all either as that just rebooted on its own as well. I had to go into the folder, kill the process, stop the service, and launch the uninstall exe in order to put an end to it all. My system is now unprotected thanks to your blunder, so thanks for that. Not that it was protected while this mess was going on, mind you. It kept disabling all the protection. I'll be honest, I suspect foul play here. I understand bad patches happen, but this particular behavior can be seen as particularly suspect depending on how you look at it. Like it might be the work of a hacker using our systems for some ill process, or an act of sabotage from a malcontent employee. I honestly don't know what to make of this mess, but its one hell of a screw up.
  5. I frankly have never even heard of f-secure and therefore do not have it, so there's no way it's the source of the issue. Regardless, I just got another update notice and this time it worked properly, so either I got lucky or the devs just pushed out a hotfix.
  6. This error is now occurring for me as well after attempting to update today. At the end of the installation I got errors about it not being able to stop a service (it did not specify, so I'd advise the devs to make it do so in the future if they think it will help with error reporting in the event of a similar error cropping up) and now mbam simply refuses to boot and is giving the error mentioned by the OP, leaving me with no real malware protection on my computer. I'm still not even convinced that Discord had any actual malware on their system so as far as I am concerned this is two strikes in the first month of the new year alone. I'm on Win7 btw, so this is not a Win10 problem whatsoever. Just thought I'd clarify that.
  7. As far as I can tell, this isn't true. my definitions are up to date and I'm still getting warnings. In fact, it sounds to me like you aren't up to date. The latest definitions were released today, on the 14th. The ones you name appear to be 10 days old.
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.