Exclusion doesn't seem to work for floppy drive

[Guest]

Hi,
I have Defender scheduled to run a Full Scan, except for a few items I
have added to the EXCLUDE list. One of these items is "A:\". However, when I
show up as DEFENDER approaches the end of it's long task, I hear it noisily
trying to access the floppy drive for about a minute. This is very annoying.
If it ignores the floppy drive, it might also ignore all the other items in
the Exclusion list as well.

Does Defender IGNORE the Exclusion list if it is scheduled to run with a
FULL SCAN?
How do I set up the General Settings under Tools, so it will scan the
complete system, except for the floppy drive, and certain shared folders?
I suspect it scans EVERYTHING, no matter what is in the exclusion list.

 

[Erhan Karabekir]

Hi
I have posted several messages in the past that exclusion doesn't actually
work; Defender ignores whatever you place in the Exclusion list and proceeds
to scan them. I placed Norton Internet Security files and folders in the
exclusion pan but Defender simply ignored this.
Erhan

 

[Guest]

Hi Erhan,
It seems that not only DEFENDER is ignoring the "exclusion list" - I am
surprised that Microsoft is ignoring the bug, by not responding to this
community with an acknowledgement.

 

[Joe Faulhaber[MSFT]]

Hi all,

I tried this by putting a file that detects as spyware on my A:\ drive,
pointing a run key to it, and having an exclusion path for the drive. My
a:\ drive did spin up, but the threat wasn't detected. If I removed the
exclusion, it worked properly. So I think WD is functionally correct. I'll
check in wether we can stop the drive from spinning up.

Regards
Joe

 

[Guest]

Thanks Joe [MSFT],
That is good news to hear. I don't know what WD is doing - it "rattles
and buzzes" the empty floppy drive for what seems about 30 seconds, causing a
real annoyance. I appreciate you guys fixing it.

I have a couple of "shared" file folders listed in the EXCLUSION list
along with the A-drive. I hope that WD is skipping them as well. Since they
are just massive data files, I don't need WD spending an extra hour going
through them each day either. I can't prove that it does, but I will schedule
a scan, and see if it attempts to do so.

One other item along this line - I notice that WD options for "SCHEDULED"
scans are only FULL and QUICK. Yet there is also a CUSTOM scan setup box,
which is not included as a third option. Is that an oversight?
--
Thanks
Joe

Hi all,

I tried this by putting a file that detects as spyware on my A:\ drive,
pointing a run key to it, and having an exclusion path for the drive. My
a:\ drive did spin up, but the threat wasn't detected. If I removed the
exclusion, it worked properly. So I think WD is functionally correct. I'll
check in wether we can stop the drive from spinning up.

Regards
Joe

 

[Joe Faulhaber[MSFT]]

I checked around, and the engine does resolve filetype and attributes for
the drive when figuring out what the system looks like, but that should be
the only disk activity when a drive is excluded. If you have more (filemon
from sysinternals can probably tell), please report it. Net is, I don't
think we have anything to fix here.

Custom scans are left out of the scheduled scans intentionally, since they
don't provide very good protection. If custom scan finds something, it will
then perform a quick scan (a little better than the normal quick scan,
actually) to do proper cleaning, but for regular protection, quick or full
are the only ones that we consider for "green" status.

Thanks,
Joe

Thanks Joe [MSFT],
That is good news to hear. I don't know what WD is doing - it "rattles
and buzzes" the empty floppy drive for what seems about 30 seconds,
causing a
real annoyance. I appreciate you guys fixing it.

I have a couple of "shared" file folders listed in the EXCLUSION list
along with the A-drive. I hope that WD is skipping them as well. Since
they
are just massive data files, I don't need WD spending an extra hour going
through them each day either. I can't prove that it does, but I will
schedule
a scan, and see if it attempts to do so.

One other item along this line - I notice that WD options for
"SCHEDULED"
scans are only FULL and QUICK. Yet there is also a CUSTOM scan setup box,
which is not included as a third option. Is that an oversight?
--
Thanks
Joe

Hi all,

I tried this by putting a file that detects as spyware on my A:\ drive,
pointing a run key to it, and having an exclusion path for the drive. My
a:\ drive did spin up, but the threat wasn't detected. If I removed the
exclusion, it worked properly. So I think WD is functionally correct.
I'll
check in wether we can stop the drive from spinning up.

Regards
Joe

 

[Guest]

O.K. - then I don't understand, if the activity is just a check, it
rattles the floppy for quite some (annoying) length of time, in about 3 or 4
bursts. Do you think that maybe other protection software, like Norton, is
trying to stop DEFENDER, and shutting down the access - thus the push/pull
rattle that goes on as both try to access the empty floppy drive?

Just a guess on my part, though.

Does "resolving filetype and attributes for the drive", as you say,
actually cause the drive to seek, etc. , or is that a table look up, and the
drive should therefore be silent, in such case?