LabVIEW 2023 Errors after .EXE build

[JanisLabGuy]

Hi,

understood that .exes in the internet could be .... dangerous.

I also talked to the IT guys.

The guess with the antivirus software was neglected: If you could simply pass an antivirus software by holding the enter key to floud the system with instances, this would be too easy, right? I Think every instance is checked by the antivirus software, but I agree, it still seems to be the best guess.

My question would still be: can I somehow find out if the vi file is corrupted, i mean, its working as VI in Labview completely fine, seems to be a build error that is not shown. Could be blocked through antivirus software as a software that "creates" an .exe could possibly be a virus for any defender software....

[GerdW]

Hi Janis,

---

@JanisLabGuy wrote:

My question would still be: can I somehow find out if the vi file is corrupted, i mean, its working as VI in Labview completely fine, seems to be a build error that is not shown. Could be blocked through antivirus software as a software that "creates" an .exe could possibly be a virus for any defender software....

---

Have the IT guys check the antivirus logfiles

• when you create an executable
• when you open/run the executable

[JanisLabGuy]

Hi,

i think the root cause is found: its the Antivirus software. We do not get any information from the antivirus software that the message i get is from the software or any data is in quarantine, but it is visible in the protection history tab in windows.

I cannot access the risk events in detail due to admin restrictions, but we will check that and it will probably do the trick to somehow make an exception regulation. I would wait for this to happen and post it here if it is solved or not. 

[JanisLabGuy]

Hi,

so the issue actually is the Windows Security.

Unfortunately Windows Security never popped up to say "Hey, Windows Security here, we have an issue with your file.".. Thanks Windows 😉 

Anyway i would therefore say it can be closed as the issue is the Antivir/Security topic. I think next step is how the organisation can exclude the created .exe but i think that can be done with the URL timestamps and signature somehow.

The solution is therefore more or less to exclude in the security of windows or the antivir software,