Hi Stu;
I believe both the GUI and Task Scheduler. What I've seen is that at the
MPScheduled scan time the scan starts running but only lasts a few seconds
before it shuts down without any error being reported in the scan log, but
then the GUI doesn't get updated as having run a scan, so after three days
of this I start getting the haven't run a scan in over 3 days message. The
only difference is that the MP Scheduled scan task is Run as NT
Authority\System through the WD interface where as my self scheduled daily
scan is Run as my own Admin Account, but the confusing part is that both
System and my Admin account have the same permission levels. A scan run
either manually or as a scheduled task from my Admin account runs
successfully with a quick scan lasting 4 minutes or so and the GUI last
scan date is correctly updated in this case. Why it won't run as System, I
have no idea, and there are no error clues to follow, just that the scan
duration is very short. I'd imagine that ChazBo is seeing this as well, so
scheduling a scan to run from the Admin authority id rather than System
bypasses the problem. This unexplainably started happening to me around
March for my daily quick scan although the MP Scheduled Scan was working OK
before then. I had a monthly scan scheduled to run separately at that time
which was still running so I just disabled the MP Scheduled daily scan in
Options and added another scheduled task to run from my account at that
point to do the daily scan, this worked without problems and continues to
run well.
Yes, I plead guilty to advocating Event Log Explorer, the Ms method of
looking at that log is just too primitive. In regard to your Event ID
3003. Error code 0x80070005, it's certainly a permissions problem but
where? Since I think your not getting this reported on any specific
checkpoint, like a registry location that Defender monitors which would
make me look elsewhere, I think first I'd look at the permissions on the
Defender folder itself and all subfiles. Assuming my system is setup
correctly (LOL) since I'm not getting 3003 errors, here's what I see:
Security Settings:
Administrators and System both: Allow Full Control, Modify, Read & Execute,
List Folder Contents, Read, Write
Advanced Settings:
Administrators and System both: Allow Full Control, (not inherited), Apply
to this folder, subfolders, and files