G
Guest
NAV 2006 Quickscan appears to have a problem when the number of "startup"
files exceeds a certain level. After processing about 700 or so files it
loops consuming 80-90% of the CPU without only minimal file count
progression. Response of other processes is severely impaired giving the
impression that the system has frozen.
Windows Task Manager reports that process Navw32.exe that has been logging
about 1000 I/O Reads per second is now getting no I/O read activity. The
problem starts when the Handles stat reaches ~500 suggesting some sort of
file management table overflow. NAV 2005 on a similarly configured system
only processes 110 startup files and never encounters this limit. NAV 2006
may be including more files in this "startup" class.
A bypass is to UNCHECK the NAV Options / Manual Scan / Scan active programs
and startup files as well as NAV Options / Liveupdate/ Run Quickscan on
definitions update. A successful full system scan with these options turned
off showed no detectable viruses. Also a check_disk reported no problems with
the drive itself.
Symantec now has an open case for this problem.
files exceeds a certain level. After processing about 700 or so files it
loops consuming 80-90% of the CPU without only minimal file count
progression. Response of other processes is severely impaired giving the
impression that the system has frozen.
Windows Task Manager reports that process Navw32.exe that has been logging
about 1000 I/O Reads per second is now getting no I/O read activity. The
problem starts when the Handles stat reaches ~500 suggesting some sort of
file management table overflow. NAV 2005 on a similarly configured system
only processes 110 startup files and never encounters this limit. NAV 2006
may be including more files in this "startup" class.
A bypass is to UNCHECK the NAV Options / Manual Scan / Scan active programs
and startup files as well as NAV Options / Liveupdate/ Run Quickscan on
definitions update. A successful full system scan with these options turned
off showed no detectable viruses. Also a check_disk reported no problems with
the drive itself.
Symantec now has an open case for this problem.