Latest Version of Malwarebytes

f14tomcat said:

Just posted mine under both ya!

Malwarebytes 3.6.1 WER Report - Malwarebytes 3 Support Forum - Malwarebytes Forums

Attachment 204817

Ahhh, so it hit you too TC Glad you posted, Welcome to the club

I see someone posted that it was to do with self protection but that would be on startup not shutdown.

kado897 said:

I see someone posted that it was to do with self protection but that would be on startup not shutdown.

He said it fixed the issue Keith, I have not tried it myself.....Also someone suggested turning off Fast Startup .....mine is always off.

OldMike65 said:

He said it fixed the issue Keith, I have not tried it myself.....Also someone suggested turning off Fast Startup .....mine is always off.

I have it on but not the early start feature and I only got the error on the first restart.

Just a wild guess..... the self protection code is causing it somehow to not allow a clean service shutdown. MBAM Service is going out kicking and screaming! And barfing!

f14tomcat said:

Just a wild guess..... the self protection code is causing it somehow to not allow a clean service shutdown. MBAM Service is going out kicking and screaming! And barfing!

Yup someone reported turning it off, fixed the crash issue.

Running the paid version and unless it just hasn't updates on it's own, I'm leaving it alone till one of y'all posts it's fixed. LOL, Is there any indication AVAST might be involved?

Wiley Coyote said:

Running the paid version and unless it just hasn't updated on it's own, I'm leaving it alone till one of y'all posts it's fixed. LOL, Is there any indication AVAST might be involved?

Well after chatting with one of the tech's on MalwareBytes forum, it does not sound like they intend to fix this small bug that we have reported anytime soon, as they don't think it needs to have a Quick fix issued at present time. They said in their next released update which could be in a few weeks they will address this issue then.

OldMike65 said:

Well after chatting with one of the tech's on MalwareBytes forum, it does not sound like they intend to fix this small bug that we have reported anytime soon, as they don't think it needs to have a Quick fix issued at present time. They said in their next released update which could be in a few weeks they will address this issue then.

That's the impression I got from the forum. They have managed to replicate the problem and will probably just let it run until the next update.