Jump to content

dprout69

Honorary Members
  • Content Count

    95
  • Joined

  • Last visited

Community Reputation

2 Neutral

About dprout69

  • Rank
    Regular Member

Recent Profile Visitors

1,509 profile views
  1. I had a desktop and laptop with 8 GBs of RAM. The system trays were both very slow on the order of 13 seconds. One day my desktop went down for the count permanently so I bought a new desktop and laptop (they were due for replacement). The processor speed and other hardware didnt really change much, but these new ones have 16GBs of RAM and Malwarebytes opens right up now instantly. Not sure how much you have as I didnt open the zip, but maybe time for an upgrade? I know Malwarebytes is very intensive on RAM to which I've complained on that as well. Even if it seems like you have a lot av
  2. Just updated to 4.2.3 and all issues appear to be gone. Seems like a stable build other than some odd behavior when it was installing, but that seems to be par for the course. Penetration *giggity* testing has been moved to advanced exploit... is it not a good idea to turn that back on? Im pretty sure that was on by default in the last version I was using 4.2.1 and it was running fine. Anyone else using it?
  3. There are literally 4 other threads about this on the first page. Malwarebytes knows they're wrong (or have at least accepted that people are angry about it) and are intending to change how it's done, but they dont know when. Which mean it could be a very long time.
  4. @Porthos - Apples and Oranges. Major difference between between "we're installing something and you MIGHT need to restart" and "we are shutting down down your computer in 10 minutes and there is nothing you can do about it." One implies I will have control over the process and I'll be able to shut down MY computer in a controlled manner. The other one may occur if I get up and walk away from my computer and you do it anyway.
  5. If people arent smart enough to reboot their computers before calling for support then I put those people into the same category as someone who doesnt check to see if something is plugged in before assuming it's broken and calling "the guy". My computer is my computer. Do NOT force anything upon me and @digmorcrusher said it... warn me multiple times after the fact if you like... warn me before I install that you are going to require a restart and ask me if I wish to continue the installation, but under no circumstances should a piece of software ever assume that it knows more than me about
  6. Just to chime in on this... I had the same problem about a week ago on Windows 10 Pro 1909. Researched and never found any fix for it and ended up putting a system image back on from a month ago in order to fix it. I had the biggest suspicion that it was Malwarebytes that was causing the issue, but never had any proof. The reason I believe it was Malwarebytes is that I hadnt updated or installed anything in a couple of weeks and then noticed the issue shortly after I updated to the MB version right before 4.2.2. So, I dont think it was related to 4.2.2, but was introduced right before that
  7. @exile360 - It happens on two different computers so NETGEAR A6100 WiFi Adapter and Qualcomm Atheros AR5009 802.11a|g|n WiFi Adapter. @AdvancedSetup - No doubt it's a legitimate ongoing issue, however, to note the distinction: 1) Those 363 million are most likely for a permanent state. In other words, it doesnt just blink out and then come back 20 seconds later only to be normal. I've had that happen on my work computers over vpn, but it was an issue that had to be fixed on the vpn or network and it stayed as no internet connection the entire time. None of that applies here.
  8. Alright, so just updated to the latest 4.2.2 and happy to report that the neighborhood is visible again. However, unhappy to report that there is still an issue that was noticed in the last version as well, but I didnt think it to be a separate issue at the time (probably isnt which is why it's mentioned that the issue still persists for some). The network icon in the system tray appears to change to connected (changes from globe to wifi symbol) and then about 10 seconds later goes back to a globe (and this can last up to 20 seconds all the while says it's connected to my router, but no inte
  9. It runs fine. However, if you've never used it before it gets quite tedious. Seems like it's still somewhat of a work in progress which is probably why MSFT doesnt turn it on by default.
  10. https://downloads.malwarebytes.com/file/mb4_offline 4.2.1.190
  11. Oh and I don't know if it would, but there was no message like defender has been deactivated... The icon would just disappear and malwarebytes would appear. Turn off malwarebytes and defender would appear.
  12. As mentioned above, I've already done a system image and reverted back to the prior version so there are no logs anymore. Unable to help there, but Porthos confirmed the web protection aspect already. As far as the defender icon, I only turned it off/on to deal with the aforementioned issue with network neighborhood. It was booting up and running both fine until I manually turned it off and on. Thats about all I can give you other than Im using Windows Pro 64 1909.
  13. Right click in the tray > Quit Malwarebytes Wait > Double Click your desktop icon to open it back up Is Defender still there?
  14. Windows Defender Icon - There were no problems prior to updating yesterday and no it was not set to register in the security center. Network Neighborhood - I've already done a system image. Seems that release is a bit buggy. I just dont have the time to be a beta tester so Ill wait to see if they fix anything in later releases and just stay on the prior version for a while.
  15. Aaaaaaaand just noticed another issue... when I open Malwarebytes back up as described above, it makes the windows Defender icon disappear from the system tray. Happens on both computers. You know I've been with Malwarebytes a long time, but sincerely I have to say you have the worst beta testing in the world that no one sees this stuff. This is happening on different two computers. Looks like Im going to have to put a system image and roll this update back. Thanks
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.