Isn’t there a downside to this, surely that means you have to have windows defender (or a background service/engine) running to get this benefit. When we are essentially saying disable windows defender if installing avast or 3rd party AV (even windows 10 is meant to disable WD if a 3rd party AV is installed).
You and bob3160 are 100% right.
Just wanted to give it here for completeness. I have Windows defender disabled as this should be for the Avast settings.
Steven Winderlich mentions something, but forgets to mention that.
No bob3160, DavidR and polonus etc. do not need this because they have Avast AV resident security. So for all of us keep windows defender disabled.
Yes, I’m aware of that, but this so called work around is using what appears to be a WD element ‘MpEngine’ so something of WD would be running when windows 10 and savvy users would have already disabled it. So for me this hack is Pointless.
Still a good hack to have and Defender doesn’t have to be running to add it, many users like myself run multiple systems with numerous AV’s, Defender being one of them
With some AV’s, that MPCmd thing still runs even when Defender is disabled. I don’t know if it does for all but I know for a fact that it did when I was using Bitdefender Free.
The file is MpCmdRun.exe and it appears that what is does is sense if another AV is installed or running. If no other AV is found, it turns Defender back on. That seems like an excellent feature that ensures that you have some kind of protection if your solution of choice somehow stops working. It appears to run every time something needs to be scanned. It’s only present in Win 8.1 and 10.
Sorry Bob, but no it doesn’t. Defender itself gets turned off but the file I mentioned still runs and turns Defender back on if no other AV is detected.