Windows 10: Defender Scheduled Tasks Not Running Since Creators Update

Like the title says. The top task I manually ran and then stopped it. I do get a quick scan to run based on a separate task. Other computers not updated to Creators all run these tasks daily as this one did prior to the update.

They are listed as running in services.

:)

 

windows defender

As far as I know, we still have the issue with Ccleaner that causes repetitive prompts to scan with Defender:

http://www.winhelponline.com/blog/defender-needs-to-scan-your-computer-ccleaner/

But there’s also an issue with the built-in Automatic Maintenance scans, and these have only run sporadically since the release of the Anniversary Update – while the other Windows Defender scheduled tasks have continued to run with a “daily” baseline
frequency. This issue was purportedly escalated to the development team some time ago by forum management – but since there hasn’t been any response, I’m assuming now that this erratic behavior is the new norm, and that it’s actually
by design. At the same time that the Automatic Maintenance scans began to fail, so did any user-scheduled scans that had been set up to run under the
System user account (the “System alias”). So once I identified the source of the failure, I advised people to revert the user account for their own scheduled tasks to the
local administrator account – and then we pointed out that the Automatic Maintenance scheduled scan task would also run consistently again if its user account was switched over to the
local administrator account. Now I haven’t had time to look at this closely yet, but it now appears that this workaround no longer restores the baseline frequency for the Automatic Maintenance scheduled scan task in the Fall Creators Update.

So as far as I can see, there’s really only one way left to get a reliable Defender scheduled scan in the Fall Creators Update – and that’s to create your own scheduled task. I just revised my command-line scheduled-scan tasks, because these were also
broken by the Fall Creators Update. As always, these revisions come without warranty of any kind, either expressed or implied, because there’s really nothing that I can build that the developers can’t break:

Windows Defender - How to schedule a scan?

 

windows 10 recovery rollback fall to creator scheduled task operation shutdown windows defender

yeah that's not going to happen clean install i don't know about media tool repair thing

the thing is if i try to hide 1709<-i think there's a way to how will i know if i stay on 1703 if the next creator update comes along does same thing

and again if i stay on 1709 not run windows defender cache mainteance windows defender scheduled scan

the windows defender scheduled scan will start then i see warning saying the process has stop completion every few hours and then i see those 2 things task error

the thing is due the windows defender scheduled task process has been terminted it will not update last threat scan

i still don't know why verfication ran yesterday and i don't know if it will run automatically anymore or not

now if manually run them i will have to do them everyday and automatically mainteance will prob not run them anymore and that only leads windows defender cleanup will run

so again if i stay on 1709 surely the next build will fixed everything and windows defender scheduler scan will not show that warining event viewer and will start and scan not be terminated don't see that inside windows defender task scheduler and windows
defender cache mainteance

 

Hi bru,
Look at the MpCmdRun.log located in c:\windows\temp it might give us some more info.

Do you have a 3rd party anti virus installed ?
Have you checked Event Viewer for any errors ?

 

Only Malwarebytes Premium. Have that on the other computers too, and also on this one before Creators, but it is now the newest version of Malwarebytes. I'll get the other info shortly.

 

Not sure I see anything in Event Viewer. Lots of entries in MpCmdRun.log. This is the start:

MpCmdRun: Command Line: "C:\Program Files\Windows Defender\MpCmdRun.exe" -SignatureUpdate Start Time: ‎Fri ‎May ‎26 ‎2017 19:39:31Start: MpSignatureUpdate()Update started Search Started (MU/WU update) (Path: http://www.microsoft.com)...Time Info - ‎Fri ‎May ‎26 ‎2017 19:43:55 Search Completed Update failed with hr: 0x80240438Search Started (Direct HTTP) (Path: http://go.microsoft.com/fwlink/?Link...EC24)...Update failed with hr: 0x80072ee7Installation Completed Search Started (Direct HTTP) (Path: http://go.microsoft.com/fwlink/?Link...EC24)...Update failed with hr: 0x80072ee7Installation Completed Update completed with hr: 0x80240438ERROR: Signature Update failed with hr=80240438MpCmdRun: End Time: ‎Fri ‎May ‎26 ‎2017 19:44:07

 

Do you have Malwarebytes set to run a daily scan and if so at what time ?

Don't quote me on this ... I think those task are kicked off somewhere around 12-2 AM


Update: I just ran across this, looks like it applies to those errors.
https://support.microsoft.com/en-us/...ndows-defender

 

No, Malwarebytes runs a weekly scan. And as AFAICT Defender is updating definitions just fine. As I mentioned it (Defender) does run a daily scan based on a created task, which is a holdover from when Defender wouldn't run a daily scan as part of scheduled maintenance in the early days of Windows 10.

 

K, wonder if you can run the Default Scheduled Scan with it's parameters manually?

Open Command Prompt as Admin
"C:\Program Files\Windows Defender\MpCmdRun.exe" Scan -ScheduleJob -ScanTrigger 55

Note: The MpCmdRun.log when running it like that is in c:\users\USERNAME\appdata\local\temp

 

Just set up a custom scan to run at a certain time every 2 days. Time I set had already past and the scan did not kick off.

Doesn't seem to be working, and googling around yields not solution