Unable to Scan C:\WINDOWS\SYSTEM files.

Avast Free Antivirus / Premium Security
1

I tried an archive scan, then stopped it as it was going to take quite some time, however when I stopped it the results of the last scan appeared, and there was 11 listed lines of C:\WINDOWS\SYSTEM\ with various .dll and .exe files in it.

Why would Avast Beta 4.8.1128 not be able to scan these files?

EDIT,

When I right click a file on the Results of last scan screen and click on scan, it successfully scans, why did it not scan it the first time?

Just tried the other 10 files on that results screen and the message for them was An error has occured during the processing of 1 result, I get this for the 10, but the first one that makes the total 11 was ok.

2

Can you copy & paste here that 11 lines of files not being scanned?

3

Sorry I don’t have them anymore, and I didnt have the option ticked for to create a report.

Unless there is another option for me to find these lines then I’m afraid they are now lost.

If I remember rightly they were in a temp folder, and some were from Adaware that I do not use any longer.

4

Temporary files could be deleted. avast could have access denied to them while scanning.
Adaware files could be password protected. avast do not use brute force to open archives and scan them.
Everything seems logical and ok…
Do you think you’re infected?

5

I don’t think so.

I tried using the exclusions and I tried adding the windows system folder, however when I done a scan I noticed that the windows system folder was indeed still being manually scanned, why would this be? is it because the windows system folder is scanned by default? and should never be excluded?

By the way, some of those files that were not being scanned were indeed password protected, but most worrying of all was that some said that the archive was corrupted! and some were system files, so I am slightly worried about that. Of course this was before I was trying out the exclusion folders.

6

Archive corrupted are inert, can’t harm your system. Could be an avast problem (its internal unpacker) or a problem in the file itself. Don’t worry.

Hmmm… Which entries are in your Exclusion lists right now?

7

Folders that I know are ok such as music files etc.

I did try excluding the Windows Sysyem folders, but they manually scanned, so I removed them from the exclusion list, funny how they still scanned tho.

8

You should never do that… you’ll opening a big door to infection… a huge one…

9

I have taken these exclusions off now apart from the folders for personal files, I did this to make the scan quicker.

10

So, use the on-demand exclusion list, not the on-access (resident) one.

11

Sorry but how do I do this?

12

You need to use the Exclusion lists:

For the Standard Shield provider (on-access scanning):
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize.
Go to Advanced tab and click on Add button…

For the other providers (on-demand scanning such as the screen-saver or the Simple User Interface):
Right click the ‘a’ blue icon, click Program Settings.
Go to Exclusions tab and click on Add button…

You can use wildcards like * and ?.
But be careful, you should ‘exclude’ that many files that let your system in danger.

13

Thanks for that info.

Is this a different way of excluding folders? the other way by right clicking on the blue icon, then program settings, then exclusions.

I take it any one of these ways is for manual scanning only, or is this for the auto scanning that takes place when browsing the web and or opening files.

14

No.

This is for on-demand (manual) scanning only.
Into Standard Shield and WebShield there are exclusion lists also. For files, Standard Shield, for webpages, WebShield.