Windows Defender Update 1.14.1511.3

  • Thread starter Thread starter Guest
  • Start date Start date
I suspect that the latest release broke something in its ability to remember
when the last scan was run. My Defender had been running flawlessly on
several test platforms but now claims that a scan has not been run in 2 ... 3
.... 4 days on two of these systems. No other functionality seems impaired,
however, and it is probably configuration-specific.

For the record, my test platforms each have mixtures of 8 or 9 gigs of
applications installed, including SQL, three broswers, and many non-MS apps.
(I have them all hardened to a CIS Benchmark score of 8.25 or higher, just to
keep things "interesting".) Then again, it might be interacting with Prevx1
or SocketShield which is being concurrently tested (and which have not yet
exhibited any peculiar interactions).
 
Back
Top