There are like 70 .TMP files in the Avast Free directory and most of them are between 1 and 2 MB in size. Are these used by Avast or are they just taking up space?? Can the be deleted with no problems?!? Thanks much.
What are the files? IOW what does it say before the .tmp?
Aav1A1.tmp, ash1AD.tmp, asw1B4.tmp, BCU3D.tmp, ETC. Not going to post them all 'cause too many. Bfore someone asks also running Avast Free 2015 on a Windows XP system.
Often best not to use Abbreviation in isolation:
One example IOW = Isle Of Wight there are many others, but the person would have to know if it is In Other Words or it causes confusion.
I take it no one has a reply about the .TMP files I asked about and listed some of??
I’m not seeing these in either my XP Pro or win7 netbook systems and I don’t recall seeing this reported in the forums.
If they are avast .tmp files (which they appear to be) then avast housekeeping should clear them up in due course. Are you getting any other avast error messages displayed to the screen ?
Have you just done a program update by any chance ?
If you have, does rebooting remove these ?
Check the avast Settings > General, scroll down to > Maintenance and expand the section - You could try to reduce the settings - but this isn’t directly related to .tmp files.
These files are in Avast directory which is updated at least a couple times weekly!! No avast error messages yet. And rebooting does nothing to these files as far as removing them. I have tried deleting and it says “access denied”.
That is because the files/folders are protected by the avast self-defence module - avastUI > Settings > Troubleshooting - enable Avast self-defence module.
Whilst they are in theory only temp (.tmp) files it is hard to say if they are in use or not and if their removal may have repercussions or not.
I removed Avast with Windows Add / Remove Programs then re-installed it and been running it for a couple days with same settings as before and updated it and scanned system both days and no .TMP files re-appeared YET and it runs fine so whatever the .TMP files were is beyond me.
A hiccup/corruption may be responsible for the .tmp files, reinstalling could well resolve that - this however is speculation. As I said before I have never seen this problem reported on the forums or replicated on my systems, weird.