I'm saying that the Automatic Maintenance Scan no longer runs on a daily basis, and consequently the Last scan information in the Windows Defender UI, or in the Windows Defender Security Center, is no longer being updated on a daily basis. That’s the new normal behavior (as far as I know), and it’s not the result of running manual scans. The scheduled scan itself has to actually complete successfully in order for the Last scaninformation to be updated, but the completion is failing most of the time, with a Last Run Result of 0x2 in Task Scheduler, and this entry in the MPCmdRun.log file:
MpCmdRun: Command Line: "C:\Program Files\Windows Defender\MpCmdRun.exe" Scan -ScheduleJob -ScanTrigger 55
Start Time: Sat Sep 30 2017 00:37:12
Starting RunCommandScan.
RunCommandScan is using default scan type: 1.
Scanning path as file: (null).
Start: MpScan(MP_FEATURE_SUPPORTED, dwOptions=16385, Timeout in days = 1)
MpScan() started
MpScan() was completed
ERROR: MpScan(dwOptions=16385) Completion Failed 80508018
MpCmdRun: End Time: Sat Sep 30 2017 00:37:13
So the Last scaninformation will normally fail to be updated for several days if you don’t run a manual scan. But if you’re actually saying that the Last scan information is failing to update even when you get a notification that Windows Defender has successfully scanned your device, or when you run a manual scan, then please make that clear, because that’s a different issue.
GreginMich