Discussion in 'other anti-malware software' started by puff-m-d, Nov 14, 2016.
I've emailed you mine.
OK, we've identified the issue and we'll have it fixed in the next component update. In the meantime, either reboot the machine or Exit the application through the tray icon and restart it. Sorry again folks, a few little hiccups here .
Any rough time frame for the fix?
I exited the application and restarted it and each time I receive a popup showing that a layer of protection is turned off. I could see that the web protection was off but would come on not too long after the popup. I suppose it's a matter of timing. Can shutting down and restarting the app during an update cause this? This did it 2 out of 3 tries. First 2 tries gave me the popup and the 3rd was normal.
edit: The hanging update seems to be fixed.
Still no issues here with the latest version of all my security software and no features disabled. Really liking the new version of MBAM.
Nope! Not fixed here. If I manually run Update after starting MB 3.0 it updates OK, but the next automatic update and it's back to checking.
You're right. I spoke too soon. Momentarily fixed.
In the FAQs it states:
To ensure there are no conflicts between two real-time anti-malware scanners running alongside each other, would it be wise to exclude each program in each other's exclusions list?
Must it nag me, and demand my attention on every startup, if I have a shield disabled? I can't have exploit module on because it blocks Chrome from opening, and I can see the nagging getting tiresome quickly.
Even if it just went away after nagging me, but I have to go to it and close it manually.
Not fixed here either. "Checking..."
running windows defender and malwarebytes 3.0 together and no problem so far.
If you have issues with the updates please try this:
1- Stop the MBAMService service
2- Delete the file UpdateControllerConfig.json
3- Start the MBAMService service
Does this resolve it?
What's the location?
You can just search your C: drive. But it's somewhere under C:\ProgramData\Malwarebytes\ (don't recall the exact location atm).
Interesting program, but not ready for prime time yet. There are still too many bugs that need to be ironed out. Instead of releasing a half-baked program, the Beta testing period should have lasted a little bit longer. Don't get me wrong, my Malwarebytes friends, I do like MBAM but it just isn't ready for public release yet. Just my two cents.
Found it. I'll have to wait and see next time MB automatically checks for updates. Manual updates seem to work OK.
Edit: I see the Component Package version is now 1.0.0. I hope that's right!
This is a bug that was caused by a component update we pushed (from 1.0.39 to 1.0.40)
There is a race condition in the code where it gets stuck. We're working on a fix now, but if anyone has the issue, try these steps:
1. Right click on the tray icon and click Exit.
2. Restart the application.
3. If that does not work, close it down again and delete C:\ProgramData\Malwarebytes\MBAMService\config\UpdateControllerConfig.json
3. Restart the application.
Unfortunately, all software must be released eventually. It's a matter of finding as many bugs as possible before then.
To put it in perspective, we already have 300,000 users on MB3 and maybe 100 or so reports of issues. Sure, there are quirks, but the number of bugs has been relatively low.
So after that the correct Component Package version is now 1.0.0?
No, can you click Check for Updates and see if a new one gets delivered?
It says I'm current. Still at 1.0.0, so no new version delivered.
Replying to email.
Each time it is mentioned to exit protection and then start it again some of the protection does not come back on automatically. Earlier, web protection was slow to come on and now malware protection doesn't automatically start and won't start manually.
There is nothing "unfortunate" about releasing software; it just shouldn't be released before it's ready for public release.
... which does not necessarily mean that the other 299,900 MB3 users have not run into any problems.
Relative to what? Relative to ALPHA software? Maybe. Relative to BETA software? No, definitely not!
Separate names with a comma.