Jump to content

ggeinec

Members
  • Content Count

    31
  • Joined

  • Last visited

About ggeinec

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. OK, so after monitoring for a few days it appears that Adobe Reader is triggering the random 'Adobe Reader is now protected' notification window when it is checking for updates.
  2. Thanks for your offer of help with MBAM on Windows 7. I decided to wait to install MBAM 3 on our three Win7 PCs until the early problems settled down. Meanwhile life events got in the way so I decided to put off upgrading to MBAM 3 until I replace our Win7 PCs with Win10 PCs later this year. I have three lifetime licenses to push through the process. Should be interesting. 😊
  3. exile360 - Thanks for responding. Yes, I know I am running a very old version of MBAM, but I have my reasons. I plan to upgrade to the current version soon on a new Win10 PC. Thanks for your concern. I already had checked Adobe Reader for updates. My copy is at version 2019.021.20048. When I 'Check for updates' it responds with 'No updates available.' When I go to the download page it offers version 2019.021.20047. So my copy is more recent than what is offered on the download page. Strange. Thanks for the tip on checking Task Manager when I get the Adobe Reader notifications from MBAE. I will start doing that.
  4. I'm running standalone MBAE 1.13.1.117 on Windows 7 Home Premium 64-bit on three different PCs. About a week ago on two of these PCs the MBAE notification window started to pop up randomly to announce that 'Adobe Reader is now protected' when I have not initiated any activity to open the Acrobat Reader. I don't know if this is happening on the third PC but I am waiting to find out. I have standalone Malwarebytes Anti-Malware 2.2.1.1043 Premium and ESET NOD32 (was v12, just updated to v13) running in real-time and with startup scans from both of those with no messages. Thoughts about why MBAE is throwing up those messages about Adobe Reader? Thanks!
  5. Ok. 🙄 I just found the MBAE beta forum so I will close out this thread and start one over in that forum. Sorry for the mix up.
  6. I should add that while I am running MBAE standalone I posted my message here because it appears to be the only forum that directly address MBAE. Please let me know if there is a more appropriate place for my messages. Thanks!
  7. I'm running standalone MBAE 1.13.1.117 on Windows 7 Home Premium 64-bit on three different PCs. About a week ago on two of these PCs the MBAE notification window started to pop up randomly to announce that 'Adobe Reader is now protected' when I have not initiated any activity to open the Acrobat Reader. I don't know if this is happening on the third PC but I am waiting to find out. I have standalone Malwarebytes Anti-Malware 2.2.1.1043 Premium and ESET NOD32 (was v12, just updated to v13) running in real-time and with startup scans from both of those with no messages. Thoughts about why MBAE is throwing up those messages about Adobe Reader?
  8. Arthi, I downloaded and installed this new version of MBAE on my sacrificial laptop. This version of MBAE appears to work fine with Firefox 59.0.1. I launched new Firefox windows, new tabs, new windows and new private windows from inside an already open window, multiple versions of Firefox open at the same time, etc., and Firefox opened and loaded content in every case the way I asked it to. Tomorrow I will install this new version of MBAE on my desktop to verify that it works there as well. Thanks for your and your team's persistence in researching and resolving this problem!
  9. My bad. Sorry about that. I should have said "Windows Updates through January" which I applied on all three PCs on February 9. We have no further Windows Updates on any of the PCs after that. I was planning to install the February updates this past weekend but got sidetracked by this Firefox problem. So no, no Windows Updates on March 7th/8th.
  10. For what it's worth, adding to this topic for Windows 7 and Firefox 58.0.2 for additional information. Feel free to move to a new thread if it doesn't belong here. On March 8 we received the unprompted 1.12.1.37 update to our standalone copies of MBAE on all three of our PCs. I didn't even realize MBAE had updated until well into the process of trying to debug what was going on with Firefox. All three PCs are running Windows 7 Home Premium 64-bit with Windows Updates current through the end of February. All three PCs immediately started having problems with Firefox 58.0.2. Since that update Firefox occasionally will successfully launch and open with the requested page. But the vast majority of the time it tries to launch, it paints the right half of the toolbar, it then shows the spinning circle in an empty page for as long as we let it spin. When that happens we close Firefox and re-try anywhere from one to dozens of times and get the same result again before we get a successful session. If we are lucky and Firefox successfully opens and loads the requested page we generally can keep the session going as long as we stay inside that open window. We can load new pages by using bookmarks or history links or links on the page that do not take us out of the window. If a link tries to take us out of the open window to a new tab or a new window we almost always get the empty window with spinning circle. Firefox behaves the same way with all add-ons disabled and when started in safe mode. Uninstalling MBAE puts Firefox back to normal behavior again on my sacrificial PC. I haven't uninstalled it yet on the other two PCs.
  11. Thanks for responding but I don't want to upgrade to the latest 3.4.4 version. I want to stick with 2.2.1.1043 for now and get back my real-time protection . . .
  12. I'm running three PCs with licensed lifetime standalone MBAM 2.2.1.1043 Premium and standalone MBAE which apparently updated itself to v1.12.1.37 on 3/8/18. Unfortunately this MBAE update broke Firefox 58.0.2 on all three of our PCs. Most of the time Firefox will start to launch but will stop before it has finished loading the toolbar and will just sit there. I see from the beta forum that this update has been problematic for other people as well. On one PC I uninstalled MBAE and have not reinstalled it yet. Now the MBAM icon also no longer shows up in the task bar. When I manually launch MBAM the splash screen shows 'no protection' in the Real-time Protection field. In settings both Malware Protection and Malicious Website Protection are enabled. Why is real-time protection not turning on? I tried re-entering my license ID and my Key but that made no difference. Should I deactivate and re-activate my license for MBAM to regain real-time protection? Thanks!
  13. I'm running MBAM v2.2.1.1043 (I don't see where else to post for this version) with database v2018.01.27.03 on Windows 7 Home Premium SP1. I'm also running ESET NOD32 v9.0.425.0. Since booting up and logging on today MBAM throws constant 'malicious website blocked' pop ups for legitimate outgoing traffic when I'm in 1) Firefox 57.0.4 or 58.0, 2) MS Internet Explorer 11, and Thunderbird email client. MBAM was not doing this yesterday. Blocked items include google.com and related domains like googleapis.com (used by the MBAM site). If I start typing anything into the search box in Firefox or IE I start getting those pop ups. If I type any URL to google into the address bar of either browser I get an immediate error from each browser that the page is not accessible or secure connection failed. This is not limited to google, it happens with many, many sites. On another PC that is set up as identically as it can be, but with MBAM database v2018.1.24.8, none of this behavior is happening. I'm not updating that one for the time being. Meanwhile, I see the MBAM database has been updated to v2018.1.27.6 as I have been writing this and MBAM is still popping up 'blocked' messages for legitimate sites . . .
×
×
  • 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.