system
4
The “key” in such cases is to run the removal tool 3 times, with reboots in between, selecting the correct folder (if there is still one) and correct version each time, using always Windows Safe Mode.
Some users run the removal tool only once, or only using Normal Mode, which may be not enough in such rare cases like the one you described.
My estimates were wrong and their were actually 9 digit files in the folder! Fortunately it *[b]only[/b]* took about 4hours to clear the folder at a command prompt.
Again, my guess is that under Safe Mode, a simple
del unp*.tmp
while the prompt is already in the correct directory should be much faster and direct (specially being all zero-byte files).
Normally, this is unnecessary, and Avast should clean up itself once in a while.
A chkdsk /f on reboot reported no errors, avast cleanup tools ran, and for the next few days I have installed Microsoft Security Essentials for low level security while I research what may cause this.
If you want to reinstall Avast, remember to run the specific removal tool for MSE under Safe Mode before installing Avast.
The other tool I notice installed is Malwarebytes Anti-Malware - installed as the free 'no live scanning' option. Not sure if this would cause this issue,
Even if there is some problem with both tools installed, it would be not enough to cause this issue. What I mean is that having Avast and MBAM Free both installed might (or not) be a necessary condition, but it is not enough to cause this problem, since many other users use both without having this type of problem.
The only thing that is clear is that Avast was not able to delete old defs files, so some “block” attribute, or Administrative permissions, or something alike, was interfering with Avast cleaning up itself.