Jump to content

exile360

Experts
  • Content Count

    29,580
  • Joined

  • Last visited

  • Days Won

    21

Everything posted by exile360

  1. Greetings, The only thing I can think that might cause this would be if the software was being reset to default settings or if it was having some kind of issues with its configuration files/data files and falling back on the backup files containing the default settings. It may be useful to get a set of logs showing the details of your installation to see what might be happening: Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Gather Logs button, and once it completes, attach the zip file it creates
  2. Sure, and if they're too large you can upload them somewhere like WeTransfer.com and post the link. I'm sure the Developers would find them useful in tracking down these issues. Thanks
  3. There was an issue with the last version of Malwarebytes (the one preceding component update 1.0.508) that would show errors in the even logs every time the system was shut down. I'm not aware of any other errors in the newer builds.
  4. OK, so the problem is present even with the older build of Malwarebytes? I guess you'll need to keep Ransomware Protection disabled until this gets fixed then but at least you can install the latest version of Malwarebytes (assuming there are no other issues with it on your system) and hopefully they'll have this resolved in the next release (version 3.7).
  5. That's OK, they might be storing their data files somewhere else like under one of the local user data folders under C:\Users\<user name>\Application Data. You can try to locate it to exclude but the main thing is excluding its primary program folder which you already did. As for the support tool, it can take a while to run sometimes. It has to download FRST and run that (you'll likely see an icon in your system tray while it's running/scanning to create the logs) and it should finish after a few minutes unless something is preventing it from working properly.
  6. That's correct, the issue with the errors in Event Viewer from Malwarebytes during shutdown occurred in the last version as the result of a bug that was actually fixed in build 508 that was related to the self-protection driver and/or MBAMService.
  7. No worries, if your hypothesis is correct about it not scanning then chances are that if they do address it, they'll likely build it with the same kind of heuristics that most of their other scanning components use meaning it will be likely to catch a lot of undesirable items and they've already got a pretty good collection of known malicious sites, ad servers and other undesirable websites thanks to the Web Protection component, the hpHosts database as well as the new browser extension beta (which you might try by the way if you haven't already, as it may block these, but even if not, it will
  8. Greetings, I'm honestly not certain if it does or not, though I do know that it does scan Chrome's preferences for malicious plugins/extensions and the like. I'll have to check with the team to see if it checks the notifications/allowed list or not and will request that it be added if possible if it turns out that it does not. If you have any further suggestions please don't hesitate to let us know. Thanks
  9. Thanks for the additional info and links guys. I will be sure to report them to the staff for you so that the Devs are made aware. I hope these issues are resolved soon, I'm anxious for all the bugs to get squashed.
  10. OK, please run the support tool again and use the repair option to see if that corrects it, if not, then please run it once more and collect a fresh set of logs and attach the resulting ZIP file so that we may take a look at what's going on. Thanks
  11. Greetings, It's most likely the Ransomware Protection component causing this issue, so if you disable that for the time being that should alleviate the problem. The other workaround would be to revert to the last build of Malwarebytes until they get this issue fixed. As for why they are requesting logs, it is because the Developers are still working on this issue and attempting to track down the exact cause, so the more data they get from affected users the better, however if you do not wish to provide any logs/data then of course you don't have to and you can just wait for the fixe
  12. Interesting, I've got the update but not the issues (though I don't use any network shares as I have all such functions disabled and/or crippled on my own system for security reasons). Hopefully they get it fixed for the sake of those users who are affected soon though. Looks like Windows 10 users aren't the only ones feeling the pain of poorly implemented patches these days .
  13. Sure, no problem, thanks for the information. Hopefully it won't be necessary though and you just won't get infected again, at least I hope that's how it will be, because we definitely don't want you (or anyone else) getting infected with anything.
  14. Greetings, I suspect this may be caused by a conflict with the latest version of Malwarebytes and AVG. If you disable the web shield/web protection component in AVG, does that resolve the issue? If so, then you may try creating exclusions in each program for the other to see if that helps, otherwise you'll likely have to wait for this issue to be resolved in a future version of Malwarebytes and/or AVG (I believe it's an issue specific to Malwarebytes' code, however I do not no for certain that this is the case). The items to exclude in AVG for Malwarebytes are listed in this suppor
  15. Just FYI, I did successfully confirm the freeze issue on my own system yesterday. I was streaming a video on Netflix at the time with a few browser windows open so not a lot of resource usage or anything particularly unique (I'd been streaming stuff on Netflix for several hours before the freeze occurred, then suddenly it rendered my system unusable starting with the browser and progressing until only the mouse would move). It definitely isn't the Spectre mitigation since I don't have any (no microcode updates for my system since I'm running Windows 7 and I haven't received an updated BI
  16. I did see where a member of Support posted recently that at least some (though hopefully all) of the current known issues would be addressed in the upcoming 3.7 version, however he didn't have an ETA on when it would be available. As for MSE, I haven't heard of any freezes/issues with it and Malwarebytes. I'm running the two of them together here and the only freezes I've had were when I had Ransomware Protection enabled (which I normally keep disabled for performance reasons, though typically it doesn't cause any freezes/issues, although it appears it does for the latest version of Malw
  17. No worries, you don't need to replicate the issue again. Just getting the logs from your system helps I'm sure, as they just want to try and narrow down the environmental factors/software and hardware configurations where the issue occurs as that will hopefully aid the Developers in tracking down the source of the problem in the code.
  18. What response from MB? I don't work for Malwarebytes in case you hadn't noticed, and I guess you don't know much about automated spam filters and the kinds of activities they tend to flag because that's what I'm talking about there. I know because back when I did work for Malwarebytes years ago, our newsletter got flagged by several email providers as spam even though every user who received it had signed up for it and the company had never been flagged before that so it was all about the numbers. Either way it doesn't matter because we both agree that informing more people would have been
  19. No, there's no need for a new topic, I just meant in the future if any other issue comes up. The fact that this topic is so old is why the outdated version of the tool is linked to in the posts above, because they pre-date the latest support tool. LiquidTension will take care of you and should be able to help you resolve or at least work around the issue you're having with the software. As for the other issue you mentioned, all those instances, that's a new one on me. Maybe somehow a scheduled task ran away or something executing tons of instances into memory trying to initiate an upda
  20. That's not what I'm saying. I'm just saying email isn't the way to go. A public posting on their website or a message/notification in the product would be much more effective. Word spreads, especially in the tech scene, and no one is trying to hide anything (they wouldn't have created FAQs about this stuff if they were trying to hide it, and certainly wouldn't be addressing the issues and assisting users in public if they were; they'd force everyone to contact them on the helpdesk to keep it private in email).
  21. This topic is from 2017; in the future I'd recommend creating a new topic of your own, even if it seems like the same issue because often times completely different issues/circumstances can cause seemingly identical symptoms/problems, especially since there have been many Malwarebytes versions released since this topic was created over a year ago. I understand you were just expressing the fact that you seem to be dealing with the same issue and seeking help, but unfortunately the solutions for each may be very different. Normally an automated reply would respond asking for logs using the
  22. I doubt they could ever do that without setting off just about every spam filter on Earth due to the sheer number of users/customers they have, not to mention the fact that Malwarebytes doesn't collect the email address of every user of the Premium version (i.e. trials, not to mention licenses purchased through third party resellers as well as retail boxed versions which only require a valid license key and never prompt for registration via email), so while that certainly would have kept the customers who purchased the software direct from the Malwarebytes website informed, none of the other u
  23. There is a conflict with Avast, however that is not the only cause for this issue (as I mentioned, there are currently multiple AV conflicts with build 508 of Malwarebytes) and it is indeed happening on some systems where no third party AV is installed. So basically it's the same symptoms with multiple causes which may or may not be the result of the same change to the code in the Web Protection component in build 508 (i.e. there may be multiple causes/changes in the code resulting in different issues which need to be tracked down and fixed, but only the Developers can know that for certain).
  24. One of my all time favorites from way back in 1991, long before "Nu-Metal" or any of the other Hip Hop/Metal blends/genres emerged on the scene, Public Enemy and Anthrax were getting down and dropping Thrash Metal with a Hip Hop beat and hardcore lyrics to match: Bring the Noise, 'nuff said!
  25. Yes, and while I know this isn't always the cause (sometimes the issue is caused by the Ransomware Protection component, and sometimes it's not a conflict with an AV at all), we have seen many reports where that indeed was the case, particularly with Avast, Bitdefender and ESET and I've also seen some reports about similar issues with AVG, Avira and Kaspersky with the latest Malwarebytes release.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.