After a quick scan, Defender reports the correct scan time. After a while it nags me to perform another scan but reports the last scan was done in 2013 (see below). Why does Defender keep losing track of its scans and is there a fix for this odd behaviour?
Attachment 248667