Problems with scheduled scans

[Guest]

I am using Windows Defender Beta 2 and am having problems when scheduled
scans run. About half way through the scan, the system will try to scan the
floppy drive and / or CR-ROM drive. As there is no disk in the drive I get a
system error message cannot access drive. This appears to happen with either
a full scan or quick scan. The problem did not occur in Beta 1.

I have tried adding drives A: and D: to the "Do not scan the following
drives or paths" section under the Advanced settings, but this makes no
difference.

As anyone else encountered this problem and can anyone suggest a solution ?

When the problem occurs, the cancel button has to be hit several times
before the error dialogue box disapears. I have now disabled the scheduled
scan and just performs scans manually. The problem does not seem to happen
with manual scans.

 

[Bill Sanderson]

Am I correct in guessing that this is a Windows 2000 system? I haven't
observed a difference between scheduled scans and manual scans--I see this
as a bug--and the workaround for me is to put media in the drives in
question.

 

[Guest]

Thanks for the reply Bill.

Yes it is a Win 2000 System (SP4 with all latest patches).

 

[Guest]

I noticed this too on 2K Pro systems, and placing media into the drive was
the only way to continue (short of clicking continue several hundred times --
a real nuscience).

Perhaps Microsoft will correct this bug in a future update.

\\

 

[Bill Sanderson]

I believe Microsoft is aware that this happens--I don't have any further
confirmation that they can reproduce it, or that it is getting fixed--but I
believe they've seen the posts on this issue.