I'm having a problem with the NOD scan. It will start out doing great . You can see the progress in the task bar and it is moving along. But when the graft gets about three forths to the end it stops . Nothing shows up in window to indicate what is being scanned and it just sits there chunking away not moving. I have another question. I have 2 hard drives. One is just to store digital photos. On scan targets it won't let me uncheck it. Maybe that is where my hang uo is. Please help.
I have the same problem. It gets to about 3/4 of the way and then it just sits there. No files show as being scanned and the percentage at the end just flashes 0% off and on. I let it sit there for about 45 minutes and it never moved from that point. It has happened now on three attempts to scan with NOD. My system information follows if it matters... NOD32 Antivirus System information Virus signature database version: 1.606 (20040124) Dated: Saturday, January 24, 2004 Virus signature database build: 4174 Information on other scanner support parts Advanced heuristics module version: 1.005 (20031222) Advanced heuristics module build: 1047 Internet filter version: 1.001 (20031104) Internet filter build: 1012 Archive support module version: 1.008 (20031127) Archive support module build version: 1078 Information on installed components NOD32 For Windows NT/2000/XP/2003 - Base Version: 2.000.9 NOD32 For Windows NT/2000/XP/2003 - Internet support Version: 2.000.8 NOD32 for Windows NT/2000/XP/2003 - Standard component Version: 2.000.9 Operating system information Platform: Windows XP Version: 5.1.2600 Service Pack 1 Version of common control components: 5.82.2800 RAM: 512 MB Processor: Intel(R) Pentium(R) 4 CPU 2.40GHz (2386 MHz)
Well then it does not appear to be related to the 000.8 or .9 update. I had downloaded the installer when I read here that it was now the newer updated version. I was thinking that this was the cause of the problem. But now it is perhaps something else. I have never had a problem with NOD just kind of stopping during a scan prior to this.
NOD32 Antivirus System information Virus signature database version: 1.606 (20040124) Dated: Saturday, January 24, 2004 Virus signature database build: 4174 Information on other scanner support parts Advanced heuristics module version: 1.005 (20031222) Advanced heuristics module build: 1047 Archive support module version: 1.008 (20031126) Archive support module build version: 1077 Information on installed components NOD32 For Windows NT/2000/XP - Base Version: 2.000.6 NOD32 For Windows NT/2000/XP - Internet support Version: 2.000.6 NOD32 for Windows NT/2000/XP - Standard component Version: 2.000.6 Operating system information Platform: Windows XP Version: 5.1.2600 Service Pack 1 Version of common control components: 5.82.2800 RAM: 512 MB Processor: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794 MHz)
Maybe it's a bug related to the processor Pentium IV like the shutdown bug that only affect if you've Pentium IV. I've AMD and all here work OK. A Eset moderator can reply this better.
All is well here, no problems on scan... NOD32 Antivirus System information Virus signature database version: 1.606 (20040124) Dated: Saturday, January 24, 2004 Virus signature database build: 4174 Information on other scanner support parts Advanced heuristics module version: 1.005 (20031222) Advanced heuristics module build: 1047 Internet filter version: 1.001 (20031104) Internet filter build: 1012 Archive support module version: 1.008 (20031127) Archive support module build version: 1078 Information on installed components NOD32 For Windows NT/2000/XP/2003 - Base Version: 2.000.9 NOD32 For Windows NT/2000/XP/2003 - Internet support Version: 2.000.8 NOD32 for Windows NT/2000/XP/2003 - Standard component Version: 2.000.9 Operating system information Platform: Windows XP Version: 5.1.2600 Service Pack 1 Version of common control components: 5.82.2800 RAM: 511 MB Processor: Intel(R) Pentium(R) 4 CPU 2.40GHz (2386 MHz)
I just tried a TDS3 scan and when it got to C:\System Volume Information\Restore(31414675-6CBE-4639-8F67-8C2E-395D) it hung. So I stopped it. I just recently reinstalled Windows XP . Do you think that could have anything to do eith it? Please help. Thank you.
Hi WilliamP! TDS-3 seems to produce false alarms and hangs from time to time when scanning with USER privileges... Try to scan as admin or run TDS-3 with admin privileges, maybe this solves the problem If that doesn´t work I suggest posting in the TDS-3 forum! Greetz Storm
Ok, I went and turned off system restore, which then deleted the system save points. I then defragged my drive, rebooted, and turned system restore back on. I scanned with NOD and it went through fine. It seemd to start doing what it was before but I brought up AMON and it showed that files were being scanned even though none showed on the NOD scanner window. So this seems to have fixed the problem for me at least. Or maybe I just needed to be a little more patient when scanning before who knows
I set up NOD32 to scan C drive only. It was trying to scan F which is digital photos.Scan went great . No problems.