Hi, we're a charity using Symantec Endpoint Protection 11.06 clients on our PCs.
We have a custom-developed .NET application which has an auto-upgrade function which allows it to overwrite itself with a new .EXE file when we want to roll out a new version.
However we have discovered that overwriting the .EXE file leads to Symantec Network Protection identifying the EXE as a possible threat when it tries to access the network. The users then see a dialog like this:
What can we do to avoid this? Or, in other words, what is it that triggers this warning exactly?
Would using Signed .NET Assemblies help? Is it something to do with
how the EXE is overwritten?
Thanks in advance for any advice.