Defender won't run scans automatically

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I installed Win Defenderlast week, and double-checked that it is set to run a
scan every day at 6AM. % days, now, and nothing. I had the same problem
with its predecessor, Anti-spy. What am I doing wrong?

I'm running XP Home, and installed the 32 bit version.

Thanks,
 
Hello Geebee,

Is the Task Scheduler disabled under services? Microsoft Antispyware
schedules as a hidden task using the Windows Scheduled tasks facility--so
Task Scheduler needs to be availªble. Scheduled scans are done via the
Windows Scheduled tasks facility. Go to Control Panel, Performance and
Maintenance, Scheduled tasks. In the menu at the top, choose Advanced, View
hidden tasks and Notify me of missed tasks. You should see an entry for MP
Scheduled Scan. If you right click this entry, and choose to run it--what
happens?

For the benefit of the community reading this post, please rate the pºst.

I hope this post is helpful.

Let us know how it works ºut.

Еиçеl
 
I've been having the same problem as Geebee. I followed Engel's instructions
below. On windows 2000, I didn't have an option to view hidden tasks. I did
view the log and saw that "MP" was running daily. Unfortunately it was
starting and stopping again after as little as 20 seconds, and wasn't able to
complete the scan. Any idea what the problem could be. It works fine when I
run a scan manually. (unlike Geebee, I did not have this problem with
Anti-spyware.)
Thanks,
jwaltz
 
The scheduled scan execution mechanisms changed completely, I believe,
between beta1 and beta2.

Beta2 uses the Windows scheduled tasks mechanism. There is a command line
portion of Windows Defender--mpcmdrun. You can see the arguments this
executable takes by just running it at a command prompt, and you can, in
fact, effectively create your own custom scheduled jobs--quickscan daily,
fullscan at longer intervals, if you like, for example.

We've seen a number of posts like this and the problem seems to relate to
Windows 2000 systems. Things to check are what credentials the scheduled
task is set to use--are they valid? and, perhaps, trying your own job and
seeing whether you can make that work--perhaps using administrator
credentials. I seem to recall that one thread involved an argument syntax
in the automatically created job which apparently was incorrect. Removing
one of the arguments fixed the problem.

I'm being pretty vague here, and if you aren't familiar with command line
work or the scheduler, this probably won't help you much (and maybe not even
then!)--but that's what I'm remembering at the moment--been on vacation, and
it's hot, and late too!

--
 
Back
Top