If your investigations have not revealed that this file Avast has a problem with is actually a decompression bomb, move down to the next potential fix below. In case you’ve obtained it from a questionable place, just remove it from your system and initiate another boot-time scan in Avast at the next system startup. If this scenario is applicable and you have reason to believe that you might be dealing with a decompression bomb, the best way to fix the problem is to simply delete the file. These ‘decompression bombs’ are regularly used in DoS attacks meant at incapacitating virus scanners – The majority of security tools are aware of this practice so they refuse to scan the archive in order to avoid crashing the system or make it more vulnerable to attacks. These files have the potential to grow to be very big once they are extracted and possibly use up all the memory. The most common reason why this error message will occur is a scenario in which Avast things the file that it’s being analyzed is actually a ‘decompression bomb’ (also known as a zip bomb).Ī ‘ decompression bomb’ is a term given to archive files (RAR or ZIP) that have a very high compression ratio. Method 1: Warning against a Decompression Bomb

If this scenario is applicable, you should be able to get the issue fixed by temporarily disabling the System Restore functionality and allow your system to boot up without it to fix the problem. File corruption in the System Restore volume – Under certain circumstances, Avast is known to throw this error due to a corruption problem with the System Restore volume.In this case, you should avoid the file altogether and try to obtain the same data from a different source. You are dealing with a ‘decompression bomb’ – By far, the most common cause that might trigger this error code is an instance in which Avast thinks it’s dealing with an archive that might initiate a DoS attack if it’s unpacked.

Boot scan with avast