About reporting any found issue for Security intelligence updates for other Microsoft antimalware...

[SwimmeRM]

Hello all,

can it be correct to also report here any found issue related to Security intelligence updates but whose effects can be quite so important that I know are already impacting on at least 1 product normal usage (Microsoft Security Essentials, yes I know it's a 'legacy' one) inside 'other Microsoft antimalware' (products) category ?

I'm asking this simply because from 'Microsoft Security Intelligence', choosing Downloads -> Updates -> 'Antimalware updates' the resulting web page that opens has the title 'Security intelligence updates for Microsoft Defender Antivirus and other Microsoft antimalware' and so it's also basically defining 2 main (product) categories (1) Defender, 2) other Microsoft antimalware) and maybe 2nd one is less specific for this techcommunity.

And I know there's already another direct feedback method available, using the emoticon '' [Provide feedback] icon found right below 'Search' menu item available in 1st upper line (that anyway, so far I've already used it several times, including this one too) , but it is also true that sometimes in this techcommunity I've also seen others reporting here issues or effects related to some signature updates (but mainly for Defender category only) and so far I've seen no other specific comments to be taken as a guideline about really needing to avoid to do the same because inappropriate.

Thanks in advance for your attention and next comments I'll receive. 0:-)

P.S. I know I've been quite generic so far, but I just want to avoid providing much more details if others should consider inappropriate (unless even too off topic for this techcommunity) to do so immediately for another non Defender 'legacy' antimalware product.

Best Regards

Rob

[#2 · Accepted solution]

After an additional double check I did, I found out that effective impact of what I found out yesterday was indeed much lower then expected and today I also verified that same minor issue is no more impacting on Microsoft Security Essentials that now can again be updated manually like before, so I guess/hope that yesterday, my initial updates via '' [Provide feedback] (that obvioulsy is a 1-way communication only) and even before my posting here might have probably helped too anyway... 

[#3]

JFYI (obviously for those very few worldwide really interested) since some days already MS Security Essentials is only allowed to forcefully update manually anyway, but now I've probably determined that main reason behind this could just be a recent disabling of any access to main servers involved in downloading signature updates via TLS1.2, so I've already tried to ask if re-enabling a partial only access might still be doable (with this I mean only to URL paths being accessed directly by MS Security Essentials self downloads).   

I'll keep you updated about my attempt results... 0:-)