I apologize if this is something I’ve already brought up before, and I’m positive the topic in itself has been brought up before, but should we at all be worried about corrupted ZIP archives when doing boot-time scans? Even if we shouldn’t, is there any way to get rid of corrupted ZIP archives? If so, what is the best way to do it?
For your convenience, I have the full paths of some of such archives I was able to take screenshots of during the boot-time scan:
Yes it has been mentioned, but there is no need to be concerned.
Corrupted Archive file, this could simply mean that avast is unable to unpack it to scan the contents of the archive and assuming it is because it is corrupt. Even if it were corrupt there is nothing that a user can do to resolve any corruption, short of replacing the file. This I wouldn’t recommend (especially if this is for archives in the \System Volume Information folder, part of the system restore function) unless you are getting problems relating to that file/s outside of the avast scan. Presumably they aren’t an issue when using MS Office Templates.
Files that can’t be scanned are just that, not an indication that they infected.
but should we at all be worried about corrupted ZIP archives when doing [b]boot-time scans?[/b]
Boot time scan is not meant to be used as a regular scanner, it is a special tool to be used if you have problem removing a detected malware. Boot time scan does not have any detection advantages