Question about NOD32 scanning

  • Thread starter Thread starter C J.
  • Start date Start date
C

C J.

Hi everyone,

Here recently I've noticed that scheduled scans are taking forty five mins
at a minimum - up to three hours. The same three volumes are being scanned.

Is this normal for NOD to do?
 
From: "C J." <[email protected]>

| Hi everyone,
|
| Here recently I've noticed that scheduled scans are taking forty five mins
| at a minimum - up to three hours. The same three volumes are being scanned.
|
| Is this normal for NOD to do?
|

It all depends on the the type of data, the quantity of data and the speed of both the CPU
and hard disk. If you have hundreds of thousands of files then 3 hrs sounds normal.

To reduce the scanning time, make sure all TEMP folders are cleasred and the IE TIFm Java
Cache and other Browser caches are kept to a minimal amount.
 
Hi dave, thanks for the reply. I've made sure to dump all the tempfile
locations (even Content.IE5) and reboot before scanning. Some nights the
scan of all three drives, has completed in 45 mins... only to take 3 hours
for the same drives, and amount of files the very next night.

As an example: lastnight it took 2:42:26 to complete, the day before only
took 46:27 ...
 
From: "C J." <[email protected]>

| Hi everyone,
|
| Here recently I've noticed that scheduled scans are taking forty five mins
| at a minimum - up to three hours. The same three volumes are being scanned.
|
| Is this normal for NOD to do?
|

It all depends on the the type of data, the quantity of data and the speed of both the CPU
and hard disk. If you have hundreds of thousands of files then 3 hrs sounds normal.

To reduce the scanning time, make sure all TEMP folders are cleasred and the IE TIFm Java
Cache and other Browser caches are kept to a minimal amount.
Click to expand...

Maybe reducing the depth of scan, like 'archives',
which as such aren't much danger unless extracted.
Oh, and while we're talking NOD,
is it normal for the kernel to be a non-removable system process?
(C:\Program Files\Eset\nod32krn.exe)
can be set to be ignored but not 'fixed' in hijackthis v2
 
Back
Top