Avast Full Virus Scan Stuck
Scanning your PC for viruses with Avast Antivirus. Full Virus Scan: a predefined, in-depth scan of your system that checks your storage drives and memory for malware (including rootkits). Targeted Scan: scans the folders you select when you initiate the scan. Choose File types to be scanned. When Scan all files is checked, your scan is more thorough but slower. You can also specify that potentially suspicious files are detected based on either: Content - Avast examines each file to determine file type. This option is safer but the scan takes longer.
Windows 7 x64AMD A8 Processor Quad-core 1.5GHz8GB RAMAMD Radeon 6620G graphics card750GB HDDSo I downloaded AVAST today as I heard it was a good antivirus software and wanted to try it out. I started a scan today about 2 hours ago and while it is scanning different files every few seconds it is still at 0% and is incredibly slow.
At this rate it could take 24 hours to complete.Why is it so slow? I know my processor isn't the best but this is ridiculous. I usually use Microsoft Security Essentials and that would have a full system scan finished by now.UPDATE: It's finished now, I left my PC to go do something else about 2 hours ago and it has since finished. I guess nothing is wrong but it does still seem unusually slow. :A zip bomb, also known as a Zip of Death, Peta bomb or decompression bomb, is a malicious designed to crash or render useless the program or system reading it. It is often employed to disable, in order to create an opening for more traditional viruses.Rather than hijacking the normal operation of the program, a bomb allows the program to work as intended, but the archive is carefully crafted so that unpacking it (e.g.
By a virus scanner in order to scan for viruses) requires inordinate amounts of time, disk space or memory.Interesting: Parent commenter can. Will also delete on comment score of -1 or less. Any reputable one can.
Best Free Virus Scan And Removal
Most of the non-reputable ones can too.Not too long ago I had this discussion on the possibility of a zip-bomb getting through with people more knowledgeable than me that assured me that the instructions to open a lot of empty data from a compressed file would be easy to replicate and detectable by most anything after 2007 (was it 2007?).Worth noting that a program attempting to open a zip bomb would cause some gigantic memory usage (not enough memory would then cause it to crash).A fractal designer, now that's something I'd like to se how anti-virus fare against. (not impossible to create a new, not yet widely protected against fractal code, but they would probably cut off after 3 or 4 loops of the same code, much like they do with the zip bombs, leading to a Gb or so of wasted memory until they cut it, at least that's what I expect would happen).
I have never had a problem scanning with Comodo AV until today and mine stuck on this exact same file. Like all the previous posters I had to crash start my PC to get everything to work again. On reboot I went through Comodo checking to see that everything was working etc and noticed while clicking on the 'Update Now' AV button that an update from 1724 to 1725 was available and updated.Maybe some of the mods could tell what effect an automatic update would have on the AV if one became available during mid scan although i still find it strange that my PC and Hakunamatata's both stuck on the same file.
Windows Virus Scan
Free Online Virus Scan
Anyone got any ideas what would cause this to happen? Try to pin-point the trouble area with the context-menu scanner by scanning root folder by folderDocuments and SettingsProgram FilesWindowsetc, now in the folder that fails try to isolate the folder beneath that where it fails.If you can reproduce and know on what files and or folder it fails, please report back. It will help the Dev's to know what goes wrong, also please post the windows eventlog crash info from cavscan.exe or cmdagent.exeYou can also use Process Explorer and Process Monitor to watch cavscan.exe do it's job, on process monitor you could filter on cavscan.exe and only show file monitor activity to see in what file and or folder it last accessed. The cmdagent crashes with error code (?) 928 when scanning the file 'C:Program Files (x86)Xfirexfiretoucan6437857.xll' (always this file).
I've been running XFire for 4 years with many antiviruses, like Norton, NOD32, AVG and lately avast, and now Comodo, and had never had any problems with scanning it's files.The event error is a typical JIT crash, it is called by cmdagent.exe and handled by JIT. It happens the moment the scanner attempts to scan the file.I appreciate your concern and I hope that this issue can be resolved promptly.PS: I did not notice any cmdscan.exe process, only cmdagent.exe.