Before you go ahed and remove them all, do consider where the file came
from, there's a good possibillity that the file could be O.K. while the
algorithm that Avast is using has trouble analyzing this multi-packaging
correctly at all times. One person on the forum you mentioned also says how
only one out of several of these files that he compressed himself was
flagged this way. If you trust the app that the file belongs to, then I
would leave it where it is.
It's no use trusting your anti-virus to dispose of your data, before
accepting any suggestion you should try and find out what kind of file it is
and where you got it from - if for nothing else, you may need it badly one
day, so where will you go then?
Tony. . .
"Denise" <> wrote in message
news

0580B4F-13EC-4C59-8BAB-...
> I ran a scan with Avast home version in normal mode. Avast came back with
> about 10 or so results that said, "Unable to scan: The file is a
> decompression bomb." I put them in quarantine and ran another Avast scan
in
> Safe Mode yesterday and they weren't there.
>
> When I Googled "decompression bomb" I found a post at a forum where
someone
> said that, "Typically such a bomb is a multi-level packing thing -- data's
> compressed with one packer (e.g. into a zip), then the resulting archive
file
> is in turn packed (usually with a different packer), and so on several
times.
> We had a thread here a while back reporting avast and system crashes from
> trying to scan an apparently small file (50 or 100K, if I remember) which
> would have eventually expanded, if disk space and memory were available,
to a
> couple of hundred gigs."
>
> My computer is running fine but I don't want these files taking up all
that
> space for nothing. Can I delete these files from quarantine?
>
> --
> Denise
>
> ~ If you don't know where you came from, you won't know where you're
going.