When I do a boot scan Avast shows me that I have 3 corrupt files. Does Avast do anything with these corrupt files (fix, delete, etc) or is it just alerting me to the fact that they are there?
antivirus programs will only do something (clean / quarantine / delete) with infected files
so this is just a scan error message
By examining 1) the reason given by avast! for not being able to scan the files, 2) 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.
Files that can’t be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.
Also, the packaging of the file could have some error, or use a non-standard pattern…
Clean, Quarantine, or Delete?
http://antivirus.about.com/b/2007/03/11/clean-quarantine-or-delete.htm
So your saying that a corrupt file just means Avast cannot scan it? How do you fix or delete a corrupt file or do they need to be fixed or deleted?
@sjadventures
Can you please provide us the exact location and filename of the detected files?
A few weeks ago I made a boot Scan in Firend’s Vista PC and Avast said that it could not scan several files because they were corrupted, and I fixed it doing a disk check on the computer and it took away corruped files and replaced them with good ones.
rm
Can you advise on how to perform that?
How do you fix or delete a corrupt file or do they need to be fixed or deleted?It depends what the file(s)are fore.... so if you answer magna86 question we may be able to tell you....
Since when do AV scanners check for corrupted files?
What are the corrupted files?
Sounds to me like Avast is finding corrupted Avast files. In that case the solution is to repair or reinstall Avast.
Below is exactly what one of them said.
C:Documents and Settings \ Circuit City\My DocumentsDownloads\vcredist_x86.exepart|>vc_red.cab|>mfc90u.dll.30729.01microsoft_vc90_MFC_x86.SP Error 42127 {CAB Archive is corrupted}
They don’t specifically scan for corrupt files, but the try to unpack archive files. If they are unable to unpack them they could well be corrupt and that is what is being reported, a file cant be scanned and the reason corrupt archive, etc.
You can’t speculate as to what these files are when the OP hasn’t reported what these files are, file name and location. So we have to wait his answer to that question.
Now that he has just answered that they aren’t avast files.
Well the important part (excuse the pun) is vcredist_x86.exepart, and that appears to be a failed download as part is normally tacked on to the partial download before it has completed the download.
Since the file is incomplete and avast tries to extract the contents, part of the file is missing (corrupt) and that is why (the reason) the error is reported on a file that couldn’t be scanned.
Are the 3 corrupt files something I need to correct or delete and if so how? The other 2 were very similiar to the one I posted but did have a little variation but the front part of each corrupt file was the same. All of them included the part
As DavidR said, these are not filesystem corrupted files (so, nothing to do with chkdsk).
These are part of a CABinet file. Just as zipped files, CABinet files are archive files that can contain folders and other files. And just as zipped files, you could have several files that are acting like a chain:
part001.zip
part002.zip
part003.zip
…
or, similarly,
part001.cab
part002.cab
part003.cab
…
or
part.cab
part.001
part.002
…
The point is, that they are a chain. Each part is not complete. Only opening the complete set, you would obtain the real complete content (imagine 3 CDs of 680MB each part, and you copy all 3 archive parts to your computer to rebuild the original complete archive contents).
In your case, either one of the parts is corrupted (and it simply would need to mistakenly change, say, a “zero” for a “one”, and all the complete set could be unreadable); or Avast is not able to understand this particular set of archives.
In any case, this does NOT necessarily mean that the archive (or a part of it) is infected. It may, or may not be. All that Avast is reporting is that, as far as Avast understands, the set of files that conform the complete set of archives can’t be opened and then scanned by Avast.
One explanation could be that one part of the set is not located in the expected folder, hence Avast doesn’t know how to open it. Whichever the reason, is not telling you “anything” definitive about that archive.
I understand the explanation and I am very appreciative of all the help but still do not know if I need to deal with the 3 corrupt files or ignore them.
See DavidR’s post reply #11. It’s an incomplete download. avast is unable to scan incomplete downloads.
The file is corrupt and “not necessarily” infected. Try to re-download the file. 
Will do . Thanks again everyone for the help.
You can try running chkdsk by right clicking C drive properties Tools check now, the first box if checked will check for bad sectors on reboot.
The second box will do a longer check but can take an hour or more.
Also it will not hurt to check system files by pasting this in command prompt or run— sfc /scannow
Do you have something with a name similar to “vcredist_x86” in your “Downloads” folder? From Avast’s point of view, there is nothing to do. From your point of view, you might want to check what that file/archive in that “Downloads” folder is doing there. Do you need it? Do you want it? Could you download it again (since an incomplete/incorrect download might be the source of this corrupted file/archive).
There isn’t a whole lot a user can do, other than to ignore files reported as being unable to scan as the archive is corrupt in the scan results.
They are in your Downloads folder, so presumably you downloaded them some time ago ?
Check how old the file/s is/are, creation date, the older they are the less important and if they are corrupt e.g. the download didn’t complete (the .part bit at the end of the vcredist_x86.exe.part file name, then you couldn’t install that vcredist_x86.exe update, making it worthless.
You won’t be able to find anything after the vcredist_x86.exe.part| as these files >vc_red.cab|>mfc90u.dll.30729.01microsoft_vc90_MFC_x86.SP are inside the vcredist_x86.exe.part file.