Avast blocking a beneficial file

Avast Free Antivirus / Premium Security
1

I am using a scripting program, Autoit, to build an EXE. In the process, I guess it uses some application (aut2exe.exe) to create a .tmp file. Avast File System Shield is blocking this .tmp file. Is there a way to remedy this?

I can see how to exclude files of certain extensions from File System Shield. But I would like Avast to continue to scan the .tmp files in the temp area. Is there a way to tell Avast that files created from this application (aut2exe.exe) are legitimate?

I’ve attached a screenshot as I’m not entirely sure how to create/view a proper log.

OS is Win 7 32-bit.

2

Just report that file as false positive and fill in the form.

3

Thanks for the reply. A couple follow up questions though:

  1. Does submitting that false positive form merely flag the TEMP file as legitimate? Or does it flag ANY TEMP FILES FROM THAT APPLICATION as legitimate? The former doesn’t help me at all; the latter is what I need.

  2. Once I submit the false positive form, does it go into effect immediately? Or do Avast representatives have to review and approve it? If the latter, will I receive any confirmation when that happens? When I have submitted these forms in the past, I have not received any confirmation.

Thanks

4

Sometimes Avast will respond in the thread. Most times after several virus definition updates (after you have submitted the file to Avast), you can scan the file while it is in the virus chest periodically to see if it is still infected or a false positive. I would give it a good 2 weeks, and if it is still infected, leave it there. If it comes out clean, then it was a FP. You can also verify with any of the online virus/url scanners as well.

5

Thanks for the reply. But I’m not sure that submitting a false positive report will resolve my problem. My application creates a different (randomly named) .tmp file every time it builds an EXE. Even if I submit a false positive report for one .tmp file, the next one will just get caught by Avast again (as it has a different filename). Am I interpreting this correctly?

6

So you are keeping these temp. files and not cleaning them out if I understand correctly?

What version and product of Avast are you using?

7

So you are keeping these temp. files and not cleaning them out if I understand correctly?

Thanks for your reply.

The scripting application I use compiles a script into an .exe file. In that process, it creates a .tmp file that (I assume) it must use in some capacity to carry out the .exe creation. As it stands, during the entire process, Avast is removing this .tmp file as soon as it is created. So the scripting application is failing in its attempt to create the .exe file, presumably because it cannot find the .tmp file.

I’m not sure if these details are exactly what is happening. What I know for sure is that the scripting application can create an .exe file without issue when Avast is disabled. When I enable Avast and re-run the scripting application, Avast blocks the .tmp file, the scripting application encounters an error, and the .exe file is not created.

What version and product of Avast are you using?

The latest version.