avast! AGAIN and AGAIN and AGAIN... [June 20, 2014]

[NewsArchive]

All,

Okay, avast! is doing it again and again!

http://www.avast.com

See attached screenshots. Version resource embedding and icon injection is
again blocked. This is such a waste of time for our support. The avast!
guys fix it and a few weeks or months later they introduce the very same
false-positive bug again.

Reported (and ticket opened) at least 20 times in three years, fixed 20
times, re-introduced 21-times... This is the worst project management I
have ever seen in my whole life.

So if you are still an avast! user, you know what you have to do.

Oh boy! This is killing me!

Friedrich

P.S. To fix it temporarily: Settings -> Global Exclusions -> Add the
mentioned file path.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

[NewsArchive]

To make it searchable. Error messages are:

1. error GEN1025: Unable to write version resource:

2. Fatal Compiler Error: GEN1094: Cannot inject stub loader entrypoint:

In the next SetupBuilder maintenance update, we'll add avast! to the
compiler error message. "Note: If you are using an avast! product and you
see this error message, please contact avast! Customer Care and refer to
#TICKET XYZ"

Friedrich

[NewsArchive]

Hi Friedrich

I understand you exactly. In the past we also got a lot of support calls
from our customers. "Suddenly" our dll files were destroyed by avast. We
also had to exclude our application directory in avast. Of course, we
uploaded our "suspicious" dll files to them, but never ever got a
reaction. Very bad.

So again and again: avast SUCKS!!! :-(

Best regards,
Jeffrey

[NewsArchive]

Good idea!

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Okay, enough is enough. SetupBuilder support is under heavy load right now.

This is the new error message in the next SetupBuilder maintenance release.

Friedrich

[NewsArchive]

Just curious - but can you detect if any of these are actually
installed? If so, then perhaps you can set your own flag upon SB8 start
up. Then you could re-word the error message:

Your current installation of Avast! has reported a false positive.
Please refer Avast! support to ticket #xxx when you send them a copy of
the file they have issues with. Meanwhile, add an exception for your
project - refer to the Avast! documentation on how to do this and then
recompile your project.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Russ,

The problem is that it seems to "block" the generation of the file. It
happens when the compiler writes the version stamp to the PE Header of the
(on-the-fly) generated setup file and/or when the compiler embeds a custom
icon into the file. You can disable the file version or inject icon
function and the same project compiles without any error. Enable version
stamping and avast! complains again.

The good thing is that a developer from the avast! viruslab came back to us
and they are working on it now. Unfortunately, still quite a few support
requests in our InBox :-(

Friedrich

[NewsArchive]

BTW, there are quite a few different protection products and versions
available from the same vendors. Not easy to keep the list up to date and
you need access to all their editions/versions to extract the registry items
for product detection.

I really hope that avast! will fix it so I can remove avast! from the
compiler error message. avast! Media / Communication and Development /
VirusLab came back to us very quickly.

ESET didn't have the intellectual capital to fix a similar issue in their
products. They even tell our customers that it is not one of their ticket
numbers.

Friedrich

[NewsArchive]

Sounds pretty smart to me<g>

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.

[NewsArchive]

Hubboy!

> ESET didn't have the intellectual capital to fix a similar issue in their
> products. They even tell our customers that it is not one of their ticket
> numbers.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Excellent - sock it to them.

> Okay, enough is enough. SetupBuilder support is under heavy load right
> now.
>
> This is the new error message in the next SetupBuilder maintenance
> release.

J André Labuschagné

[NewsArchive]

The avast! developers have fixed it in the new definition update.

To be honest, I am impressed. Good job!

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner