afbergner

Started the service again and clicked the check for updates button before the RAM climbed too high. The update installed, but I needed to shutdown/restart the app. Everything appears stable on my box now. Malwarebytes version: 3.3.1.2183 Component package version: 1.0.262 Update package version: 1.0.3803

...and then update their resume.

Do you realize that the software requirements for MalwareBytes do not list Windows Server as a supported OS? It's only for Windows client. https://www.malwarebytes.com/pdf/datasheets/MBRTDatasheet.pdf

Windows said it couldn't stop the service for me. If you've disabled the service and restart your system it should remain off when it comes back up. Just a tip.

You don't remember the McAfee fiasco about eight years ago where they released a definition update that classified a Windows XP system file as a virus? Blue Screens of Death for everyone!

Just a word to everyone saying "I've had enough of Malwarebytes - I'm going to switch to something else"....Switching to another program can potentially bring different problems. Every antivirus product I've ever used has had an issue here and there. Even Microsoft releases buggy updates, and here we all are still using Windows. Just sit tight. They'll fix it.

High memory usage here as well. Never had a problem like this with the program. My system was running fine last night. Woke up this morning and it was locked up. Restarted, and it was almost non-responsive. When I finally got task manager to come up, I saw it was using 11GB out of 16GB of memory. My system couldn't breathe. I killed Malwarebytes from my taskbar and everything returned to normal. I started it back up again and watched it slowly slurp up all available memory. I also saw notifications that Malwarebytes protections were being turned off, probably due to not enough memory

The latest version of the Windows Offline Generator tool (found at http://download.wsusoffline.net/)isbeing detected by MalwareBytes as malware (Trojan.Agent.AutoIt). I've attached a copy of the executable (zipped with the password "infected") as well as my Malwarebytes log file. The file was submitted to VirusTotal and Malwarebytes was the only scan that showed it as infected: https://www.virustotal.com/en/file/01102d62e224487771e34165ccc7946bcfb578620eae5a34e968c757d932cd58/analysis/1454169358/ Thanks, --Aaron MalwareBytes Log.txt UpdateGenerator.zip