And I suspect that is what happened because if it was a problem with Windows Defender, I would think there would be millions and millions of users complaining about it! And there isn't. What I suspect happened in your case is there was a recent update to ESET and that Windows Action Center setting in ESET was reset to the default. But you have to manually tell Malwarebytes (not Windows Defender!) to leave WD running as the default action is for WD's real-time component to gracefully step aside.įor Malwarebytes Premium users curious how to do this, open the Malwarebytes control panel, click on Settings > Application tab then scroll down to "Windows Action Center" and tick the " Never register Malwarebytes in the Windows Action Center" button. And both are easy on resources so they can be run in real-time at the same time with no conflicts or bogging down the system. However, unlike some 3rd party scanners, Malwarebytes and Windows Defender play very well together. This also frees up some system resources, which may be important on systems with small amounts of system RAM. This is to avoid any potential conflicts (two dogs guarding the same bone) caused by running two real-time scanners at once. This action tells Windows Defender a 3rd party scanner has been installed so WD's real-time component will disable itself. This is how every 3rd party "real-time" anti-malware solution (including ESET) is suppose to work.
When you install the "Premium" (real-time) version of Malwarebytes, it will register itself with "Windows Action Center". I don't use ESET so I cannot comment on it specifically, but I can comment on Malwarebytes and the steps should be very similar. That is NOT a criticism of ESET, just a comment based on previous observations with several 3rd party anti-malware solutions.
Click to expand.Is it still going on? Not sure MS can do anything about it if it is working fine now and it is not something you can duplicate at will.įrankly, I would suspect ESET before WD.
0 kommentar(er)
