AVG protection and SetupBuilder IDE crashes

[NewsArchive]

-- AVG Antivirus & Antispyware and SETUPICON #pragma to customize the actual
installer icon.

Scenario: After updating your SetupBuilder (V7.x or V8.x) environment to a
new version -or- renaming the installer .exe name in Project Properties, the
AVG Antivirus system brings the SetupBuilder IDE "down" (crashes the
compiler).

Jane helped to track down this issue. Up to know, there is no known
workaround to this AVG bug, which is there "forever". After the crash, you
have to restart the SetupBuilder IDE and then subsequent compiles have no
problem.

The same might happen with the "#config Win32 PE header..." and "#embed UAC
manifest..." compiler directives.

The AVG system (real-time monitoring functionality?) causes a "crash" in the
Windows API which manipulates the generated executable. As a result, the
SetupBuilder IDE itself also crashes. The system does not even wait until
the Windows API call gives control back to SetupBuilder. It does not help
to exclude the folder where the .sb8 project file, source files, and
generated installer are.

Unfortunately, this is completely out of your control. If you notice this
on your computer and you are AVG protected, please report the issue to AVG.

--
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]

Yikes! Is this with AVG only? I use ESET, but to be fair, I don't use
this function, but would this explain the rare compiler crashes I get?
When I compile again, it works. Both the rareness of the crash and
the 2nd time it works is enough preventing me asking you about it. I
can't reproduce so why bother? <g>

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Russ,

> Yikes! Is this with AVG only? I use ESET, but to be fair, I don't use
> this function, but would this explain the rare compiler crashes I get?
> When I compile again, it works. Both the rareness of the crash and the
> 2nd time it works is enough preventing me asking you about it. I can't
> reproduce so why bother? <g>

The good thing with ESET is that (in most cases) it gives control back to
the application and we can report an error message if ESET blocks the .exe
manipulation process:

---
CHANGE : IDE: Under certain circumstances, customers with "ESET security
solutions" installed (e.g. NOD32) sometimes get a "Fatal
Compiler Error: GEN1094: Cannot inject stub loader entrypoint:
Para1: C:\yada\yada.exe Para2: 91648 Para3: 6664" or "Fatal
Compiler Error: GEN1093: Cannot inject main setup icon" errors
during the setup compilation process. This is caused by a
(false-positive) bug in ESET products. We have added an
additional compiler text: 'Note: If you are using an ESET
product and you see this error message, please contact ESET
Customer Care and refer to #TICKET 83977'.
---

But on rare occasions ESET also crashes that Windows API and brings the
system down. There is absolutely nothing that we can do :-(

The main problem is that neither AVG nor ESET have their heuristic
real-time-monitoring under full control. You can call it over-protective or
you can call it a bug <g>.

Friedrich

[NewsArchive]

Thanks! You are a responsible vendor. I don't expect you to solve
another vendor's issue (but perhaps there is some extra money in it for
you! <g>).

Reporting it is fine. And if my customers see something like this, I
know what advice I can give them.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

What I was seeing is not something your customers should see, Russ, unless
they have SB licenses.

It's not when the installer is run, but when it's being created.

What I tested at Friedrich's suggestion was:

1. Create installer XYZ. include the #setupicon pragma. Save. Compile in
SB. Appcrash and SB dies.
2. Reopen SB. Compile installer XYZ. Compiles fine.
3. Repeat until bored.
4. Copy installer XYZ to installer YYZ. Save. Compile in SB. Appcrash
and SB dies.
5. Repeat steps 2 and 3
6. Copy installer XYZ to installer YYY. Delete #setupicon pragma. Save.
Compile in SB. NO Appcrash. SB is happy. AVG (presumably) is happy.
Windows is happy.

Jane Fleming

[NewsArchive]

Jane,

> SB is happy. AVG (presumably) is happy. Windows is happy.

Happy. Happy. Happy.

Yeah, that's reasonably legal in California!<g>

Lee White

[NewsArchive]

But they tax happiness there.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Thanks for the clarification.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

But they do so for our own good !

Jane Fleming

[NewsArchive]

It's nice to be taken care of<g>

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