joshuals

I will follow your advice. Thank you.

I'm running a recent re-install of V2.2.1.1043. In a previous thread I described how, in early April, I allowed an update to Version 3 which resulted in several problems, including the well-documented issues of conflict with Microsoft Office 2016 and Real-Time Protection not starting. I reverted back to V2.2.1.1043 and the problems went away......until I began to get the pester screen to update again. After clicking "later" I noticed that not only was Real-Time Protection not running, but the radio buttons in Settings -> Detection and Protection (for Malware Protection and Malicious Website Protection) were set to "disabled". Not sure how that happened, but everything had been running normally for about two weeks after the V2.2.1.1043 re-install until I was prompted to update. In any case, the solution you provided in this tread fixed the problem and all is well. I will certainly be interested in allowing the update when the issues I experienced with V3 have been resolved.

Yes....I understand. But after clicking "later" I found that the Real-Time Protection on this existing install would not turn on. Does that make any sense?

Please correct me if I am wrong, but it appears (from my experience today) that clicking "Later" to the "update nag popup" prevents the currently installed version of MBAM from enabling Real-Time Protection. Not sure whether this is an unintended consequence of clicking the "Later" button or not ......... ? I am presently running version 2.2.1.1043. Once I followed the instructions in Post #2 of this tread, the nag popup ceased and Real-Time Protection was enabled on the next reboot.

@dcollins @AdvancedSetup Well, go figure. I cold-booted the laptop this morning and after letting it idle for three hours, and without launching any other applications, MBAM and MBAE are working normally (Real Time Protection is "on"). I then ran a fresh FRST log and the System Errors related to MBAM that showed in the previous FRST log did not occur this morning (except for those two errors related to Garmin, which has for some time been disabled from running at Startup via Task Manager.) So let's do this: I'll keep an eye on MBAM and see if the Real Time Protection stops running again and try to determine what triggers it. If (when) that happens, then I will do as you suggest and start a new post in the other forum that you suggested. Please let me know if this plan of attack makes sense. I have some experience and training with FRST and nothing jumps out at me that would indicate the computer is infected. Please tell me if you see otherwise. Also, please tell me if the errors and missing files cited in the MB-Check log indicate that there is a problem with my MBAM/MBAE installation. Thank you for all your help.

@AdvancedSetup Thank you for your response. Since the logs that were requested by Post 22 were for @dcollins to examine, I will wait for his response so that we don't get two topics going at once on the same issue. Then, if he agrees, I will do as you suggest.

@jadinolf: Presuming "Mwb" is your nickname for Malwarebytes, the answer is "no"...... @AdvancedSetup: With all due respect, I was in hopes to get some help fixiig this issue on this forum......am I in the wrong place?

Here are the requested logs. Logs.zip MB-CheckResult_4-05-17_2.txt Addition.txt FRST.txt

Hmmm....in attempting to carry out the instructions in Post 20 I opened the MBAM Console and was greeted with the screen shown in the attached screen shot in MBAM_1.png. Clicking "Fix Now" does nothing. I then attempted to start "Malware Protection" and "Malicious Website Protection" from the console. Upon opening this console, both radio buttons were "Disabled". I changed the buttons to "Enabled" as shown in the second screen shot, but the condition shown in the first screen shot persists. The MBAE icon still shows in the Notification Area. What logs would you like me to submit?

Thank you for the excellent support!

I have completed the uninstall of MBAM V2 and MBAE and have reinstalled both using the installers you recommended. The fresh install of MBAM was authorized without my having to enter the license information. The fresh install of MBAE also completed successfully and I did have to enter the license info to authorize it. I have successfully run a scan with the fresh install of MBAM V2 and the MBAE icon shows in the Notification Area. All appears normal. Please find the fresh log from the mb-check tool. Do you need FRST logs as well? MB-CheckResult_4-05-17.txt

Will do.... Please comment on the question in Post 13 regarding re-authorizing the product without having de-activated it first. Thank you for your help.

For uninstalling would you recommend "mb-clean-2.4.1.1007" or should I use an application such as Revo? Is there going to be a problem re-authorizing if I uninstall without having deactivated the license? (Remember, I cannot open the MBAM console) Can you verify that these two installers are "good"? mbam-setup-2.2.1.1043.exe 5A141EA85724385EE7E68C10247E154BBD72CE1A656EBEDE99BB0FCA5BB5974A mbae_premium.exe C5277C6EFAACEB0738573DB4B29FBC2F36D47619EEE46631C710AD68B291B211

Yes. I am going on the road soon and, for now, am only interested in getting back to where I was before I allowed the V3 upgrade. Neither MBAM or MBAE are running at Startup. I can launch MBAE manually, but MBAM will not launch. If I attempt to start MBAM manually, there is some brief activity in the Windows GUI but the MBAM console does not come up. On the day (3-27-17) that I reinstalled MBAM and MBAE I was able to start them both and successfully enter the license information. I only noticed that they were not running yesterday when I attempted to right click on a file and have MBAM scan it. When I did that, nothing happened and it was then that I noticed that neither product was running. I believe that the logs I submitted in Post 7 indicate that there was an error starting MBAM, do they not?

Thank you.....I will probably sign off for the night shortly but will check back tomorrow. I just confirmed with Virus Total that the installer I used to re-install MBAM V2 and MBAE have the correct SHA-256, so I don't think there was a problem with those files.