Thank you, Cecilia for your fast reply! You actually responded to what I specifically asked and wanted to know! I will certainly follow your advice! I also added the path C:\WINDOWS\Temp\* to Exclusions list in avast Settings to prevent this from happening again in future Ad-aware scans.
However, after rebooting Windows, I checked C:\WINDOWS\Temp directory and verified that the ********-****-****-****-************\tmp******** subdirectories were still there, still containing no other files than those restored by me from the Virus Chest!Ĭonsidering that those tmp******** files are probably avast's false positives, and that those files were likely produced by Ad-Aware during each scan and would probably be cleared out by the program itself, were it not for avast's untimely action, I want to know if it is safe to manually delete them now and the resulting empty directories containing them, given the fact that each file is 39,1 MB in size, which is not negligible. I then, restored the supposedly infected files from avast's Virus Chest to their original locations. It is noteworthy that in same tmp******** directories, there was another tmp******** file which disappeared as soon as Ad-Aware was closed. Immediately before each of the scans finished, Avast's File System Shield alerted me that it detected a tmp******** file infected with Win32:Evo-gen in C:\WINDOWS\Temp\********-****-****-****-************\tmp******** directory, attributed to the process AdAwareService (* are digits/letters) avast automatically and immediately quarantined those files.
Yesterday, I did a few custom and quick scans in Ad-Aware.
I use Avast Antivirus for real-time protection. I've been using Ad-Aware Antivirus only to do occasional on-demand scans.
0 kommentar(er)
