Search the Community
Showing results for tags 'compiled exe'.
Greetings to all, This may relate in regards to My question: If I have 2 different au3 scripts compiled individually as a standalone executable(s) (compilation settings are the same) OR If I have one au3 script compiled as a standalone executable(s) with different compilation settings. Does an Anti Virus see them as one signature for all? or treated as unique signatures? My reason behind this is that I am trying to plan ahead on how to deal with these false positives. I am a part of a small IT admin team that would like to automate some repeatable task
Hey there, I didn't really know how to name the titel .. so let me explain it a bit further. You all might know that a compiled Autoit-Exe gives an error message containing the Error and the line when it crashes. Often those messages aren't usefull because it states the line in the compiled script is not the line in your script if you have used includes. Decompiling the exe often doesn't help either. Well .. I don't want to start a discussion about the benefits of those messages. I just want to disable them. I want my exe to just fail an crash and that's it. Nothing more. When there's
Howdy, In a bizarre twist of events a client installed McAfee Antivirus Plus (the paid version). I have scripts running there, the simplest is a little HTTP downloader, which opens HTML pages and downloads some files. These scripts have been running for years. The new AV kills the process. The process just "disappears" with no warning. I can not find an "exception" setting. IT on site had to kill it in the Task Manager and restart the PC. All other AV products (even the free ones) have an easily accessible Exception setting. Note that the standard McAfee that typically comes with Acroba