Problem with Scheduled Scans

I have Defender set to scan daily at 4:00AM. The problem behavior is that if
Defender cannot run the daily scan at 4:00AM (e.g., because the computer is
not on), Defender will run the scan at some point later when the computer is
on (e.g., 1:00PM). My computer is essentially unusable during a full scan.
I've actually had to do a hard power-down to get the machine back. And, there
is no indication that the problem is Defender running a scan unless you open
the UI.

Suggestion: Either skip scheduled scans that could not be executed because
the computer was off or provide an option for doing so.

If you can get the UI up, there is a cancel button, and this has worked in
my experience, although I can easily imagine that it might not in the
circumstance you describe. I've seen a post stating that a missed scan is
initiated 10 minutes after a subsequent login or switch on--not sure which.

--

"brown3141" <brown3141@discussions.microsoft.com> wrote in message
news:382EA7B7-D305-4D99-8249-03DD13A12617@microsoft.com...
>I have Defender set to scan daily at 4:00AM. The problem behavior is that
>if
> Defender cannot run the daily scan at 4:00AM (e.g., because the computer
> is
> not on), Defender will run the scan at some point later when the computer
> is
> on (e.g., 1:00PM). My computer is essentially unusable during a full scan.
> I've actually had to do a hard power-down to get the machine back. And,
> there
> is no indication that the problem is Defender running a scan unless you
> open
> the UI.
>
> Suggestion: Either skip scheduled scans that could not be executed because
> the computer was off or provide an option for doing so.

What you describe is consistent with what I've observed. I really think this
is poor design. The most likely effect of having missed scheduled scans start
10 minutes after a login is that people will turn scheduled scans off. If I
wanted the scan to run, I would have left the machine on.

I will try setting it to a quick scan instead of a full scan and see whether
the situation improves.

Thanks.

---Jim

"Bill Sanderson" wrote:

> If you can get the UI up, there is a cancel button, and this has worked in
> my experience, although I can easily imagine that it might not in the
> circumstance you describe. I've seen a post stating that a missed scan is
> initiated 10 minutes after a subsequent login or switch on--not sure which.
>
> --
>
> "brown3141" <brown3141@discussions.microsoft.com> wrote in message
> news:382EA7B7-D305-4D99-8249-03DD13A12617@microsoft.com...
> >I have Defender set to scan daily at 4:00AM. The problem behavior is that
> >if
> > Defender cannot run the daily scan at 4:00AM (e.g., because the computer
> > is
> > not on), Defender will run the scan at some point later when the computer
> > is
> > on (e.g., 1:00PM). My computer is essentially unusable during a full scan.
> > I've actually had to do a hard power-down to get the machine back. And,
> > there
> > is no indication that the problem is Defender running a scan unless you
> > open
> > the UI.
> >
> > Suggestion: Either skip scheduled scans that could not be executed because
> > the computer was off or provide an option for doing so.
>
>
>

Missed scans - I am still experiencing random scans after missed scans on
one machine and none on another. It also seems to me that one update
downloaded and installed itself - but that may have been the user pressing
random icons, though he denies this.
"Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
news:OlE9qADPGHA.1444@TK2MSFTNGSA02.privatenews.microsoft.com...
> If you can get the UI up, there is a cancel button, and this has worked in
> my experience, although I can easily imagine that it might not in the
> circumstance you describe. I've seen a post stating that a missed scan is
> initiated 10 minutes after a subsequent login or switch on--not sure
> which.
>
> --
>
> "brown3141" <brown3141@discussions.microsoft.com> wrote in message
> news:382EA7B7-D305-4D99-8249-03DD13A12617@microsoft.com...
>>I have Defender set to scan daily at 4:00AM. The problem behavior is that
>>if
>> Defender cannot run the daily scan at 4:00AM (e.g., because the computer
>> is
>> not on), Defender will run the scan at some point later when the computer
>> is
>> on (e.g., 1:00PM). My computer is essentially unusable during a full
>> scan.
>> I've actually had to do a hard power-down to get the machine back. And,
>> there
>> is no indication that the problem is Defender running a scan unless you
>> open
>> the UI.
>>
>> Suggestion: Either skip scheduled scans that could not be executed
>> because
>> the computer was off or provide an option for doing so.
>
>

