debug executables flagged as malware?

[ElectroLund]

My company uses Symantec anti virus and this morning I was greeted with a bunch of my debug EXEs being flagged.  Is there anything I should know about here?  I doubt these are actually suspect files; most are from the example projects.

[Ian.W]

I use virustotal.com to check files and URLs with dozens of AV engines in one shot.  Though it does not get those positives removed from your Symantec filter, it could help convince them that their engine is creating false positives.

[kjellor]

Hi, did you get any feedback from NI on this one?

[ElectroLund]

No, I'm waiting on reply from my corporate IT.

[vix]

The same issue sometimes happens with TrendMicro WorryFree Business Security used in my company.

The false positive are usually fixed in a couple of days by TrendMicro, but I must reinstall the software previously deleted

This happens both with CVI and LabVIEW applications.

[gdargaud]

They probably flag everything not present in their database as malware ! And charge you for it.

[tombom]

Hi All,

I'm using LabWindows 2020 and Windows 10.

It seems that I get a similar error with the McAfee virus scanner:

The application consists of a single UIR with two command buttons ( a "Quit" and an "Inc A" button, which increments a variable A each time when the button is pressed. The application is cleaned, as the debug-exe obviously tries to connect to some cloud service. It is cleaned from the system and deleted.

The examples, however, seem to work without any problems.

Has anybody an idea how to fix this?

McAfee only gives me the option to disable the specific thread function. This might no be a good idea.

The project "IncA" is attached as zip file.

Best regards

[tombom]

Hi All,

at least for McAfee I possibly found a solution:

One needs to uncheck the Option "clean, if the recommended threshold is exceeded".

I do not know, if it is wise to do so, but at least I can debug the program.

Adidtionally, if I do not uncheck this option, the files created as "release" exe files are also not executed.

BR

[mlh5953]

I had a similar problem using Avast.

I was able to remedy the problem by 'signing' my application.

I added a digital certificate I created, and no more problem.

Had to do the same thing with the distribution package.

[holly7787]

---

@mlh5953  ha scritto:

I added a digital certificate I created, and no more problem.

---

Hello, I've got this malware problem too but not on every application... how did you create your own certificate?

thanks