My Avast seems to have a massive glitch here. The scan results are mixing previous results with the new scan log, evidenced by it showing the VBS:FluffleMiner-D from a few days ago, in exactly the same places as last time. My scan results clearly say infected file but the scans amount of infected files is 0, any help would be appreciated. Added some screenshots, don’t know if they’ll be any help.
Could you rescan the files in the chest after updating… They should all come back no virus
Yes I did that before this happened. It is showing previous scan results as well as the scans results, sometimes it shows that those have been detected despite them being in the chest, sometimes it shows multiple copy’s of same Skydrive folder I’m then warning section. The screenshot clearly shows the scan says Virus found but no infected files.
You can right click and restore the files, then delete them from the chest
But that doesn’t explain why my scans are showing previous scan results as well.
Until files are deleted from the virus chest they will remain there, and the other scans will remain until you clear the logs
I have cleared scan results and when I do a scan the scan results show this scan logs and sometimes previous logs combined into new logs.
OK you have the intermittent bug that has been reported and they are working on
What does that bug do?
It fails to clear the log entries properly
Is there any fix or do I just have to wait for now?
It is just a matter of waiting until Avast fixes this minor problem
So when I do a scan and It shows Threat Found and the two FluffeMiner-D’s in same locations it’s an error?
Is it still showing the detections ? As this FP should have been cured with an update a day or so ago
Sometimes it does and sometimes it doesn’t
What is the VPS that you have ?
131116-1
I had this a few days ago…I have seen reports that it’s an FP and some that say it is a legit virus.
Not to be rude but we are not discussing the fact if its a false positive or not. We’re discussing why my Avast shows previous scan logs within the new scans log.
And thats a known bug which will be fixed in some update.