Well, I see you have a lot more "different" real-time security than me ...
So, I can't duplicate your scenario ...
Can you restore the System Image with the network disconnected ?
Unplug the LAN cable, disable any network wi-fi devices ...
Then there could be no auto update before you have control and can change the settings so MBAM does not auto update (after the restore) ...
I could, but I won't :) It's bed time for Bonzo, and I already redid all my programs and Windows Update. I can try it again after making new images this weekend, if they don't fix it before then. I did see a poster complaining about 2 icons. He was asked to right click each> properties> Path. But mine disappear as soon as they are hovered over. Suspect each check for updates is creating a new one. MBAM does appear to keep running when they are gone. A manual check for updates crashes MBAM. A right click on a file, scan with MBAM works correctly. A Guy
Looks like fixed.
https://forums.malwarebytes.org/inde...owtopic=148770
Odd, but wish I'd have found it before all my playing :)
A Guy
I'm starting to get a popup which states a new version is available and it's important to have the newest version,
I know what mabm is referring to but 2.0 isn't going to happen yet,
Still too green at the gills,
Cheers.
To be quite honest, beyond this latest weirdness, the last few betas have been no issue. I run custom scan with rootkit with no issue. It takes a long time to right click, scan an individual file, but how often do I do that? Looks like they are almost there for you old holdouts
A Guy
AS far as I can tell Jack, Malwarebytes considers the 2.0.1 beta over. If you go to the Mbam download page, you get version 2.0.1.1004
2.0.2 Beta is up to build 1012 which seems fairly stable.
There are however a number of GUI issues.
Daledoc1 on Mbam forums has a good handle on the status and makes excellent suggestions to the developers.
Hopefully 2.0.2 will be ready for primetime in a few weeks or a month. The developers are fixing things as they are reported - but sometimes it's two steps forward, one step back.
My take: the presentation issues in 2.0.2.1012 are annoyances, the stability is far better than 2.0.1
- it's not yet Release To Manufacturing (RTM) material though.
The current (non beta) version seems to be MBAM 2.0.1.1004 or at least that's the one that appears on the MBAM website. It's also the version that gets downloaded by UVK if no other versions are installed - otherwise it uses the currently installed version.
It still makes use of the swissarmy.sys driver that is also present in the beta releases and seems to cause BSOD's on my machine. If I stick with MBAM 1.75 it doesn't use that driver and works just fine.
Dumps attached. I've seen pretty much the same problem with an Avast driver on my machine so stopped using Avast!
I'm sure that dump would be better served on the mabm forum ?
I'm not sure why mabm is pushing this new product so hard now,
Seems it only hit the market 4-5 weeks ago,
Possibly they what more feedback,
Cheers.
Quote
