Latest Version of Malwarebytes

[DavidE]

Well, I see you have a lot more "different" real-time security than me ...
So, I can't duplicate your scenario ...

I did the full uninstall, reinstall thing before I restored a system image. It seems obvious an automatic update must be at fault since the restored system image immediately exhibited the same issue, even though it was working fine then, and for days afterwards.

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) ...

 

[A Guy]

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

 

[A Guy]

Looks like fixed.

https://forums.malwarebytes.org/index.php?showtopic=148770

Odd, but wish I'd have found it before all my playing

A Guy

 

[ThrashZone]

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.

 

[A Guy]

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

 

[Layback Bear]

I wonder when the beta is going to be over and Malwarebytes is ready for Broadway.

 

[Slartybart]

I wonder when the beta is going to be over and Malwarebytes is ready for Broadway.

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.

 

[ThrashZone]

I wonder when the beta is going to be over and Malwarebytes is ready for Broadway.

Looks like 2.? what ever is going prime time it's been pestering me all morning,
Cheers.

 

[Callender]

MBAM current version

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!

 

[ThrashZone]

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.

 

[Callender]

MBAM Forum

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.

Thanks! The dump was attached for information and wasn't meant as a request for help. I guess that I'll have to stick to v1.75 and alternative products for now. I figure that the driver still has a few bugs to be ironed out .
if enough users are experiencing the same problem.

 

[ThrashZone]

Hope you like pestering popup messages,
1.75.... produces plenty,
Had to turn it off it was getting so annoying,
Cheers.

 

[Callender]

Pop ups?

Hope you like pestering popup messages,
1.75.... produces plenty,
Had to turn it off it was getting so annoying,
Cheers.

I think that "pop ups" must be my middle name! I know what you mean.

Anyway after some digging about it seems hopeful that MBAM 2.0.1.1004 is now working on my machine! I can't really say for sure as the scan hasn't fully completed but no BSOD so far.



Changes made to my machine so far:

Deleted:

C:\Windows\SysWOW64\Drivers\uziymtuy.sys (Incompatible driver for AVZ AV configured to scan on demand only. The driver wasn't loaded anyway).

Deleted:

Hidden task that didn't appear in Task Scheduler but was shown in the registry. Appears to be a leftover from software that was uninstalled a long time ago.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\iolo Process Governor]
"Id"="{44219ABF-5366-4EBE-A485-671797EE5CDD}"
"Index"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{44219ABF-5366-4EBE-A485-671797EE5CDD}]
"Path"="\\iolo Process Governor"

Also there were a couple of invalid entries in msconfig Startup tab for CCC.exe and also Wordweb along with invalid file paths left behind after I'd run the AMD Cleanup Utility a few months ago and installed the graphics card driver without Catalyst Control Centre.

Configured the MBAM scan to exclude two encrypted drives and another non windows partition.

To sum up - one or several of the above seems to have been the cause of the problem but I can't say for sure which one(s).

I'll try different options for the next scan in around a week or so.

All the best.

 

[A Guy]

The public betas were actually the fix for my BSODs. Not had any, or any system slowing/freezing since the 1st beta. A Guy

 

[ThrashZone]

The last thing I want for a any type of security is a version called Beta

 

[Britton30]

The public betas were actually the fix for my BSODs. Not had any, or any system slowing/freezing since the 1st beta. A Guy

Did the extra icons go away too?

 

[A Guy]

The public betas were actually the fix for my BSODs. Not had any, or any system slowing/freezing since the 1st beta. A Guy

Did the extra icons go away too?

Fixed that too

http://www.sevenforums.com/system-security/240099-latest-version-malwarebytes-39.html#post2778399

A Guy

 

[Britton30]

Good to know Bill, I followed you to the MBAM forum, but don't quite understand your fix from the poster there about "backup admin account".

 

[A Guy]

I logged into the built in (hidden) admin account

http://www.sevenforums.com/tutorials/507-built-administrator-account-enable-disable.html

And ran the update. Which worked. Disabled that account again, logged back into my account, and the problem was gone. Don't ask me why, some permission was reset I'd imagine. All I know is it worked!

A Guy

 

[andrew129260]

The last thing I want for a any type of security is a version called Beta

The more people that beta test though, the better the product becomes. That is however, if the maker of the software actually responds to the feedback instead of ignoring it.

Virtual machines are fantastic for this purpose. I do not recommend installing beta software on your main pc.