WD; Long scan times

[Guest]

I noticed a very slow response from my laptop (XP home SP2) and decided to
run a scan. It has been over 24+ hours and still has not completed.

The summary indicates that 13000+ objects have been scanned. Also, a
particular file is being displayed as the current item being scanned:
c:Windows\system32\oleaut32.dll

I don't recall downloading anthing before my machine started acting up.
BTW, inaddition to WD, my anivirus is Avast.

Does sound like a WD install issue or a virus/spyware?

Thanks for all you help.

 

[Bill Sanderson MVP]

Is this a full scan, or a quickscan?

I think that it is more likely that this is a beta issue than malware, but
you should investigate.

Can you run a Quickscan, and is the time more reasonable? Quickscans on
machines I work with range from under 2 minutes to about half an hour. I
have seen reports of longer times--into "hours"--but not "days!"

Also--what Windows Defender version are you on? (See the top number in
Help, about.)

If it is 1.1.1051.0, consider downloading the newer code available a the
download center:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&displaylang=en

(this code is not yet being made available for automatic download--so users
who downloaded before April 12th will have the older code unless they've
chosen to re-visit the download.)

This code has a number of fixes in it, so it is possible it might do better
for you.

 

[Guest]

Is this a full scan, or a quickscan?

I think that it is more likely that this is a beta issue than malware, but
you should investigate.

Can you run a Quickscan, and is the time more reasonable? Quickscans on
machines I work with range from under 2 minutes to about half an hour. I
have seen reports of longer times--into "hours"--but not "days!"

Also--what Windows Defender version are you on? (See the top number in
Help, about.)

If it is 1.1.1051.0, consider downloading the newer code available a the
download center:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&displaylang=en

(this code is not yet being made available for automatic download--so users
who downloaded before April 12th will have the older code unless they've
chosen to re-visit the download.)

This code has a number of fixes in it, so it is possible it might do better
for you.

Bill,
Thanks for your quick response.
I checked the version and this is what I have:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1372.0
Definition Version: 1.14.1410.10

I tried running a quick scan and the scan hangs for about 45 seconds when
it get to :

C:\WINDOWS\system32\oleaut32.dll

Have you ever heard of an issue when scanning this particular dll?

 

[Bill Sanderson MVP]

Yours is the second message I've read today mentioning that file and an
issue related to scanning times.

I don't know what this might be about, but I'll see if I can get any leads.

--

 

[Bill Sanderson MVP]

Hmm - I was misremembering--your post is what I was recalling! This .dll
file is one that has a number of versions, and which is used by lots of
apps--it's quite possible that the scan is looking at the chain of apps
connected to various code at a given moment, and that this may take some
time.

--

 

[Guest]

Hmm - I was misremembering--your post is what I was recalling! This .dll
file is one that has a number of versions, and which is used by lots of
apps--it's quite possible that the scan is looking at the chain of apps
connected to various code at a given moment, and that this may take some
time.

Bill,
To clairfy another point. The scan continues to come back to that
particular dll as the scan continues. As I come back to view the progress,
the number of objects scanned has increased but the file being scanned is
still the oleaut32.dll.

 

[Bill Sanderson MVP]

I don't know--does it seem like it is in a loop? How long does the
quickscan take?

--

 

[Guest]

I don't know--does it seem like it is in a loop? How long does the
quickscan take?

The last complete "Quick Scan" took over 24 hours. After I uninstalled and
reinstalled WD I ran another quick scan. It was zipping along untilit kept
coming back to the oleaut32.dll. Then I just stopped the scan.

Hope this gives you more information on my problem.
Thanks again,
T

 

[Bill Sanderson MVP]

OK - something is clearly broken. I have seen one other report involving
rediculously long scan times like these.
Thanks for the report.

For the moment, I'd turn off scheduled scanning and just use real-time
protection.
--