Sign up for a new account in our community. It's easy! Already have an account? Sign in here. 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. Share More sharing options Followers 3. Recommended Posts. Posted February 21, Just for the sake of experiment , removed both and installed ESET as having the minimum impact on a pc, according to AV Comparatives You will not believe what a difference!!!!!
Link to post Share on other sites More sharing options Ried Posted February 21, Details required :. Cancel Submit. Le Boule MVP. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. A subscription to make the most of your time. Try one month free. The simplest solution is to tell the programs to ignore each other. Remember, this is only necessary in Windows XP, not Vista or 7.
After this, the two should behave just the way they are supposed to. We'll be posting our updates here. We can just now confirm a workaround is disabling Microsoft Security Essentials' real-time scanning in normal or safe mode. We're still troubleshooting and will provide updates here as we learn more.
I got the slowdown this morning, when I updated MSE definitions new series: 1. Normally, it takes 18 minutes or so, but it was running over MSE is running more or less at its normal speed, but I'm also seeing slowdowns in browsing.
A custom scan with rootkit check normally takes 2 hours, but this afternoon, I aborted the scan at almost 4 hours. I have it running, and it's bog slow; maybe halfway through the files at 2. Forgot to mention: Windows 7 Home premium. It only seems to be Windows 7 64 bit? It happens after MSE updates to the latest definition. It slows down and eventually locks up the PC. The PC eventually becomes unusable and unresponsive. You can see many event log messages with "fault bucket" and talking about the MSE process.
Booting into safe mode or before the PC crashes and disabling MSE real time scanning works around the issue. As does removing MBAM. It is definitely a conflict between the two. We did this - I have had reports that this doesn't work - users are still experiencing issues until Malware Bytes Anti-Exploit is disabled.
Just wanted to share our experience. We have no new updates at this time. Our suggested workaround is still disabling real-time scanning in MSE. So far, it looks reasonably fast on a custom scan. On the main machine, I have the standard non-business license. Disabling realtime scanning is not really an acceptable option and increases our risk. The whole purpose of having two solutions is for the added protection. This way you don't have to disable realtime scanning.
The implementation of the following Malwarebytes recommendations for AV software process scanning exclusions contained within the following post seems to have addressed our issues.
Can anyone else confirm the same?
0コメント