GreginMich replied on February 10, 2014
In reply to Mission444's post on February 10, 2014
The “normal” problem with this is that everything is hidden away so well that people just don't realize that a scheduled scan is being run. This is the first case I’ve seen where it’s actually failing to run. Since my reply was a highfalutin explanation of why you won’t have this problem with the Windows (8) Defender Scheduled Scan, and it turns out that you actually do have this problem, my reply should definitely be unmarked as the “answer” – and I’m not sure that I really have an answer for this one.
The first thing you should do is run Automatic Maintenance manually (where it won’t be constrained to idle-time) and see if the scan completes successfully:
Action Center > Maintenance > Start Maintenance
And then run the System Maintenance Troubleshooter:
Action Center > Troubleshooting > System and Security > Run maintenance tasks > Advanced
And while you’re in the vicinity, run the Power Troubleshooter:
Action Center > Troubleshooting > System and Security > Improve power usage > Advanced
If that doesn’t help, then I would take a look at the Event Viewer and Task Scheduler logs for a clue to what’s going on:
Event Viewer > Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational
Task Scheduler > Task Scheduler Library > Microsoft > Windows > Windows Defender > Windows Defender Scheduled Scan (History)
Task Scheduler > Task Scheduler Library > Microsoft > Windows > Task Scheduler > Regular Maintenance (History)
GreginMich