Antivir problem

[NewsArchive]

Hi,

We have a great problem with antivirus programs.

After the Setup is complete, the antivirus programs delete or cancel
some files. You don´t see any information about how files are blocked.

Is it possible to check all files from the setup is it install or not?

best regards

Dirk

[NewsArchive]

Dirk,

> We have a great problem with antivirus programs.
>
> After the Setup is complete, the antivirus programs delete or cancel some
> files. You don´t see any information about how files are blocked.
>
> Is it possible to check all files from the setup is it install or not?

Well, the setup installed the files without any problem, but AFTER that the
anti-virus decided that your files are devil. So you have to contact the
anti-virus vendor and report the false-positive bug. You should do this
immediately! Otherwise, you'll run into a support nightmare sooner or
later.

Hope this helps.

Friedrich

[NewsArchive]

BTW, and code-sign all your own application files (.exe, .dll, .ocx, ...).
This can help to 'minimize' false positives; or not <g>. If the anti-virus
/ anti-spyware vendor has a bad day then you are out of luck.

Friedrich

[NewsArchive]

:(

thx Friedrich !

Dirk Büchel

[NewsArchive]

> :(
>
> thx Friedrich !

We experienced a similar issue last year. Our internal automated license
registration systems worked fine and without any source code modification
for more than six years. This system handles the serial number and
subscription key stuff for all SetupBuilder users worldwide and is located
in a protected folder.

The avast! Internet Security protection system downloaded a new virus
definition update and suddenly, the license registration system crashed with
"This application has failed to start because yadayada.dll was not found.
Re-installing the application may fix this problem."

Hmmm, it turned out that !avast simply REMOVED ("false-positive") one
component from the protected folder. And of course, it did not help to
restore the file from a backup -- avast! "re-removed" the file immediately.
Adding the file to the scan exclusion list did not help either.

It turned out that this component (a Visual Studio written DLL) was not
code-signed. But we had a code-signed equivalent available (very same
version, code-signed a few seconds after the compile date). BINGO. That
worked fine and we were back in business. Code-signing application files
can help :-) but no guarantee. We reported the false-positive to avast!

Friedrich