![]() |
|
#1
|
|||
|
|||
|
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.
|
|
#2
|
|||
|
|||
|
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? |
|
#3
|
|||
|
|||
|
I do have MS office 2007 installed.
Why? |
|
#4
|
|||
|
|||
|
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.
|
|
#5
|
|||
|
|||
|
Has there been any progress with this issue?
|
|
#6
|
|||
|
|||
|
No... I'm working around it by starting my scans manually, rather than using the scheduled scans...
![]() |
|
#7
|
|||
|
|||
|
This issue appears to have been resolved by 3.0.642.
Does ESET publish a fix list anywhere for there releases? |
|
#9
|
|||
|
|||
|
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) Last edited by wibo : February 29th, 2008 at 11:25 AM. |
|
#10
|
|||
|
|||
|
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]. |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|