Windows Defender Working Fine

[Guest]

Like many others, I am not having any trouble with scans or definiions.
After some problems upgrading from Beta 1, with the help from this news
group, I have followed these posts and wondered if it was working as it
should. I believe it is! One question I have however, is if there is a
problem will I be informed? I also run CCleaner for cookies etc. The full
scan runs about 1hr. 45 min. which is about the same as in Beta 1. Just
wondering about notification of problems found. Thanks to all in these posts!

 

[Bill Sanderson]

This depends on the settings. A scheduled scan may be set to take the
default action--this is in tools, general settings. If that's set, those
actions (the default action depends on the severity of the threat) will be
taken without your intervention, but will be recorded in history, which you
can view. Otherwise, for example on a manually initiated scan--you will be
presented with results and nagged until you do something with them.

 

[Guest]

Yes, I see those settings and they appear to be working just fine. Again
thanks for your attention! Very helpful!

 

[History Fan]

The full scan runs about 1hr. 45 min. which is about the same as in Beta

1. Just
wondering about notification of problems found.

That's kinda slow, isn't it? I just ran a Windows Defender full scan
and it took 14 minutes. I have 6GB used on my computer, with a P4 processor
at 2.4Ghz.

 

[Guest]

Have no idea what you are talking about all I know is every full scan I have
taken with this program or any other such as ewido etc. takes sbout the same
for a full scan. However, a quick scan only 10-15 min. Following others
posting on this site it is pretty normal. Maybe I am wrong, but I am
satisfied. Maybe someone will advise.

 

[Bill Sanderson]

Scan times are dependent on a number of factors--disk speed, processor speed
(a fullscan is cpu intensive because I believe it computes hashes for every
file) and number of objects. Objects include every file in every zip or cab
or .ISO file--so there can be a lot of them--more than most folks expect.

I see a range of 1 minute to about 10 for quickscans in office machines, but
there's what looks like a reliable report of a 3 hour quickscan in this
group--so things vary--I believe on that system a fullscan is 6 or 7 hours.

--

 

[Guest]

Thanks for the info. So a full scan running 1hr 45min is not abnormal for a
home user not office files? I am not an expert only a novice. I do
appreciate the information I read in the various news groups. I don't mess
with things if they seem to be working okay. Thanks again!~

 

[Bill Sanderson]

No--that sounds quite well within normal bounds. There's a good message
from one of the Microsoft staff posting in these groups about the
differences between the scans, and I believe that the quickscan is a
suitable default for most purposes. I'm generally doing full scans only
when something's found on the quickscan.

--

 

[Guest]

Okay, Thanks again!!

No--that sounds quite well within normal bounds. There's a good message
from one of the Microsoft staff posting in these groups about the
differences between the scans, and I believe that the quickscan is a
suitable default for most purposes. I'm generally doing full scans only
when something's found on the quickscan.

 

[Guest]

Bill,
Sorry to jump in on this but sounds like you have alot of knowledge. Also
thought I saw your name in a rather lengthly discussion involving "in valid
pointer" error after receiving "no scan in three days" message. I too was
able to launch the scan from the menu bar. So many threads with so many
thoughts. couldn't find the discussion again.
Anyway, the discussion drifted off in another direction which was TDFM. I
believe the cure was to remove MSAS and its directories and issue some
"run,cmd,.." processes. I have no MSAS entries in "add remove programs" but I
do have a MSAS directory . I'm running XP Home SP2, not on a net. I think the
earlier discussion involved a network user.

I am currently running WOC which has implied the inclusion of Defender in
the public release in June. If this is the case, I can live with this extra
step, scan from the menu bar, unless its a good idea to remove MSAS
directories for house keeping purposes.

Thanks in advance

Patrick

No--that sounds quite well within normal bounds. There's a good message

....deleted for space...

 

[Bill Sanderson]

I would ignore the idea of removing the Microsoft Antispyware folders. I
really don't see any connection between them and any issue with Windows
Defender. I think they are extaneous--and if space is a concern, I'd get
rid of them, but I don't think removing them will "fix" any issue with
Defender.

I think the errors launching scans directly will get fixed over time with
updates.

 

[Guest]

Bill,
Thanks, I'll wait for future releases.

Patrick