Jump to content

exile360

Experts
  • Content Count

    21,485
  • Joined

  • Last visited

Everything posted by exile360

  1. While this is true for most cases, it is not true for all. Early on I verified that some of these issues were indeed due to a conflict (or at least due to the presence of another security web filter driver like the Web Protection in Malwarebytes) because many users were able to resolve the issue by disabling the Avast web shield or the web protection in several other AV products (Avira, AVG, and ESET for certain, and there may be others) allowing them to keep all Malwarebytes modules enabled without any further issues/freezes. Again, this is not the case for all, and I realize that, but it is true that it is the case for at least some.
  2. Same here. So far all good with Ransomware Protection enabled again.
  3. Interesting, I guess Avast must have been having some kind of similar problem on their end around the same time as Malwarebytes. Thanks for the info. I guess it would be a good idea to check and see if users have Avast installed in the future once the fix for Malwarebytes rolls out officially to everyone if any similar issues crop up again.
  4. Someone else will have to do it for any OS older than 7 as Malwarebytes only officially supports Windows 7 and newer Windows versions now and won't be developing any new features for Vista or XP. They do still provide the last compatible version of Malwarebytes for those operating systems for download, but that's it.
  5. Good, at least it worked. I agree that this isn't an ideal solution or user experience. I'll bring it up again to the Product team and hopefully they'll make a change in an upcoming release to eliminate the need to remove/reinstall the software just to unregister it from the Security Center/Action Center.
  6. Well that's a bummer It was worth a try anyway. Hopefully the memory dumps and data that LiquidTension collected for the Developers will prove helpful. I'm sorry that we haven't been able to solve this problem so far.
  7. A new beta build was just released which includes fixes for issues related to protection, in particular Web Protection. That may be worth a try to see if it corrects the problem if you're willing to give it a shot. If so, it can be found here.
  8. Greetings, I did report this issue to the Product team however I do not know the status of a resolution for it in the product. In the meantime you should be able to perform a clean installation to remove Malwarebytes from the Windows Action Center: 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, or by downloading and installing the latest version from here Please let us know if that fails to resolve the issue and if there is anything else we might assist you with. Thanks
  9. exile360

    Windows 10 1809 and MBAM Premium

    OK, so just to make sure I understand, fast startup was enabled, you disabled it then restarted your PC and Malwarebytes still isn't showing the mbamtray.exe process in Task Manager, is that right? If that is the case, is the tray showing up I your taskbar/notification area near the system clock on system start? If so then it could just be a difference in how it functions/shows up in Windows 10 (I can't confirm as I'm on Windows 7 here) and as long as the tray is working then it should be fine. Thanks for the info on the email link. I will inform the forum team about the issue so that they may report it to our forum software provider that handles the forums and emails. Hopefully they'll be able to fix it at some point in a future update.
  10. Apparently some genius at Microsoft (likely at the prompting of someone from a third party hardware manufacturer who figured out this is how it should be a long time ago ) finally figured out that it might be a good idea to stop preventing basic, core, identical hardware drivers from installing on different devices just because some higher level software components and/or additional drivers/files may be specific to certain device types and OEMs (such as the driver software for notebooks which tend to focus on power saving features and avoiding thermal issues). For a long time, many hardware manufacturers (looking at you, AMD) would prevent their standard/generic drivers from installing on some platforms/devices, especially notebooks and tablets because they assumed that the OEM that built and sold the system would provide their own 'special' driver for the hardware. This is because, especially in laptops, tablets, all-in-ones and other non-desktop form factors, manufacturers will sometimes tweak the drivers they provide to customers to provide better battery life as well as down-clocking to prevent overheating. The trouble is, all too often OEMs don't often update their drivers, and when they do, it is often much less frequently than the original hardware component manufacturer meaning that, unless the end user is allowed to install the more up to date drivers from the component manufacturer (such as Intel, AMD or NVIDIA), they are likely to miss out on major feature updates and bugfixes, including BSOD fixes, performance enhancements, security/vulnerability patches and other important updates to the core driver components. It sounds reasonable in theory since it often is the case that an OEM will provide special drivers for the components shipped in their systems to customers to improve battery life and to optimize for the smaller, and often lower powered form factor for their non-desktop devices, however if you, like me, have ever actually taken a look at the base driver files being installed (not so much the "control" software or registry settings etc. that control things like power output, device sleep settings, low power modes, thermal throttling and device clock speeds/boost speeds etc.), they are completely identical so there is absolutely no reason that a person shouldn't be able to update these files using the drivers from the original component manufacturer's website using their much more up to date driver installation package. So now, with DCH, hardware creators will have the opportunity to provide base/core driver packages that just update the core driver components without altering any of the higher level settings that control things like low power modes, sleep modes, thermal throttling settings and clock speeds/boost speeds so that users can have the best of both worlds. All the benefits of the specially tuned/customized higher level settings/software provided by the system builder (the OEM) as well as the bugfixes, performance improvements and security/vulnerability patches provided by the individual component manufacturer who will often roll out driver updates much more frequently. I'm amazed that nobody thought to do this sooner, but at least it's here now, and hopefully hardware developers will adopt this standard quickly now that Microsoft has implemented it and is pushing for it. You can find out more about this feature on Microsoft's website here: https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/getting-started-with-universal-drivers You can read Intel's announcement (where I originally found out about this new feature/initiative) here: https://www.intel.com/content/www/us/en/support/articles/000031572/programs/intel-corporation.html To tell you the truth, I've always installed the drivers from the individual component manufacturers rather than my system's OEM because of this issue since the OEM's drivers would invariably be out of date almost immediately and you were lucky if you got two updates for a component's driver throughout the entire lifetime of the device when new drivers would be released multiple times a year if not monthly from the individual components' manufacturers and because, even though I do use a laptop, I do not run it off the battery (unless the power goes out; I like the laptop form factor for use around the house but don't actually take my system anywhere outside my home so it's always plugged in just like a desktop and I've optimized the cooling solution by replacing the thermal paste and modding the internals of the laptop to improve the airflow and eliminate any issues related to heat, thus allowing me to run a stable overclock on my hardware components full-time without any thermal throttling issues whatsoever). This is one of the longest standing issues to create frustration and confusion for computer users and is one of the primary reasons so many users try these "driver updater" programs (which are generally PUPs and not recommended) and also why these types of programs will so often fail to detect/download/install the correct device drivers for a user's particular hardware components/system, because there are so many different versions available from so many sources. DHC should eliminate the need for these types of applications, enabling users to go to a single known good source for each individual component to update their core driver components (especially since the higher level/performance/tuning related stuff isn't likely to change much if at all in most cases).
  11. exile360

    Feature Request: Dark Mode and other GUI stuff

    Do you know of a particular font that is preferred for dyslexic users?
  12. exile360

    Windows 10 1809 and MBAM Premium

    Yes, I believe it should also show the mbamtray.exe process unless I am mistaken, at least that's how it is in Windows 7. Since you're running Windows 10 it is likely that this is being caused by the fast startup feature which is enabled by default but is known to cause problems with Malwarebytes and other software. You can find out more, including how to see if it is enabled as well as how to disable it if you wish to here as well as here. Please let us know if that resolves the issue or not. Thanks
  13. Yes, I know. I wasn't saying that DEP was exclusive to Vista+, just that it was a built in function in the OS implemented by Microsoft just like ASLR.
  14. Good insight, I bet you're right. This also explains why, since 3.x was first released, that Vista and 7 (though especially 7, likely because so few stuck with Vista once 7 was released) have been plagued by performance issues, lockups and just overall bad behavior of MB3 under various conditions across several releases. It also explains why so many of those same issues did not seem to impact Windows 8/8.1 or Windows 10 in most cases. I've been watching these issues since 3.0 was first released and I've been keeping a close eye on them since I'm a Windows 7 user myself (with absolutely no intention of ever downgrading to Windows 10) and I kept wondering why it seemed that so often issues with Malwarebytes would be isolated to Windows 7. I'm sure it's not the only reason, but it would explain a lot considering how similar so many of the issues appear to be, with either the entire system or Malwarebytes itself locking up/freezing or just taking a long time to load or unload and delaying and/or freezing everything else in the process. I hope that the Developers keep this in mind going forward because I suspect this is not the only module to be impacted by this limitation in 7.
  15. exile360

    Forum Browsing

    You're welcome Yep, basically the way it works is it will remain bold as long as you have not viewed the most recent post/reply to a topic. Once you have read the most recent reply it will no longer be bold until there is a new reply from someone.
  16. Well, I just tested trying to delete one of Malwarebytes' data files from its data folder and the driver did prevent it, even when using admin privileges so at least that's working as it should. I wonder why they changed how it protects its processes? Maybe they encountered a compatibility issue with third party AVs etc. and were forced to change it to avoid those issues or something. I can't think of any other reason why they'd limit its protection like that.
  17. exile360

    Forum Browsing

    It should show in bold with a dot or star next to it if there is one or more replies in a topic since the last time you viewed it. A star means it is a topic that you have posted in and a dot means it is a topic you haven't posted in. See the example below which shows at least one example of each: The first topic is one I haven't read yet or haven't seen the most recent response to yet and that I have not personally responded to. The second is a topic I've read with no new replies so far and that I have no posted in. The next 3 are just like the first one; topics I haven't posted in with one or more posts I haven't seen/read yet. The last one is a topic I've personally posted in with no new replies/posts since the last time I read/viewed it.
  18. I have an Intel chipset and raid controller as well, and while I did see similar behavior with regards to switching windows/clicks and the cursor, I saw no errors or issues related to the disks or Intel IRST software. As for reporting/replicating the various activities that seem to trigger it, it may lead to a clue as to the cause if it is at all reproducible as was the case with the Battle.net game launcher (one of the first means the QA team found that allowed them to reliably replicate it thanks to reports from users). That's on the QA/testing side though, so you needn't worry about the Developers being sidetracked by what does or doesn't reliably trigger the issue to occur. They are looking at the code because that's their job, but any reports and data that indicates a possible consistency in how to reliably reproduce the issue can in fact lead to a fix because it can indicate more precisely where the issue lies with regards to the functions of the Malwarebytes drivers, processes and services even if the issue is also random/semi-random under other conditions/on other systems. I know all of this because I used to be QA for Malwarebytes and worked directly with the Devs on countless issues throughout the years, and while they would indeed comb through the code and analyze changes from one version to another just as you mentioned, they also relied on me to reproduce the issue reliably to help point them in the right direction with regards to precisely where in the code it was occurring and most importantly why it was occurring because knowing that a change they made is causing an issue is not enough since there is no doubt a good reason for the change such as adding new capabilities and/or improving performance etc., so they can't just roll back the code to the old version by sacrificing every change they've made to the software in the most recent release because of such an issue. They need to know precisely why the issue is happening and then correct or work around the issue while retaining the improvements and changes that they made to the code in the latest release so that the users get the benefit of the fix as well as the benefits of the new features/capabilities (such as augmentations to protection, which is likely what this change was that caused this considering the driver(s)/component(s) it's related to).
  19. They must have changed it then. It used to prevent any Malwarebytes process from being terminated this way and would show an access denied dialog/error, otherwise it would be trivial for the bad guys to terminate it then block it from restarting itself which was the entire point of self-protection in the first place.
  20. Hey, you never know. I assumed that because MS hadn't added that feature until Vista (and I believe it's also exclusive to x64, though I may be wrong on that point) that it didn't apply to XP, but if they did it in EMET then perhaps they did it in MBAE/MB3/MBAM as well. I'll make a note of it and ask the Product team and get you an answer for sure one way or the other.
  21. Thanks for the info. I'll be sure to report that to the team for additional troubleshooting/investigation.
  22. It is normal to be able to stop the service using Services.msc, but you shouldn't be able to kill it using Task Manager if self-protection is working.
  23. It shouldn't make too much difference and you can verify that it's working by trying to terminate any of Malwarebytes processes using Task Manager (you should get an error/access denied message box because of the self-protection driver blocking it).
  24. You may be correct. I will ask the Devs to find out if Malwarebytes is doing something similar on XP.
  25. Greetings, It's possible that the issue you're experiencing is similar to the one being discussed in this topic. If you would, please try each of the workarounds mentioned in this topic under the Known Workarounds section to see if that resolves it or not, particularly the second one involving reverting to an early build of the program. Please let us know how it goes. Thanks
×

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.