2 ms·

>3rd party applications should NOT be responsible for insuring that the OS can receive critical security updates It is because these (misbehaved) 3rd party app

>3rd party applications should NOT be responsible for insuring that the OS can receive critical security updates It is because these (misbehaved) 3rd party applications do things that cause the mitigations update to make computers unusable. >and of all things, hilariously defaulting to 'no' It does not default to "no" since the default is to run MSE / Defender.

JadeNB 9y ago
> > and of all things, hilariously defaulting to 'no' > It does not default to "no" since the default is to run MSE / Defender. I think that it's reasonable to read the grandparent's post as meaning "defaulting to 'no' under certain conditions on the system". It would surprise me if there weren't plenty of users out there who have legacy workflows with antiquated antivirus software still running, either because they set it up and haven't changed it or because their local tech geeks set it up and they don't know how to change it. I know that, as I've tried gradually (and unsuccessfully) to ease back into Windows after a long time away, it's been hard for me to believe in Defender as a full AV solution, and my first instinct was to run old favourites like ClamAV as an extra layer of defence.