I recently did a start up scan with avast and I moved the following file into the chest because it was dectected as harmful:
C:\Window|Temp|Unp209643389.tmp FOR win32:PUPgen[PUP]
What is that file used for and is it actually harmful?
The file should be in the c:\windows\temp_avast_ folder, is that the location it is ?
That location is where avast unpacks or sends files to be scanned, giving them that file format, e.g. unp999999.tmp, normally after scanning this file and any others should be removed from the avast folder.
So why that folder wasn’t cleared is beyond me, do you have any other security software installed, e.g. anti-spy/malware ?
Auto deletion isn’t a good first option you have none left.
Unless you changed your settings when you scheduled/elected to do a boot-time scan ?
Then deletion wouldn’t be the recommended option, that would normally be Move to Chest, me I have it set to Ask (then I choose the action), see image. Note that I have also unchecked the Scan for PUPs (Potentially Unwanted Program) and Unpack archive files, inert unless unpacked and an executable run (before that would happen the file system shield would scan).
It asked you because it was detected (and your on demand scanning settings were set to do so, check them :)).
But it should be automatically deleted. Something blocked the deletion.
Do you use any other security program that could be interfering?
Is this MBAM Pro ?
If so that could be responsible for the file not being removed from the folder, so add the c:\windows\temp_avast_ folder to its Ignore List.
Personally I don’t feel they need mutual exclusion as you call it, if you read the link that Pondus gave it doesn’t even mention the folder I gave and this is the very area that you had a problem with. A possible conflict resulting in that temp file remaining, it may also have stopped avast from actually scanning it.
So for me you only need to exclude the folder I mentioned in my previous post, Reply #9 above.