Custom Scan problem!

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

Guest

I am trying to get Windows Defender to scan my ext hard drive E: through a
custom scan, however it only appears to want to scan c: drive. Does anyone
else have this problem?...or am i doing something wrong?
 
I don't have an external drive handy to scan--it seems to be happily
scanning a drive on a server some miles away via VPN at the moment, however.

I take it that the external drive does not show up in the UI for the custom
scan? How is it connected?
 
Ok, i figured out that it is scanning the ext E: drive, however it seems to
like to want to scan C: drive first. Lord knows why when i only want it to
scan E:. I figured this by disconnecting E: drive mid scan (which is
connected via USB), i got an error 0x80508019 advising me to reconnect the
drive...and yeah the UI shows that it is scanning C:, things like Word,
Works, Media Player etc etc, things i dont want to scan.
 
It does this, and lots of folks find it disconcerting, or worse.

My take on it is that it is trying its best to be sure something isn't
running that might conceal the true content of whatever you are asking it to
do a custom scan of, but I don't know.

--
 
Hello Bill,

it does not matter what you ask WD to scan, it start to scan the c:\ drive!!
A other thing is when you close the program while scanning with the red
x, the program is still scanning without showing anything!
Normal if you close a program it stops!!
Also nobody has a item in the allow list, cant remember anything!!

Regards >*< TOM >*<

Bill Sanderson schreef:
 
I'm not worried if it is scanning the C: drive aswell, obviously there is a
reason for it, like you suggest, it could probably be to check that something
is not concealing itself as something else. My problem at first was that I
thought it wasn't scanning what I wanted it to, but now I know it does, it's
all good.
Thanks.
 
I just read a message in a different group, where the query was, "How can I
get Spybot Search & Destroy to scan a single drive."

The reply from the author (second hand) was essentially that you could not,
that by design it starts with the registry hives it can see and works out
from there, scanning everything it can see that might be relevant.

I think that is what is happening with the quickscan and with this scan at
the start of a custom scan. There's at least one Microsoft post in these
groups giving an explanation of quickscan versus full scan dated today, as I
recall. Any way-- I don't think it is doing a full quckscan, but I think it
is attempting to be sure no known spyware is already running before going on
to check the selected specific area.

--
 
Back
Top