Should I exclude the TEMP folder from scanning?

[REDACTED]

One of the programs I use daily gets a sharing violation and loses info when one of its files that it created in the TEMP folder gets locked by Avast.  Their support people say that I need to exclude the TEMP folder so this won't happen again.  I think it would be a bad idea.

Thoughts?

[igor]

Well, any exclusion is more or less dangerous (depending on how exactly the mask is set, for example).

However, as far as I know, Avast scanning should be synchronous - i.e. there shouldn't be any sharing violation, the calling process is simply stopped and waiting for the scanning to finish (unless some strange multi-threaded processing takes place). Can you tell us more about the problem - i.e. what program is that, how to reproduce the issue etc.?
Thanks.

[stibi]

  Their support people say that I need to exclude the TEMP folder so this won't happen again.

Seems nonsense. At my computers TEMP ist not excluded, and I have no such problem.

[REDACTED]

One of the programs I use daily gets a sharing violation and loses info when one of its files that it created in the TEMP folder gets locked by Avast. ...

Thoughts?

Sorry for my English.

Same problem here, Windows XP Sp 3
In my case it happens with:

- 7Zip when I drag and drop files (7Zip creates a temp folder - inside system temp folder  containing extracting files; while when I use "Extract..." menu voice, the temp folder seems not to be created and so there's no problem)

- Thunerbird not always, when a file ends up in "Moz_mapi" temp folder

- Copernic Desktop Search 4.0: it writes some dll files in the temp folder
  • at startup: Copernic says it can't read the config file (which isn't in temp folder)and crashes
  • when opening the option window and it crashes again

Tried to set Avast not to use the Cache, and sometimes it works.

Now I've added a "write" esclusion for Temp folder and everything seems working

Cheers

[Para-Noid]

Seems nonsense. At my computers TEMP ist not excluded, and I have no such problem.

I wouldn't say anything until I know more about the file.
With all due respect, your system is "not" exactly the same as the OP's set-up.
It's always best to get as much information as possible before making such a comment.

@Giannux  Please start your own topic. It's extremely difficult to help two different users
               at the same time. Even more so because set-ups vary from user to user.

[stibi]

I wouldn't say anything until I know more about the file.

In this case I would check the file in the TEMP folder that  gets locked with Avast.