Files Avast cannot scan - Password protected

Wittmann · 2015-08-24T13:37:40.000Z

I did one of my many scans and a large list of residue appeared of files that Avast could not scan because they are “Password protected”. All of them seemed to be “png” files in the archives.

Having looked at the Avast blogs on this from previous users complaints, I did a search for “*.png” and all of these files are images or icons. None of them being at all suspicious.

From the Avast previous blogs etc. it is stated that all these Password protected files pose no threat whilst they are in the archives. It is then said that when any of these files become live, Avast will check them and will block them if any problems.

Is this resume correct ?

Pondus · 2015-08-24T13:44:17.000Z

yes, realtime protection monitor evrything that happens in your computer when on
any file that is unpacked/access/read/save/run … is checked in realtime

a file that can not be scanned does not mean it is infected, just that it could not be scanned for whatever reason avast give. it is normal

if you tell us what file / location … full file path, we may be able to tell you what they are

Wittmann · 2015-08-24T14:04:40.000Z

Pondus post:2:

yes, realtime protection monitor evrything that happens in your computer when on
any file that is unpacked/access/read/save/run … is checked in realtime

a file that can not be scanned does not mean it is infected, just that it could not be scanned for whatever reason avast give. it is normal

if you tell us what file / location … full file path, we may be able to tell you what they are

Thank you for that assurance. I have looked at them all and they are all quite innocent images or icons etc. to do with programs.

i am happy now, knowing that Avast will scan them when they become live and block any that are unacceptable. No need for further action.

A typical example is attached :-

bob3160 · 2015-08-24T14:08:12.000Z

Pondus post:2:

yes, realtime protection monitor evrything that happens in your computer when on
any file that is unpacked/access/read/save/run … is checked in realtime

a file that can not be scanned does not mean it is infected, just that it could not be scanned for whatever reason avast give. it is normal

if you tell us what file / location … full file path, we may be able to tell you what they are

Some more information on this topic can be found at:
http://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/

Wittmann · 2015-08-24T14:35:43.000Z

bob3160 post:4:

Some more information on this topic can be found at:
http://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/

Thanks Bob, that is the link where I got the answer and posted to confirm. I am happy now.

Pondus · 2015-08-24T14:44:42.000Z

you can test your AV function with EICAR test file http://www.eicar.org/85-0-Download.html

remeber this is just a text string, not a .exe file so evry function will not be triggered

bob3160 · 2015-08-24T14:44:55.000Z

wittmann44 post:5:

bob3160 post:4:

Some more information on this topic can be found at:
http://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/

Thanks Bob, that is the link where I got the answer and posted to confirm. I am happy now.

My pleasure.

Announcements