Avast WEBforum

Other => General Topics => Topic started by: muymalestado on June 19, 2013, 01:51:26 PM

Title: "Some files could not be scanned"
Post by: muymalestado on June 19, 2013, 01:51:26 PM
Free anti virus version for domestic use.

After Quick or Full scans this message tops the Scan Results panel, followed by a list of path+filenames.

These seem to occur in groups each group of files related to one or other program and all with Status "Error: Archive is password protected (42056)".  There is no Severity and no Action.

Some programs are 'odd' to me others seem more like system programs, such as 'install_flashplayer'.

Should I worry?
Should I find these and delete them?
Is Repair a disabled feature for the free version?

Thank you.
Title: Re: "Some files could not be scanned"
Post by: Asyn on June 19, 2013, 02:44:41 PM
1. Should I worry?
2. Should I find these and delete them?
3. Is Repair a disabled feature for the free version?

1.-3. No.
Title: Re: "Some files could not be scanned"
Post by: Pondus on June 19, 2013, 03:01:48 PM
Quote
"Error: Archive is password protected (42056)".  There is no Severity and no Action.
because they are not infections...... avast will only take action on infected files, and infected files are given a malware name

search the forum for.... Archive is password protected   or   Some files could not be scanned ....and you find lots of info
Title: Re: "Some files could not be scanned"
Post by: DavidR on June 19, 2013, 03:03:15 PM
Files that can't be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.

Many programs (usually security based ones) password protect their files for legitimate reasons, there are others (and avast doesn't know the password or have any way of using it even if it did know it).

By examining 1) the file name, 2) reason given by avast! for not being able to scan the files, 3) the location of the files, you can get an idea of what program they relate to. You may need to expand the column headings to see all the text.

If you can give some examples of those file names, the locations and reason given why it can't be scanned might help us further ?
Title: Re: "Some files could not be scanned"
Post by: rob24 on July 19, 2013, 09:01:26 PM
Sorry to butt in on a oldish thread. I see there's lots covering this. I got this a month or so ago, now for the last couple days I am again. It is presumable something to do with old files but below is a screenshot, one showing the path
Title: Re: "Some files could not be scanned"
Post by: Pondus on July 19, 2013, 10:46:46 PM
empty Your recycle bin and reboot...do a New scan....any change?

Title: Re: "Some files could not be scanned"
Post by: rob24 on July 20, 2013, 12:17:23 AM
Well sort of a change. But still a load of files not scanned. I guess not to worry though. I wonder if it has to do with System Restore. I tried to do a restore a day or two ago and it was unsuccessful in that it did not restore the computer to a earlier time. It's a pretty broken OS after several years now.
Title: Re: "Some files could not be scanned"
Post by: Pondus on July 20, 2013, 12:23:01 AM
yes they are restore Points... you may remove old restore Points if you want....

anyway, as you already know, files not scanned errors are just a scan error report and not a infection....avast just tell you it could not scan the files and the reason why
Title: Re: "Some files could not be scanned"
Post by: Jim Bruce on January 19, 2014, 04:37:32 PM
I had the same "Some Files Could Not be Scanned" error message. 

I put this on an FTP site, then discovered this forum allows attachments (this is nice!).  A suggestion though, I think its useful for all such reports to be in text files so that cutting and pasting bits of them would be easy.  I could even cut an individual file name and search for it.

If its any easier here is the image file which your browser will display.

http://www.lex.sk.ca/couldnotscan.jpg

Any advice as to what these files are and what can be done?

Jim

Title: Re: "Some files could not be scanned"
Post by: DavidR on January 19, 2014, 07:23:23 PM
As has been said:
Files that can't be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.

Given that they are in a temp folder it looks like it is an incomplete download (that is the .part file type) and avast can't unpack the password protected archive (.part file)

Empty your temp folder if you wish.
Title: Re: "Some files could not be scanned"
Post by: Jim Bruce on January 19, 2014, 08:01:46 PM
Browsed to this folder in Windows explorer

    C:\Users\Jim\AppData\Local\Temp\TEMP

Folder is reported as "empty" although I have set file read options to show invisible files.

I assume this means that these files could not be repaired but they were deleted?

Jim
Title: Re: "Some files could not be scanned"
Post by: Michael (alan1998) on January 19, 2014, 08:04:00 PM
Hi, THey might be set a .sys files. Nothing wrong.
Title: Re: "Some files could not be scanned"
Post by: Pondus on January 19, 2014, 08:12:02 PM
Quote
I assume this means that these files could not be repaired but they were deleted?
avast is a antivirus program and will only take action on infected files.....

you can empty temp folders with TFC cleaner    http://www.geekstogo.com/forum/files/file/187-tfc-temp-file-cleaner-by-oldtimer/

Title: Re: "Some files could not be scanned"
Post by: Jim Bruce on January 19, 2014, 08:21:22 PM
I never deleted my files manually from the temp folder but Windows Explorer reported the folder as empty.

What then has happened?  Are the file fragments there and can't be read as files?

Should I take two aspirins and assume everything is all right  under the assumption that what I can't see can't hurt me?   :D
Title: Re: "Some files could not be scanned"
Post by: Pondus on January 19, 2014, 08:27:48 PM
run TFC and they are gone .... for now

it is normal to have some files that cant be scanned (they are not always located in temp folders)...this happens to evry AV but not all show it in the log ...on some you have to activate advanced logging to see scan errors


Title: Re: "Some files could not be scanned"
Post by: Jim Bruce on January 19, 2014, 08:37:23 PM
So..they can't be scanned they can't be erased so....

Where are the little b_ _ _ _ _ _ , they are not in the folder where AVAST says they are...?
Title: Re: "Some files could not be scanned"
Post by: Secondmineboy on January 19, 2014, 08:40:56 PM
If you ran TFC or Ccleaner they are gone now. :)

Theres nothing more to do.