If you have 2 timers set for the same time/date, and it is not working, then
the 2 are acting together like a double counter. When time gets closer, the
two would attempt to gain access to it, but only one will have permission to
it, the other will get locked out. I don't know how defender prioritizes
scheduling, maybe it does it a half an hour or so ahead of time to guarantee
it has access...so it doesn't lose that 1 second access the program gives for
the time you assign it. Maybe one program can get access to it, but since the
other can't get the access, it automatically pushes back the time so that it
can get a later chance. Since the time is adjusted for one of the timers, the
schedule is messed up for the original timer that got that access and can't
procede until its new schedule. But again, the timer that didn't get the
schedule could reset the time and add another half hour...its a part of
deadlock I suspect. You have 2 processes of scheduled times running from 2
applications, one is Windows XP type, the other process is Defender itself.
One might have access, most likely defender has priority over Windows, but
Windows doesn't have the access and is trying to get it. Look up "deadlock"
somewhere...usually refers to database, here your scheduled times are your
database. I agree with Bill, best thing to do is only have one schedule. You
don't need 2. Daily schedule is more than enough...if you need it any other
time, you can do a scan yourself. I set mine for times I'm not at the
computer, late night/early morning usually... so it isn't busy when I am
using it.
