Reply to thread

Message

<blockquote data-quote="SeriousHoax" data-source="post: 992570" data-attributes="member: 78686">There is no best AV. It depends on what you prefer for yourself. For me personally, Microsoft Defender and ESET gives me the least amount of problems. Wondering what sort of bug you experienced with ESET!On Windows 22H2, which is currently on Release Preview and Beta build, even if you install a third party AV, the Microsoft Defender service keeps running. I tested with Bitdefender and ESET and same result on both. Though it doesn&#039;t seem to use CPU. Consumes very little ram, but it&#039;s always running. Tools like Defender Control can&#039;t stop it. It comes back. Also, it updates its signature a couple of minutes after system boot up because almost all third party AVs takes a few minutes to register into Windows Security after system boot up, and it seems for that couple of minutes Microsoft Defender acts as the main AV. Looks like this new behavior of Microsoft Defender&#039;s service is going to be the norm, but I could be wrong. I couldn&#039;t even turn it off by using Group Policy. The Microsoft Defender service seems to run in a suspended mode. But signature update after booting is what bothers me if I&#039;m using a third party AV. Anyway, try a couple of AVs by yourself and then decide or stick to Microsoft Defender.</blockquote>

[QUOTE="SeriousHoax, post: 992570, member: 78686"] There is no best AV. It depends on what you prefer for yourself. For me personally, Microsoft Defender and ESET gives me the least amount of problems. Wondering what sort of bug you experienced with ESET! On Windows 22H2, which is currently on Release Preview and Beta build, even if you install a third party AV, the Microsoft Defender service keeps running. I tested with Bitdefender and ESET and same result on both. Though it doesn't seem to use CPU. Consumes very little ram, but it's always running. Tools like Defender Control can't stop it. It comes back. Also, it updates its signature a couple of minutes after system boot up because almost all third party AVs takes a few minutes to register into Windows Security after system boot up, and it seems for that couple of minutes Microsoft Defender acts as the main AV. Looks like this new behavior of Microsoft Defender's service is going to be the norm, but I could be wrong. I couldn't even turn it off by using Group Policy. The Microsoft Defender service seems to run in a suspended mode. But signature update after booting is what bothers me if I'm using a third party AV. Anyway, try a couple of AVs by yourself and then decide or stick to Microsoft Defender. [/QUOTE]

Verification