Today, for the first time since using Avast 6 it has found a Trojan on my computer with a severity level of high. I tried to move it to my chest, but the apply button is not working. I tried to click apply, but it’s just not clicking. What should I do or is there a problem with my Avast 6?
Optional information: I have Windows Defender which came with my Windows 7, but Windows Defenders is manually scanned by me. So, hopefully it’s not WD fault or anything.
Would they happen to be detections in memory from using a custom scan with scan memory ticked ? some information on the detections would be helpful or a screen shot.
IF, and others who know more than I will answer this better, this is preventing Avast from working in windows, you might look at something that works during the boot cycle.
http://thepcsecurity.com/virus-scan-boot-disk-from-avira/
Scroll down towards the bottom of the page and many options are listed from other vendors, not just Avira.
What is the infected file name, where was it found e.g. (C:\windows\system32\infected-file-name.xxx) ?
For detection on on demand scans, check C:\ProgramData\Alwil Software\Avast5\log (windows Vista, windows 7).
Thought this sounds like - Detections in Memory -
My guess is that you are doing a Custom scan in which you have elected to scan Memory and that all these detections are in memory or are listings of files that can’t be scanned. Since they aren’t physical files they can’t be moved to the chest, deleted, etc. so there is no action that can be taken, hence the Apply button being greyed out.
The detections in memory are frequently other security applications loading unencrypted virus signatures into memory (possibly Windows Defender). Having set off a scan of memory by an antivirus application looking for virus signatures, don’t be too surprised if it finds some in memory.
So if you can give some examples of the items in the list and the type of scan you did it will help us to help you.
So, this is my first time using screen shot… I hope this is what you are asking for and um, could you all please use easier vocabulary words, because I am very technologically-challenged. I read your replies over and over and I think I finally understand what you are asking me. Yes, I did create a custom scan to scan everything along with memory.
I believe this trojan came from the memory part of the scan, because when I point the arrow over it, it says something like, "Process 532 [rundll32.exe], memory block *x********F, block size ******. I’m not sure if the numbers are important or not so I used asterisks instead.
So, is this a bad thing if a trojan is found in the memory? What should I do?
So, is this a bad thing if a trojan is found in the memory? What should I do?the bad thing is that using the "scan memory" setting will give some strange scan results
so we recomend using the quick / full scan with default settings…or if doing a custom scan DO NOT select “scan memory”
Plus tru a forum search on kelihos-s and rundll32 and memory scan and you will find that this is likely to be a false positive. Aside from scanning memory can through up lots of anomalies.
The C:.…|>root.img file is just a very big file that if decompressed would be very large, nothing to worry about.
But, is it alright not to scan memory though? Like, memories don’t get infected by viruses?
Thank you Pondus and DavidR for the help, greatly appreciated =D
No problem, glad I could help.
Welcome to the forums.