When i click MOVE TO CHEST i get this
AVAST ACCESS DENIED.
CAN NOT PROCESS :
C:\Program Files\COMODO\COMODO Internet Security\Quarantine\unp186031861.tmp
SO THEN I CLICK “OK”
THEN I GET ANOTHER POP UP FROM AVAST…
MOVE/RENAME, DELETE, REPAIR, MOVE TO CHEST, OR NO ACTION…
SO I CLICK NO ACTION
and then again i keep getting pop ups asking me to make a selection
its dirving me nuts, how can i stop this…
I believe the virus has been Quarantine by COMODO
but avast will not stop with the pop-ups…
I have rebooted ad the pop ups have stopped. Only problem is the AVAST BOOT SCAN IS NOT CLICKABLE???
It use to work fine my my old XP system, but now i am using a VISTA WINDOWS X64 BUSINESS version
THE BOOTABLE SCAN DOES NOT WORK…
I am thinking because my windows is VISTA BUSINESS that perhaps the AVAST HOME EDITION thinks in fact
that this is a Business PC and will not allow that function, which is weird, cuz i only purchased this laptop
cuz it had all the features i wanted for a great price. So only thing i can do not is run a bootable scan.
So far 225 rookits have been found, and i am using COMODO to search for virus, since i dont want those pop-ups
again keep poping up non stop has they did b4 with avast. Which it found viruses in a Quarantined folder in COMODO.
I have processing the info provided by the link above, which follows
=========================================================================
If after following David’s advices, VirusTotal shows the files as being infected, I suggest:
Disable System Restore and reenable it after step 3.
Clean your temporary files.
Schedule a boot time scanning with avast with archive scanning turned on. If avast does not detect it, you can try DrWeb CureIT! instead.
Use SUPERantispyware, MBAM or Spyware Terminator to scan for spywares and trojans. If any infection is detected, better and safer is send the file to Quarantine than to simple delete than.
Test your machine with anti-rootkit applications. I suggest avast! antirootkit or Trend Micro RootkitBuster.
Make a HijackThis log to post here or, better, submit the RunScanner log to to on-line analysis.
Immunize your system with SpywareBlaster or Windows Advanced Care.
Check if you have insecure applications with Secunia Software Inspector.
Having two resident scanners installed is not recommended as rather than provide twice the protection it can cause conflicts that could leave you more vulnerable.
So you should choose which AV you wish to use and completely remove the other, e.g. uninstall the comodo suite, reboot and do a custom reinstall excluding the anti-virus element.
The boot-time scan doesn’t work with 64bit OSes, Alwil are trying to find a way round that, but currently not.
Your two AVs are fighting over the bones, avast unpacks files it needs to scan in the avast4 folder (a sub-folder of Temp) and the file names are in the form of unp186031861.tmp, when avast completes its scan it will empty that folder.
So this looks like a self inflicted wound, I don’t know if avast would have been able to scan and detect this temporary file if it hadn’t been intercepted by the comodo AV element. But this is just one of the problems with two resident scanners. and this kind of to and from alerts will continue as long as you have two resident AVs fighting over malware that is recognised by both.
I just installing COMODO Firewall or maybe it says Comodo Internet Security (or something similar with Comodo Antivirus include). I found no conflict with Avast! Antivirus.
I was trying to install a kind of harmfull program, while it was in the proccess, this Comodo suite give warning in the firts place (by giving a pop up box with option), the avast! pop up came in seconds behind (the yellow warning box above the taksbar), I chose to delete using Comodo, and the Avast! pop up warning just disappear instanly just as it used to be after an action taken by Avast! itself.
There is no conflict yet, but I’m not sure 100% if it is okay both of these two antivirus working stimulantly.
Well the case of the OP is a classic case of two AVs scrabbling over what is the same bone, resulting in multiple alerts.
It is also true in your case so I can’t see how you can say there is no conflict, if there weren’t you wouldn’t be getting multiple alerts on the same file. All you are seeing is a very mild form of this conflict, just the multiple alerts, at the other end of the scale is a conflict that could lock up your system or the AVs which could leave you more vulnerable rather than better protected. Your system your choice.