DavidR
4
They aren’t conflicting. When you set a custom scan to scan memory it will pick up signatures, that isn’t a conflict as you asked it to do that, under normal running it wouldn’t be scanning the memory in this way…
This in theory could also happen with the free MBAM if you ran an MBAM scan first and the signatures were still loaded, then ran an avast custom scan with memory scanning.