Reply to thread

Message

<blockquote data-quote="bazang" data-source="post: 1101845" data-attributes="member: 114717">The reason that most AVs do not add the non-registration setting into their product is because they don&#039;t want anyone doing exactly what you want to do. Furthermore, I am uncertain on this as I cannot find the infos, but IIRC some protection features will not work or not work correctly\fully unless the product is registered in Windows Security Center. Again, I am unsure of this dependency.Those AV might not exist well side-by-side with Windows Defender.It is not the act of registering a product within Windows Security Center that matters. What matters are all the things that the AV publisher must do to be able to register the product that is important (at least in Microsoft&#039;s eyes). There&#039;s a long list of hoops that the publishers have to jump through and, like most things Microsoft, that journey is an expensive and time consuming one.Microsoft requires AV publishers to be a member of the Microsoft Virus Initiative (MVI). One of the requirements is that the product be independently tested and certified every 12 months. It is for this reason that most AV publishers participate in the various AV Comparatives and AV Test certifications. Microsoft only allows AV publishers that are certified and accredited to become Microsoft Partners and thereby eligible to register their product on Windows.[URL unfurl=&quot;true&quot;]https://learn.microsoft.com/en-us/defender-xdr/virus-initiative-criteria[/URL]That is what Microsoft says, but if you contact all the major AV publishers their support will state &quot;&lt;AV_Publisher_Name&gt; does not support Windows Defender Periodic Scanning. It is not best practice to run two AV side-by-side even if periodic.&quot;Some products will keep disabling Microsoft Defender Periodic Scanning. This is by design and expected behavior.</blockquote>

[QUOTE="bazang, post: 1101845, member: 114717"] The reason that most AVs do not add the non-registration setting into their product is because they don't want anyone doing exactly what you want to do. Furthermore, I am uncertain on this as I cannot find the infos, but IIRC some protection features will not work or not work correctly\fully unless the product is registered in Windows Security Center. Again, I am unsure of this dependency. Those AV might not exist well side-by-side with Windows Defender. It is not the act of registering a product within Windows Security Center that matters. What matters are all the things that the AV publisher must do to be able to register the product that is important (at least in Microsoft's eyes). There's a long list of hoops that the publishers have to jump through and, like most things Microsoft, that journey is an expensive and time consuming one. Microsoft requires AV publishers to be a member of the Microsoft Virus Initiative (MVI). One of the requirements is that the product be independently tested and certified every 12 months. It is for this reason that most AV publishers participate in the various AV Comparatives and AV Test certifications. Microsoft only allows AV publishers that are certified and accredited to become Microsoft Partners and thereby eligible to register their product on Windows. [URL unfurl="true"]https://learn.microsoft.com/en-us/defender-xdr/virus-initiative-criteria[/URL] That is what Microsoft says, but if you contact all the major AV publishers their support will state "<AV_Publisher_Name> does not support Windows Defender Periodic Scanning. It is not best practice to run two AV side-by-side even if periodic." Some products will keep disabling Microsoft Defender Periodic Scanning. This is by design and expected behavior. [/QUOTE]

Verification