Hi Kurt,
We regret the inconvenience this has caused you.
Please let us know how you narrowed it down that your AVG Internet Security is causing this issue. Did you receive any threat messages from AVG while the files were being compiled?
If you did, please share us their screenshots, so that we can check & help you accordingly.
You can post the screenshot here in your topic. Click on Answer & then click on the Image [mountain symbol] & follow the instructions.
Thanks in advance!
Setting the .exe file in the temp directory into the Exclusion list solved the problem. But, it must be noted this introduces another insecurity issue. If a file name that is known to be used consistently is white listed, then any potential intruder could use that information to introduce malware to the system disguised with that name. It would be more secure to be able to tell the antivirus to ignore executable files created by a particular compiler that is installed and working in that system, rather than giving a file with a particular name a free pass. This would reduce the chance of a file of that name being introduced to the system by outside agents. It would be highly unlikely that an outside agent could gain access to the compiler in situ in order to hijack it to produce malware.
How do I configure Antivirus specifically to ignore .exe files that I am compiling in my own computer? AVG stops the compiling process with a 60 second wait time at each compilation, and I can't find a setting to ignore this particular activity. Adding an exception for the working directory and for the compiler does nothing. The interim executable "purebasic_compilation0.exe" keeps being analyzed and sent to AVG for analysis. I need to stop that happening.
I sent the AVGsysinfo zip file under case number 16273311. The .exe file is attached.
Thank you for writing us back, Kurl.
We are glad that your issue has been resolved by adding the exe file to exception, hoever it cn only be considered as a temporary fix.
For a permanent solution please send us the detected file along with logs so that we can analyse and whitelist it if there are no issues with the file.
We've sent you an email with further details. Please check your inbox/spam folders to find the email and use it to get back to us.
Awaiting for your response.
Setting the .exe file in the temp directory into the Exclusion list solved the problem. But, it must be noted this introduces another insecurity issue. If a file name that is known to be used consistently is white listed, then any potential intruder could use that information to introduce malware to the system disguised with that name. It would be more secure to be able to tell the antivirus to ignore executable files created by a particular compiler that is installed and working in that system, rather than giving a file with a particular name a free pass. This would reduce the chance of a file of that name being introduced to the system by outside agents. It would be highly unlikely that an outside agent could gain access to the compiler in situ in order to hijack it to produce malware.
Thank you for sharing the screenshot & updating the status, Kurt.
Please specify whether the issue persists after you added specific file path to the AVG exceptions.
Awaiting your response.
Hello Craig,
Thank you for writing us back.
We appreciate your efforts.
Our higher team will check this issue and will get back to via email as soon as possible.
Thank you for your understanding.