G
Guest
Full scan is taking 7 hours, would prefer to only run it once a week. Is this
possible?
possible?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
Just out of interest. How big is your HD?
Please run on-line this;
http://safety.live.com/site/en-US/default.htm
Еиçеl
Please run on-line this;
http://safety.live.com/site/en-US/default.htm
Еиçеl
G
Guest
I started a full scan on a laptop before I left for lunch, and WD was still
scanning when I returned after an hour or so.
WD was busy somewhere in C:\Program Files\Microsoft Encarta folder.
It was taking a lot of time scanning the MDST or MDDLX files some of
which are hundereds of MB in size. I stopped the scan, and have not
tried a full scan after the engine updates, but it appears as if that WD
is very slow when it comes scanning archives.
I have got a 60GB hard drive on the laptop, and according to Diskeeper
the Free Space on the drive is 80%.
A full scan with NAV takes about 30 minutes, and a full scan with ewido
takes about 25 minutes.
scanning when I returned after an hour or so.
WD was busy somewhere in C:\Program Files\Microsoft Encarta folder.
It was taking a lot of time scanning the MDST or MDDLX files some of
which are hundereds of MB in size. I stopped the scan, and have not
tried a full scan after the engine updates, but it appears as if that WD
is very slow when it comes scanning archives.
I have got a 60GB hard drive on the laptop, and according to Diskeeper
the Free Space on the drive is 80%.
A full scan with NAV takes about 30 minutes, and a full scan with ewido
takes about 25 minutes.
G
Guest
Hello Dusty,
I think you may have to work at excluding it from the scan, as an interim
measure. Tools, general settings, scroll down to advance settings, and hit
the add button.
I hope this post is helpful.
Let us know how it works ºut.
Еиçеl
I think you may have to work at excluding it from the scan, as an interim
measure. Tools, general settings, scroll down to advance settings, and hit
the add button.
I hope this post is helpful.
Let us know how it works ºut.
Еиçеl
G
Guest
If you read the help in Windows Defender, it recommends a daily quickscan,
and a fullscan only when something is found on the quickscan.
That's my recommendation, too. The quickscan is carefully designed--it
starts with ram contents and startup items and works back--so it is designed
to catch anything that is "live" - in memory or in startup vectors.
The fullscan is much more intensive--it looks at every file in an archive,
for example, but it isn't going to find more active infections than the
quickscan is.
and a fullscan only when something is found on the quickscan.
That's my recommendation, too. The quickscan is carefully designed--it
starts with ram contents and startup items and works back--so it is designed
to catch anything that is "live" - in memory or in startup vectors.
The fullscan is much more intensive--it looks at every file in an archive,
for example, but it isn't going to find more active infections than the
quickscan is.
G
Guest
The short answer is that you can use the Windows scheduled tasks facility to
do this yourelf, if you really want to.
However--consider only doing quickscans, and doing a fullscan only when
something is found by a quickscan--that's thre recommendation made by help in
Windows Defender.
Scans are done by \program files\windows defender\mpcmdrun.exe.
This is a command-line program--you can just run it at a cmd prompt and see
the arguments needed to get it to do the various things it can do.
If this is something you'd really like to get going, I can help you figure
out the precise syntax needed to create your own job to do that once-a-week
full scan--but I'm sticking with the quickscans mainly myself. except on
servers where I let it do a full scan in the middle of the night, on the
theory that it'll catch anything in user data space that might be worth
spotting.
do this yourelf, if you really want to.
However--consider only doing quickscans, and doing a fullscan only when
something is found by a quickscan--that's thre recommendation made by help in
Windows Defender.
Scans are done by \program files\windows defender\mpcmdrun.exe.
This is a command-line program--you can just run it at a cmd prompt and see
the arguments needed to get it to do the various things it can do.
If this is something you'd really like to get going, I can help you figure
out the precise syntax needed to create your own job to do that once-a-week
full scan--but I'm sticking with the quickscans mainly myself. except on
servers where I let it do a full scan in the middle of the night, on the
theory that it'll catch anything in user data space that might be worth
spotting.
G
Guest
Thanks for your help. I'll go with the scheduled quick scan, using the full
scan only when quick scan finds something.
scan only when quick scan finds something.
G
Guest
Great--I think that's the best course. Windows Defender can be scheduled
very flexibly, but not within the program.
very flexibly, but not within the program.