Windows 10: Scheduled scan time not working

Anyone can help with the problem? Or know this problem?- the Defender on our clients is managed via Microsoft Defender for Endpoint Baseline MDM- Baseline is working with all settings on the clients, no errors on client or with rolling out the BaselineProblem is the scheduled scan time set to 1PM is not working.All clients are doing daily quick scans, but the most client 3PM - 4PM, some 1PM-2PM...Seems complete random and definitely not working as planned in the policy.

:)

 

scheduled computer scan

It is not listed in the Task Scheduler library and never has been. It has always worked without being in that location on two (2) other pcs.

I schedule a scan to run daily, weekly, monthly whatever to run at a certain hour. Not my first rodeo

If I schedule a scan to run daily, it will run the first day and never again.

It won't run again because I scheduled the scan to run daily at 12pm. It ran yesterday the 18th but not today the 19th. Experience tells me since the problem started on 11/03/18 that it will not run tomorrow. That's three times to tech support and about
15 times of scheduling.

Last test result from 01/18/19 at 12[m was completed.

Like I said in my original question, I have used this application for six years on different machines. I know what I'm doing.

My question remains is there a setting on W7 SP1 that is hindering the execution of a scheduled scan

 

scheduled computer scan

The scan is independent of the Task Scheduler or it would be listed either in the library or as a process run.

The techs have looked at the log and nothing "sticks out"

Even at the level of a single end user, they want the scan to work more than I do

 

What is the meaning of "idle" with scheduled scans?

Whoops! In trying to edit the scheduled scans times in Task Scheduler, I accidentally deleted the Windows Defender Scheduled Scan from the list of tasks in the broad column shown above. Can I/do I need to reinstate it, please? (Case of a fool rushing
in etc. ....).

Otherwise, thanks again for the helpful advice.