Controlcenter not starting?

[duijv023]

Hi there

I've seen something weird.
On a New PC (intel D955XBK; RAID-1; P4-3,0; 1 GB RAM) we have installed NOD32 2.5. Works very fine.

After that we installed Winconnect (see also http://www.wilderssecurity.com/showthread.php?t=133527&highlight=winconnect )
After installing, the control center doesn't appear anymore although nod32kui.exe is running (was my first check).
Besides, SOMETIMES the splash screen didn't even disappear from the screen.
I did some eicar tests and everything NOD related is OK and functioning.
The computer is newly installed on new HD's so is considered clean, and was never connected to internet unless behind a NAT router or more

I did a simple workaround by putting a shortcut to nod32kui in startup folder, and that works fine and stable.
But of coarse this is not the right thing to solve this issue.

Any ideas would be fine

[pykko]

well, that's strange. A fresh install of NOD32 may solve the problem :)

[NOD32 user]

Since you say you are using Winconnect I guess that means you have installed onto a server OS and already have IMON disabled? If not, temporarily try with it disabled (grey icon) especially since this is the recomended configuration for a anyway, and see if that solves it.
Alternatively when I have seen this issue personally it has been because of the way windows tries to start everything at once, and to be more specific a conflict with network components. The easiest and most reliable fix for this issue I have found is to use something like 'Startup Delayer' from r2 Studios (http://www.r2.com.au/)to give each component a chance to start each in turn instead of all at once. With this it is actually possible your windows startup can be faster than it was before.

Cheers :)

[duijv023]

{QUOTE-> Since you say you are using Winconnect I guess that means you have installed onto a server OS and already have IMON disabled? If not, temporarily try with it disabled (grey icon) especially since this is the recomended configuration for a anyway, and see if that solves it.
Alternatively when I have seen this issue personally it has been because of the way windows tries to start everything at once, and to be more specific a conflict with network components. The easiest and most reliable fix for this issue I have found is to use something like 'Startup Delayer' from r2 Studios (http://www.r2.com.au/)to give each component a chance to start each in turn instead of all at once. With this it is actually possible your windows startup can be faster than it was before.

Cheers :) <-QUOTE}

Thanks for responding!
@ OS: no that is not W2k3 server, but just Windows XP PRO sp2. The beauty of WinConnect is, that it does not need W2k(3) server 8)
and therefor IMON is not disabeled (see the other thread i've launched some time ago)

@ startup: that is what I was thinking about indeed. After I changed a few things, and put the settings back because they did't change anything, the problem didn't occur anymore at that time. So timings may be critical here.
I've seen it in two different (but brand new) PC's. I will check that little program you mentioned next time I have to build the configuration again!

Greetings from a warm and sunny Holland

[NOD32 user]

{QUOTE-> Thanks for responding!
@ OS: no that is not W2k3 server, but just Windows XP PRO sp2. The beauty of WinConnect is, that it does not need W2k(3) server 8)
and therefor IMON is not disabeled (see the other thread i've launched some time ago)

@ startup: that is what I was thinking about indeed. After I changed a few things, and put the settings back because they did't change anything, the problem didn't occur anymore at that time. So timings may be critical here.
I've seen it in two different (but brand new) PC's. I will check that little program you mentioned next time I have to build the configuration again!

Greetings from a warm and sunny Holland <-QUOTE}Glad to hear it is working OK for you at the moment. Thanks for posting back to let us know :)

[NOD32 user]

Just be aware that with nothing in place to otherwise prevent it this issue may return at some point due to the nice boot optimisation feature of XP.

Cheers :)

[duijv023]

Yes of course. But for now I will keep things as they are.
This way, I will be able to see if the problems return with, or without reason, or not at all

Have a nice weekend!

[agoretsky]

Hello,

I am unsure of whether this will work because I do not have a similar configuration available to me right now, but you could try moving the NOD32 Control Center program (filename: NOD32KUI.EXE) from executing via the [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run] key into the %HOMEDRIVE%\Documents and Settings\All Users\Start Menu\Programs\Startup\ folder.

This may delay execution of the NOD32 Control Center by the operating system long enough so the problem no longer occurs on the computer.

Regards,

Aryeh Goretsky

[duijv023]

{QUOTE->

.........
I did a simple workaround by putting a shortcut to nod32kui in startup folder, and that works fine and stable.
But of coarse this is not the right thing to solve this issue.

<-QUOTE}

That is what I did indeed, but thanks for answering