Jump to content

exile360

Experts
  • Content Count

    29,580
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by exile360

  1. I'm running 7x64 SP1 here, fully patched, with Malwarebytes Premium (also fully up to date) alongside MSE in real-time (and have been for years now) and haven't had any freeze issues or crashes so far. I've been running build 508 of Malwarebytes since the day it was released.
  2. You're welcome If there's anything else we might assist you with please let us know. Thanks
  3. Greetings, It sounds like maybe the Windows Action Center is monitoring Malwarebytes and that perhaps during startup while Malwarebytes is starting its protection, but before it is fully active, Action Center sees that its protection isn't active yet and displays a notification to alert you about Malwarebytes' protection not being active but that's just my guess based on your description. You can try to resolve it by stopping Action Center from monitoring Malwarebytes (since Malwarebytes monitors itself as well and should alert you via its own tray icon if anything is wrong/not worki
  4. You should deactivate it on the old PC first if you can. If not, then theoretically as long as the old system never comes online again it should be OK, but there's no guarantee (though worst case scenario you'd just need to contact Support to get them to reset the license/deactivate all devices on their end more than likely).
  5. Yeah, it's a real bummer (and can definitely be a pain for regular members). It was actually an issue that forum admins debated on for a very long time (months if not years) until finally giving up and setting up more restrictive policies/settings because the spam had gotten so bad. At one point we were seeing daily spam floods of countless posts from spam bots with tons of new spam accounts being created almost constantly. When they finally set up all these new filters, rules and policies it cut the spam down to nearly 0 and made the forums a lot easier to manage and keep clean of spam.
  6. Spammers will create what appear to be innocent/legitimate posts and then later return to edit their previous posts to inject spam links/content into them. It's a behavior we've seen many times and is the reason the forum administrators created this policy.
  7. They do (I'm a former Malwarebytes employee so I have first-hand knowledge of this and even used to be a member of their QA team that handles the testing). Unfortunately these issues cannot be replicated reliably on every system running the affected operating systems; I should know as I'm running Windows 7 Pro x64 SP1, fully patched and haven't had any of the issues being reported with this build by users running that same OS. Unfortunately I don't know what all the variables are to reliably reproduce these issues, and I also know from past first-hand experience (and the reasons I personally
  8. Thanks for the feedback. I do know for a fact that in the past there have been many instances where they provided pinned topics and public announcements with known issues and occurrences where the software broke in one way or another. In this case I suspect that the number of issues/regressions present in this particular build has had them much more focused on chasing down the cause and data to more quickly provide a resolution/fixed build than on providing any sort of FAQ or public announcement (though I do believe they did pull the build from the automatic update/upgrade channel/servers to
  9. Thanks for the info regarding the Support Tool on XP. I'll be sure to report that to the team and hopefully they'll fix that in a future version so that it downloads/installs the appropriate build for legacy operating systems. @dcollins, @nikhils could one of you please take a look when you get a chance? I suspect your direct access to the Devs will prove valuable in determining what's going on here in this particular case (both of those members are Malwarebytes Support staff personnel). I guess we'll have to wait until they return from their time off for the holidays, but in the m
  10. Ah, I see. That makes sense. Yes, since it worked for a while chances are it's just some kind of intermittent issue with the software or it could be some kind of conflict with one of the other drivers on the system. I have one more thing to suggest to troubleshoot: Please open Malwarebytes and go to Settings>Application and toggle the option on under Event Log Data then restart the computer and once it restarts and Malwarebytes is up and running again, check to verify that Exploit Protection still isn't functioning. Once that's done you may turn off the option under Event Log D
  11. No problem at all, and I understand why you're anxious for a fix; we all are for sure. I've been reporting these issues to the Product team constantly since build 508 was first released to document all of this for them in the hopes that the Devs will benefit from all the details and get to a fixed build that much sooner, but I know that they have a lot on their plates in fixing this particular release because of all these regressions and I'm sure they are also working to track down and correct whatever it was that caused these regressions to occur in the first place to hopefully prevent anyth
  12. Everything David said above is accurate, and I'll add that the only thing a VPN will do for your security is help to prevent anyone from snooping on your traffic between your system and the sites you connect with, but any information stored on those sites, as David already stated, is only as secure as the site providers make it via their own security measures. So while a VPN may help to ensure that your ISP can't snoop on your surfing habits, help to secure your communications when using public Wi-Fi and help to ensure that you aren't a victim of any man-in-the-middle attacks, it will do abso
  13. I just noticed something else odd in your logs. They list the Windows directory as: D:\WIN-NT In XP, it should be C:\Windows, or in your case, since Windows is installed on D:\ it should be D:\Windows. Win-NT is not a valid system folder name for the Windows directory on XP so I have no idea what's going on. I also noticed other oddities in the logs regarding drive letters and folder structures and it shows D:\ as being a FAT32 formatted partition rather than NTFS. I don't know if the filesystem structure has anything to do with it but it is odd for XP to be set up that way.
  14. There are a lot of bugs in this latest release, that's why it's taking so long to get a fix. They aren't going to fix just one issue and release a patch just to release 2 or 3 more fixes for the other outstanding issues afterwards. I suspect there was a problem with the most recent update/build that reverted several issues that had been fixed in earlier releases to a pre-fixed state and they're probably working to track down and undo whatever it was that broke the build process to keep all desirable changes and revert all of the bug regressions in the build because we've seen all of these is
  15. You don't need to login on the support page. Just create a ticket and you will correspond with Support via email.
  16. No, those files are for the standalone version of MBAE, not the version integrated into Malwarebytes 3 so those other EXE files shouldn't be there. As for why the Spanish language version of the driver is being installed, I have no idea, but it may be related to why Exploit Protection isn't working.
  17. You're very welcome And if you have any more questions please don't hesitate to ask.
  18. Correct, there shouldn't be anything to worry about. As for the Support Tool, it most likely had the reinstall scheduled but failed on reboot (again, it happens, but no big deal). Basically the Support Tool tried to uninstall MB from your system, have you reboot, then was supposed to launch the installer to reinstall the latest version of MB back onto your system. Sometimes it fails, especially when a third party AV is installed (like AVG, which may have blocked it for some reason or just messed up the timing of it on boot) and you end up having to reinstall it manually. So as long as
  19. Ah, I see. Most likely it was just a temporary hiccup, probably caused by a corrupt database, configuration file or just a problem with the protection driver failing to load. These issues happen from time to time but should be rare. The self-protection in Malwarebytes is very good, so an infection turning off your protection would be very unlikely.
  20. Greetings, Your best bet would be to contact Malwarebytes Support directly so that they can assist you with this issue as they should have direct access to the account/licensing system and can hopefully make the changes necessary to align your license/subscription with the correct account/email address. To contact them, please use one of the options available on this page If there is anything else we might assist you with please let us know. Thanks
  21. Greetings, It looks like the installation is still waiting for another reboot so please restart your system one more time to see if that clears things up. If Malwarebytes still isn't working properly after that then please perform a clean installation by doing the following to see if it corrects the issues: Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Clean button, and allow it to restart your system and then reinstall Malwarebytes, either by allowing the tool to do so when it offers to on restart,
  22. OK, thanks. It looks like the Base Filtering Engine (BFE) service isn't running on your system for some reason. That may be the issue as that service is one of the required dependencies for Malwarebytes to function. You should also try removing the following exclusion from Malwarebytes temporarily to see if that allows Exploit Protection to function as I recall there being an issue with exclusions on other drives causing problems with Exploit Protection a while back: E:\Installation Files
  23. Greetings, Please try performing a clean installation by following these instructions to see if it helps: Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Clean button, and allow it to restart your system and then reinstall Malwarebytes by downloading the latest Windows XP compatible version from here Please let us know how it goes and if the issue is resolved or not. Thanks
  24. Greetings, Yes, this appears to be an issue with the latest version of Malwarebytes and Bitdefender that has been reported a few times previously. For the time being, you can try adding exclusions for Malwarebytes in Bitdefender and for Bitdefender in Malwarebytes to see if that helps at all. The files and locations to exclude for Malwarebytes can be found in this support article and you should exclude Bitdefender's folders under Program Files/Program Files (x86) and C:\ProgramData in Malwarebytes by following the instructions in the Exclude a File or Folder section of this support arti
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.