Error 42127 cab archive is corrupted

I received three of these errors locating this issue system volume information restore section corruption in a boot scan. I cannot find any details related to this topic or prescribed actions.

I hope that someone wiser than me is reading these posts.

Thanks for the help.

Prescribed action, ‘do nothing’ couldn’t be simpler.

  • 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 outside of the avast scan.

Files that can’t be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.

Is there a spot that explains the error codes as I could not locate these code explanations.

I guess I don’t know how we jump from errors found indicating corruption to software cannot scan the file can you help me find these explanations so I avoid asking questions that should be self explanatory.

Thanks

I don’t know what the error code is and to be honest I don’t think you are going to find anything other than what the accompanying message states ‘cab archive is corrupt.’

If an archive is corrupt, then avast can’t unpack the contents to be scanned, hence the file can’t be scanned. I thought that this was self-explanatory.

Well after looking this over I can see why I am confused. I read the program response as a description of the computer condition after scanning files indicating that corruption or malware exists. I did not recognise this type of labeling as indication that Avast could not unpack or scan these files. I have seen AVast label files that it could not test as “unable to scan”.

In the list of files labelled as “unable to scan” will also have the reason given, commonly this is password protected and on occasion archive corrupted. This reason may not be fully visible and you would need to expand the column width of the list to see the rest.

Many AVs don’t bother to tell you about files that can’t be scanned as they feel it unduly worries the user. I don’t know if this list of files that can’t be scanned will be displayed by default in the upcoming avast version 5.

In reality I am more concerned about the trojan sophos indicates that Avast is not locating

please use one topic.

http://forum.avast.com/index.php?topic=47710