larsonreever

I have same issue with 239.255.255.250 and also different ports.

I agree with you 100%. Before making such a statement, I wanted to make sure I wasn't suffering from the "nocebo effect". After testing RC1 (before the official version was released), I thought there was slowdown in desktop start-up, but I wasn't 100% sure. I therefore uninstalled RC1 and could sense my desktop start-up was "much quicker". I then reinstalled 1.75 - I didn't really notice a slowdown in start-up - It must have had a minimal impact on start-up or at least it was unnoticeable. When MBAM 2.0.1 was released recently, I thought I'd give it another whirl - and this time I was 100% convinced that MBAM 2x causes a slow down in my desktop start-up. I'm running W7 x64. Although for me, MBAM is not the first program that appears on my taskbar in start-up. Its the last program and it takes the icon a while to appear (possibly up to 5 seconds after all other icons have appeared - I never timed it with a stop-watch, but it definitely takes a few seconds more to load and appears to hold-up the entire desktop from being ready to use). For example, I also noticed the "network connection" icon takes much longer to "establish a connection" - It appears to wait for the MBAM icon to load first before it can establish a connection. I even experimented with delaying MBAM 2.X at start-up by 15 seconds in advanced settings, but it appeared this did not make any difference. Without MBAM 2 installed, the network connection establishes a connection with the Internet fairly quickly.

Seems they innovated too quickly and focused on making sure it worked on Windows 10 but left Windows 7 in the dust.

Nice tutorial, this will be very handy

nice thread query answered in a very intelligent manner________

sorry i misunderstood, both are different ..my apologies..you are right

thanks for the info, but i think these two statements seems to be contradictory... edited: oh sorry i misunderstood, both are different ..my apologies..you are right

Is it possible to run scans with the free version or only with the full version,

Very much thanks, actually sound info...........

Sometimes during uninstall you get that notice if for example MBAE is still actively protecting some application such as a browser and it is open while you uninstall MBAE. The MBAE DLL would still be injected into the application during uninstallation. The best way to uninstall is to follow the instructions, which are: 1- Close all shielded applications (browsers, java, adobe, etc.) 2- Uninstall MBAE 3- Reboot As for Avast, that's typical of a HIPS/Behavior engine that asks the user questions for every little action. In this case Avast is asking if MBAE can install its driver. If you are installing MBAE clearly you want to choose "Allow" instead of "Deny".

I just checked and it seems that you can't disable notifications for the real-time protection layers in the settings