DavidR
4
It doesn’t matter what it looks like, if it happens to be corrupt ‘so what.’ It isn’t an indication that it is infected, e.g. it just can’t be scanned and that was the reason why, nothing more nothing less.
- 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 unless you are getting problems relating to that file outside of the avast scan.
This particular example is somewhat strange as in the BIT7036.tmp file being an archive of sorts (that’s what the |> indicates) as the outlook.msp (update installation patch another archive/cab) file is within that file and is either corrupt or avast can’t open/extract the contents to be scanned.