Troubles With NOD32 System Scans

Hi, I'm trialing NOD32 v2.51.28 with the latest virus defs. I am using it on a fresh install of XP/SP2 with no other AV software. I have set up NOD32 using Blackspear's guide.

The problem is that the scheduled nod32.exe weekly scan will not complete. It starts at the appointed time, runs for about 20 seconds , and quits without any warning or information. It does the same thing when I run an on-demand scan. The scanner log shows the status of the scan as "cleaning", but the number of files scanned is zero.

The scan is set for my four partitions and I've used the Blackspear switches.

Can you help me get the scan to run properly?

 

Hi Beer Dog, welcome to Wilders.

Could you try rebooting your system and running a scan again.

Could you please list the switches that you have used (copy and Paste them) here.

Cheers

 

Rebooted but the on-demand scan still quits after scanning memory and a few folders in C:\. Then the screeen disappears.

In the "Run external application" box:
File: C:\Program Files\ESET\nod32.exe
Command line:
/local /adware /ah /all /arch+ /clean /cleanmode /delete /heur+ /log+ /mailbox+ /ntfs+ /pack+ /quarantine /scanboot+
/scanmbr+ /scanmem+ /scroll+ /sfx+ /unsafe /wrap+

 

I was able to run a scan by using Threat Protection Modules--->NOD32--->In-depth analysis. No threats found in 81727 files on C, D, F, and G partitions. Scan time---464 sec.

But scheduled scans, on-demand scans, and local scans all fail.

 

Hi Beer Dog,
Blackspear appears to be offline at the moment.

Would you mind posting a screenshot of the following please :-

Start an In-depth scan as you described above
Once it begins click 'Stop'
Click on the 'Setup' tab and post a screenshot of that tab
Also a screenshot of the 'Scanning targets' tab may be useful.

Cheers

 

Sorry for the delay in getting back; had to sleep and work my 10-hour shift. Things are still the same after shutting everything off overnight and cold-booting this evening.

 

Hope the two screenshots provide clues for a solution. And thanks for your help.

 

Thanks for that Beer Dog,

Yes, helps identify something - it seems your In-Depth scan is equivelant to not using the /mailbox+ /unsafe and /wrap+ switches, so there's some difference between them.

If you wanted you could try and leave those switches out of your command line one at a time and post back which one/s it makes a difference.

I'll leave you in Blackspears more than capable hands - his support is excellent. Please be sure to read carefully anything he suggests and follow his instructions.

Cheers

 

I took a slightly different approach and made the In-depth scan equivalent to the Scheduled scan. Did this by checking email files, potentially dangerous applications, and wrap log. I trust that doing this gives both scans the same switches.

After ticking off those 3 options, I was able to run the In-depth scan to completion.

 

It looks like the /wrap+ switch is the culprit.

I removed it from the scheduled scan, ran the scan on-demand, and it completed! Then I put /wrap+ back in the list, and it quit after 20 seconds when I ran it on demand. Finally, I removed it from the list once again, scheduled a scan for a few minutes ahead, and that scan ran to completion. Looking good!

But why does enabling text wrapping in the log file lead to such a problem? Searching the forum yielded a thread with this very scanner problem, and one of the solutions was to delete the log file before scanning. Could there be a bug with scan logging? Perhaps Eset could take a look. Also, why does the /wrap+ switch seem to work with the In-depth scanner and not the scheduled scans?

Thanks, Blackspear and NOD32 user for all your help.