Hi,
Over the last few months, I have a recurring problem. I get a ‘disk full’ warning on my computer and it turns out (the first time I freaked out till I understood what was happening…) that Avast is generating a temp file of OVER 200GB to 100% fill my hard disk. At the moment my work around is to restart the computer, go to the location of the file and delete it - knowing that within a week it will reappear. I need to restart the computer because the file doesn’t appear in File Manager unless I do. And yes, I have I uninstalled then reninstalled Avast - and it still happens. While I am managing, I’d LOVE not to have to do this. Apart from anything else, it can’t be ding my computer any good.
Thanks you for any advise or help.
I am using a HP Spectre x360 13, with 8gb RAM and HD of 512 SDD and 64-bit OS. Windows 10 and Office 365.
Can you post the file location in question?
Wow; thank you for your willingness to assist me. And certainly, it is C:\Users\yongl\AppData\Local\Temp_avast_ (where ‘yongl’ is my user)
Not happening here.
https://screencast-o-matic.com/screenshots/u/Lh/1580927785679-11917.png
Are you using the latest version of Avast ?
https://screencast-o-matic.com/screenshots/u/Lh/1580927978474-30993.png
I see that you don’t have this issue; it makes me feel very special (!).
Avast is updated; this edition
http://C:\Users\yongl\Dropbox\Desktop\Capture.JPG
OOOPS… THIS
I’ve notified Avast. Let’s see if that helps
I’d love to find out what’s going on there - but I’m afraid we’d need some more information (you might not have). I think a similar problem has been discussed once or twice in the past here on the forum, but we’re not able to reproduce it.
You’re saying it’s a recurring problem… do you know how to trigger it, or what seems to trigger it? How often does it happen?
You can try to create&submit the support package (and post here the ID), as described here: https://support.avast.com/en-us/article/33/
I’ll check the logs if anything stands out. However, I kinda expect they won’t be very helpful…
What I think could help would be a Process Monitor log showing how this huge temp file is created. But successful capturing such a log somehow assumes you’re able to reproduce it (within a reasonably short time frame)…
Thank you for your interest; I am glad I have caught your attention! I have seen people complain of ‘large files’ of several MBs or GBs; no-one else seems to report what I have experienced - over 200GB files which clearly stop growing only when the HD gets - literally - full. I suppose I should feel special! As to your question, not, I haven’t any idea what triggers this. I have checked the location where the file appears from time to time to see if I can identify a ‘growing file’, but I have only ever seen in this location between 2-5 temp files of 0kb. Right now, for e.g., there’s 4 of them. All start ‘unp’ then afew numbers/letters. They were created about 4 days apart (not consistent distance between their creation, or times of day when it occurred). So the program to capture data - while a great idea - doesn’t seem relevant. Thoughts? THANK YOU!
You stated that you’ve uninstalled and re-installed Avast.
You didn’t say if you’ve ever done a clean install of Avast.
If your Avast settings are not the default settings and you want them restored after the Clean Install, follow this before removing Avast.
https://goo.gl/TXjM7h
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A
Personally I don’t think the “growing” file would be growing for long; I’d rather expect it to be created (and reach the huge size) almost instantaneously - when those special (unknown) conditions are met… though I’m just speculating.
While the Process Monitor tool can be running on background for quite a long time, even if you set the filter to monitor only the specific path - starting with C:\Users\yongl\AppData\Local\Temp_avast_\unp - the log can still be rather big and eat some memory (plus it’s easy to forget to restart the tool after the machine is restarted).
But there are some interesting things here…
First that the file is in your user folder (and not in c:\Windows\Temp_avast_)… I kinda missed it the last time, but it means it’s not the main Avast scanning service, but rather something else (still don’t know what though).
Second - no files should normally be left in those avast folders, in my opinion. I mean, the folder is used for temporary storage - so files can appear there, but - except for a “lock” file - should be removed soon (well, unless something like a Windows BSoD happens… or powering down the machine without closing Windows first). Files that cannot be deleted are OK (they are still being used); files that can be deleted there are suspicious. If you say you’ve got 4 files there, 4 days apart… i.e. files two, three weeks old there - that looks like an improper cleanup (could be an unrelated issue though).
Still, without being able to reproduce (or possibly the Process Monitor log), there’s little I can do I’m afraid.
First, I am so touched that you good folks keep trying to help me. Thank you so much. I had a hectic few days so lost track. One response to each of you - yes, I will try the 'clean install as per the instructions (thanks!) and secondly, you’re right! I just saw that I couldn’t delete the file ‘because Outlook is open’; in other words there’s some connection to Outlook. I’ll post a snippet of a screen shot in that regard (ouch; not opening. But it just shows what I wrote here!). I will report back if it occurs again after the clean un/install. Thank you again; most appreciated.
AFter I followed all the advice above, I just had another “Hard Disk Full” event. SO disappointing! Does anyone have further ideas? I am thinking to move away from Avast; this is crazy…
Thanks in advance for any new ideas,
Update to the latest version (20.1.2397): https://forum.avast.com/index.php?topic=232420.0
Based on your connection to Outlook, I tried to look for all the places where temp files can be created inside the Avast’s Outlook plugin… and I didn’t like one place so I changed it (for the next version 20.2).
Now I’m not saying the code was certainly wrong, or even responsible for what you’re seeing - i.e. no guarantees it really helps; it was a “blind” attempt, without knowing where/how the file is really created. But chances are it will help…
One more idea - when you encounter this problem, and while Outlook is still running (i.e. when the file still can’t be removed), could you create a dump of the Outlook process (e.g. choosing Create dump file from the context menu on that process in Task Manager) and upload the dump to ftp://ftp.avast.com/incoming - preferably compressed to a uniquely-named archive, and post the filename here?
It could confirm whether my change is related.