PDA

View Full Version : Nod32 Daily Scan Freeze

jviper360
February 11th, 2008, 05:25 PM
My computer freezes when NOD32 runs a scheduled scan. Ctrl-alt-del doesn't even work! It seems to be okay if I run an on-demand standard scan. Any ideas what could be causing this? Btw, I'm running XP SP2.
BeanCounter
February 11th, 2008, 06:15 PM
I had the same problem with 3.0.621 installed on one of my machines. I installed 3.0.621 on three PCs and there were no problems with two of them. On the third PC I saw the same condition that you describe. As a temporary solution if have gone back to 2.7 on the PC that exhibited the problem.

Do you have MS Office installed?
jviper360
February 11th, 2008, 07:20 PM
I do have MS office 2007 installed.
Why?
BeanCounter
February 11th, 2008, 09:13 PM
On the PC that exhibited the problem with 3.0.621 I have office 2003 installed. The other PCs don't have Office installed and NOD32 3.0.621 has not caused any problems.
BeanCounter
February 15th, 2008, 09:03 PM
Has there been any progress with this issue?
jviper360
February 16th, 2008, 02:33 AM
No... I'm working around it by starting my scans manually, rather than using the scheduled scans... >:(
BeanCounter
February 28th, 2008, 03:37 PM
This issue appears to have been resolved by 3.0.642.

Does ESET publish a fix list anywhere for there releases?
ronjor
February 28th, 2008, 03:43 PM
{QUOTE-> Does ESET publish a fix list anywhere for there releases? <-QUOTE}Bookmark this (http://www.eset.com/joomla/index.php?option=com_content&task=view&id=4113&Itemid=9) page.
wibo
February 29th, 2008, 11:20 AM
Since I use version 3 of nod32 I have a daily freeze as well.
I can move my mouse but all windows are frozen, the start menu as well and all system icons.

What's happening?

(btw I have the 3.0.642.0 version)
BeanCounter
March 1st, 2008, 08:53 PM
{QUOTE-> Since I use version 3 of nod32 I have a daily freeze as well.
I can move my mouse but all windows are frozen, the start menu as well and all system icons.

What's happening?

(btw I have the 3.0.642.0 version) <-QUOTE}

That is curious.

I had the problem with 621 so I uninstalled it and went back to 2.7. After 642 was released I uninstalled 2.7 again and installed 642. Since then I have not experienced the problem. There is no mention of this issue in the release notes for 642 [see link above].