If autoupdate is working, you may well see updates installed with no
intervention.

I don't have an answer for the scanning behavior--doesn't sound right. It
should scan when scheduled if the machine is on. Missed scans may be done
starting 10 minutes after the next logon--but I don't know if this is an
"always" or whether there are more factors.

--

"AuntieKate" <auntiekate@hotmail.com> wrote in message
news:Oi92KTWPGHA.3432@TK2MSFTNGSA01.privatenews.microsoft.com...
> Missed scans - I am still experiencing random scans after missed scans on
> one machine and none on another. It also seems to me that one update
> downloaded and installed itself - but that may have been the user pressing
> random icons, though he denies this.
> "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
> news:OlE9qADPGHA.1444@TK2MSFTNGSA02.privatenews.microsoft.com...
>> If you can get the UI up, there is a cancel button, and this has worked
>> in my experience, although I can easily imagine that it might not in the
>> circumstance you describe. I've seen a post stating that a missed scan
>> is initiated 10 minutes after a subsequent login or switch on--not sure
>> which.
>>
>> --
>>
>> "brown3141" <brown3141@discussions.microsoft.com> wrote in message
>> news:382EA7B7-D305-4D99-8249-03DD13A12617@microsoft.com...
>>>I have Defender set to scan daily at 4:00AM. The problem behavior is that
>>>if
>>> Defender cannot run the daily scan at 4:00AM (e.g., because the computer
>>> is
>>> not on), Defender will run the scan at some point later when the
>>> computer is
>>> on (e.g., 1:00PM). My computer is essentially unusable during a full
>>> scan.
>>> I've actually had to do a hard power-down to get the machine back. And,
>>> there
>>> is no indication that the problem is Defender running a scan unless you
>>> open
>>> the UI.
>>>
>>> Suggestion: Either skip scheduled scans that could not be executed
>>> because
>>> the computer was off or provide an option for doing so.
>>
>>
>
>

"Bill Sanderson" wrote:
> I don't have an answer for the scanning behavior--doesn't sound right. It
> should scan when scheduled if the machine is on. Missed scans may be done
> starting 10 minutes after the next logon--but I don't know if this is an
> "always" or whether there are more factors.

It would be far more user friendly if the "run the missed scan 10 minutes
after logon" could be disabled. I just killed another in-progress scan.

Suggestions:

1. Make "run missed scans at next logon" configurable.

2. Make the "warn after [n] days of no scans" configurable.

I would disable the former and set the second to something between seven and
fourteen days, since I do a complete scan about once per week.

---Jim

Thanks--sorry I missed this earlier. I think the behavior on your #2
request has changed--that was a bug. It isn't configurable, but n is longer
than 3--perhaps 8?

Sticking with a quick scan as the scheduled scan should eliminate most
performance complaints about the scans, I suspect.
--

"brown3141" <brown3141@discussions.microsoft.com> wrote in message
news:7C6778F3-B53C-44FF-973C-29E38AAF11E1@microsoft.com...
> "Bill Sanderson" wrote:
>> I don't have an answer for the scanning behavior--doesn't sound right.
>> It
>> should scan when scheduled if the machine is on. Missed scans may be
>> done
>> starting 10 minutes after the next logon--but I don't know if this is an
>> "always" or whether there are more factors.
>
> It would be far more user friendly if the "run the missed scan 10 minutes
> after logon" could be disabled. I just killed another in-progress scan.
>
> Suggestions:
>
> 1. Make "run missed scans at next logon" configurable.
>
> 2. Make the "warn after [n] days of no scans" configurable.
>
> I would disable the former and set the second to something between seven
> and
> fourteen days, since I do a complete scan about once per week.
>
> ---Jim