[Possible False Positive - Malware.Heuristic.1003]

For some reason part of my post got cut out - found that my expert system algorithms were turned on. Once turned off - issue was resolved.

[Possible False Positive - Malware.Heuristic.1003]

Just to be clear - ensured that MB was completely up to date after a fresh install. Rebooted. No change - still detected the file. I then deleted the file HubbleCache (as directed above) - still no change. Went in and looked at the security settings; found that it was enabled so disabled it. Reran the scan - no false positives this time. I can include a copy of the file in question (was located c:\windows\pe_rom.dll)

[Possible False Positive - Malware.Heuristic.1003]

Still not fixed. Completely uninstalled MB; rebooted; and deleted all files/folders. Fresh install from newly downloaded copy still is detecting this file.

[Another Windows 7 x64 freeze after the 1.0.508 update]

1 minute ago, LAVA said:

You're welcome. I"m glad you found your way over here. However, I would recommend a roll-back to Component Package version 1.0.418 so you have full protection online.

There are many other Windows 7 users out there trying to troubleshoot their systems by throwing good money after bad, along with a lot of wasted time and productivity. 

In almost every case, nobody suspects MBAM software to be the source of their problems.  Affected users start testing RAM, swapping video cards, changing drivers, power supplies, mice/keyboards, updates, etc... until they do a search on 'Windows 7 Freeze MBAM', or someone tells them about the issue, the problem remains unsolved (for weeks in some cases).

I know the MBAM staff has been working on the issue, but a few of us indicated the problem was likely more widespread than they realized (partly because it was holiday break). If you look at our profiles, you'll notice many of us are new. i.e. We've been cruising along for years without any issues on Win7 + MBAM, and many of us are computer or IT veterans.

More sites are encountering the issue and are surprised when they are informed the problem lies with MBAM.  A few prominent sites are questioning why Malwarebytes hasn't 'taken ownership' of the problem after 3 weeks with some sort of advisory or annoucement.  This is a PR disaster in the making, yet they had a chance to get in front of it 2-3 weeks ago...

One editor wondered if the problem was bigger:  "How many Windows 10 users encounter this problem and just 'chalk it up to MS' and Windows 10 updates?  Hello MBAM?"

 

 

Exactly what happened to me - two systems; only one was experiencing issues at the time. I spent days switching hardware around trying to figure out what was going on. I even ended up reinstalling windows numerous times. Eventually ended up buying a new power supply; switched it out; and then the other system started having issues as well - and then I found this thread. Turning off the web protection did the trick for both systems. Not mad about the new power supply because I'm looking to upgrade video boards so will need it eventually anyhow. I understand that things happen - but a bit more transparency with user-base would be nice.

[Another Windows 7 x64 freeze after the 1.0.508 update]

Adding in my two cents as well:

I also suspect that this is a much more prevalent issue than what is being reported - just simply most users experiencing this issue haven't figured out (yet) that it's malwarebytes causing the issue. Speaking from personal experience, I had 1 system that's been locking up intermittently since around December 13th, and the 2nd system just started locking up about a week ago. Both sets of hardware are pretty near polar opposites of one another.

It's taken me all this time to figure out that it was malwarebytes in both cases. The 1st system - has completely been through the ringer (tested all of the hardware from the power supply all the way to the motherboard; also found corrupted windows files that could not be repaired - so it's a clean install). The 2nd system - I thought it was windows registry issues - so to has a clean install.

Long story short - I'm baffled by what's causing the issue, but using the trick of disabling web &/or ransomware protection has resulted in zero lockups.

[Possible conflict between Malwarebytes and Avast]

Just wanted to post a follow up - as stated - the Real Site Protection needs to be disabled; also - I found that Avast's "Do Not Disturb" option is still causing system sluggishness and often an inability for windows to shutdown correctly (contrary to the posts in Avast's forums - it is apparently not fixed).

My final temporary solution to all this (until things are sorted out) is to completely uninstall Avast's "Do Not Disturb" module, and set Malwarebytes up to turn on everything excluding "Web Protection". By doing this, my systems stability has been completely restored. I'm sharing this in the hopes it may help others!

[Possible conflict between Malwarebytes and Avast]

I should have added that into my post as well - I have added in the entire folder exclusions for both programs as appropriate.

[Possible conflict between Malwarebytes and Avast]

Confirming as well.. both programs have been "playing nicely" together until avast's most recent patch. If both programs are running, I experience a multitude of issues - inability to open/load programs; sluggish &/or no response from the PC; frequent lockups; inability to properly shutdown windows - just to name a few.

 

I've gone so far as to completely reinstall windows etc thinking the update caused some sort of registry corruption. I've also put the following exclusions in avast:

 

AV Exclusions List with paths...

• C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
• C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe
• C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
• C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
• C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe
• C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
• C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
• C:\Windows\system32\Drivers\farflt.sys
• C:\Windows\System32\drivers\mbae64.sys
• C:\Windows\System32\drivers\mbam.sys
• C:\Windows\System32\drivers\MBAMChameleon.sys
• C:\Windows\System32\drivers\MBAMSwissArmy.sys
• C:\Windows\System32\drivers\mwac.sys

 

Also the following folders to: (The complete folder)

• C:\Program Files\Malwarebytes\Anti-Malware
• C:\ProgramData\Malwarebytes\MBAMService

 

Bottom line is that their most recent patch severely broke something, I'm just not sure exactly what. I had to turn off all the active protection of Malwarebytes to get things to run (easier than gutting all of avasts settings).