quick scan

[Guest]

No matter what I try I do a full scan . I want to do a quick scan . Thank
you .

 

[Guest]

biblejim8
A full scan takes 90 minuyes on my notebook . I terminated most of the
quick scans only after ten minutes except in two cases I left them run the
entire 90 minutes. Thank you .

 

[Bill Sanderson]

Here's something to try.

Scans are in fact done by a command-line program you can initiate yourself.

Go to a command prompt.

cd to \program files\windows defender

(adjust for drive letters if necessary on your system)

mpcmdrun scan scantype 1 <enter>

should get you a quickscan, 2, should get you a full scan.

I've no idea why something so seemingly simple might fail--so it'd be
interesting to know whether it fails at this level too.

--

 

[Guest]

biblejim8
Tried it. Received " system cannot find the path specified" . I have only
one hard drive, C: , on my notebook. Thank you.

 

[Bill Sanderson]

Ok:

start, run, cmd <enter>

this should get you a cmd prompt.

cd \ <enter>
cd \program files\windows defender <enter>

mpcmdrun -scantype 1 <enter>

This will initiate a quickscan. If you run Windows Defender, and wait a few
seconds, you can see the scan in progress.

Does this work?

 

[Guest]

biblejim8
Triggers a full scan in all cases . Thank you .

 

[Bill Sanderson]

How about lets try:

Start, control panel, add or remove programs, Windows Defender, click here
for support information, repair.

Alternatively (if that makes no difference)

same process, but Change, Update instead of click here, etc.

This one is unique. I have seen a report of a machine on which a quickscan
is running 3 hours--perhaps that is the same syndrome, but I believe that
case stated that the fullscan was 6 hours.

Last ditch I suppose is to uninstall, remove anything left in the program
files folder, and reinstall. Purists would say to remove things in the
registry, but I try not to go there if possible.
--

 

[Guest]

biblejim8
Still triggers a full scan in all cases . Thank you .

 

[Bill Sanderson]

OK--so if I am reading this thread correctly, you are running Windows
Defender on a notebook PC (running XP?), and both a quickscan and a fullscan
take 90 minutes?

I don't have any idea what's going on, even to the point of theorizing about
it, or trying to see what information would be useful to know to perhaps
troubleshoot further.

Scan start and ends are recorded in the system event log with source
WinDefend--do those log records clearly state quickscan and full scan--they
should be labelled?

--

 

[Guest]

biblejim8
pavilion ze4610us notebook 40gb harddrive 20.4 gb files running windows xp
sp2 fully up to date facts :

scans one after another 7 March 2006
quick scan 1 hr 26 min 1 249 860 items scanned
full scan 2 hr 34 min 1 241 451 items scanned system actually scanned
files twice
quick scan 3 min 49 sec 27 647 items scanned
quick scan 1 hr 22 min 1 249 960 items scanned

scans one after another 7 March 2006
full scan 2 hr 37 min 1241 550 items scanned first time through files took
1 hr 27 min definitely scanned files twice before terminating
quick scan 3 min 27 sec 27 647 items scanned
quick scan 1 hr 22 min 23 sec 1 250 381 items scanned
quick scan 1 hr 22 min osec 1 249 564 items scanned

not done one after the other
quick scan3 min 34 sec 27647 items scanned done the day before
quick scan 3 min 46 sec 27 647 items scanned done the day before

if I do a quick scan after a full scan the quick scan operates in about 4
minutes

 

[Guest]

biblejim8
pavilion ze4610us notebook 40gb harddrive 20.4 gb files running windows xp
sp2 fully up to date facts :

scans one after another 7 March 2006
quick scan 1 hr 26 min 1 249 860 items scanned
full scan 2 hr 34 min 1 241 451 items scanned system actually scanned
files twice
quick scan 3 min 49 sec 27 647 items scanned
quick scan 1 hr 22 min 1 249 960 items scanned

scans one after another 7 March 2006
full scan 2 hr 37 min 1241 550 items scanned first time through files took
1 hr 27 min definitely scanned files twice before terminating
quick scan 3 min 27 sec 27 647 items scanned
quick scan 1 hr 22 min 23 sec 1 250 381 items scanned
quick scan 1 hr 22 min osec 1 249 564 items scanned

not done one after the other
quick scan3 min 34 sec 27647 items scanned done the day before
quick scan 3 min 46 sec 27 647 items scanned done the day before

if I do a quick scan after a full scan the quick scan operates in about 4
minutes. Thank you .

 

[Bill Sanderson]

So it appears that you can, in fact, do either quick or full scans. Is this
thread about your being unable to reliably choose between the two?

I don't know what to think about your assertion that items are being scanned
twice. I wouldn't be surprised if a fullscan scanned the content of the
quickscan twice--i.e. did a quickscan and then a fullscan.

--

 

[Guest]

biblejim8
I can do a quick scan, about 4 minutes , only if I do a full scan
immediately before it.
And yes , a full scan on my computer cycles through all the files twice.
I've seen the item scanned count climb to over 1 000 000 and then start over
at 1 and climb back to over 1 000 000 before ending the scan .
Thank you.

 

[Bill Sanderson]

That's remarkable.

and this is manually run, so we're not talking about a scheduler snafu of
some sort?



--

 

[Guest]

biblejim8
All are manual runs . Other people have reported scans that take about
seven hours. I suspect they also are experiencing the same rescaning
problem . Thank you.