Slow NOD32 Beta Startup

When i startup my computer, it shows the NOD32 Splash screen. But it shows the splash screen for about 40 seconds and thats kind of slow for me. I can see that while its just staying there, it doesnt say the version of virus defs. that are installed. It will only say that at the end of the splash screen. I am wondering if this is a bug, or if it is just my computer acting up.
Info.
NOD32 Version: Beta 2.5.9
OS: Windows XP Home w/ sp1a
Is there any other info you need?

PS:The slow startup of NOD32 also causes other things to start up slow because they start up after NOD32 and its kind of annoying.

 

I want the splash screen, i just want to know if this is a bug, or if it is my computer.

 

Nope, only NOD32 Beta.

 

Can you please try a "Repair" as per screenshot found in this thread.

Hope this helps...

Let us know how you go.

Cheers

 

Tried the repair and didnt help. Nope, no previous AV.

 

Can you please try a Winsock Repair as discussed in post number 2 here. There are 2 methods mentioned, a software one and a manual method, I actually prefer the manual method.

Let us know how you go...

Cheers

 

That patch only made it worse. Now NOD32 starts up even slower than before, taking at least 2 minutes to start up.

 

There is NO patch, it is a manual fix of the LSP chain:


Step 1. Delete the corrupted registry keys

1. Click Start, and then click Run.

2. In the Open box, type regedit, and then click OK.

3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

4. When you are prompted to confirm the deletion, click Yes.

NOTE: Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.



Step 2. Install TCP/IP

1. Right-click the network connection, and then click Properties.

2. Click Install.

3. Click Protocol, and then click Add.

4. Click Have Disk.

5. Type C:\Windows\inf, and then click OK.

6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

7. Restart the computer.


Each and every step needs to be followed precisely.

Let us know how you go...

Cheers

 

NOD32 is still starting up slow. Im going to turn the splash screen off and then see what happens.

 

Please download a FRESH copy of the Beta from www.nod32.com

Uninstall your current version.

Remove the Eset Folder from C Drive> Program Files.

Install the FRESH copy that you downloaded above.

Let us know how you go…

Cheers

 

Turning off the splash screen doesnt help anything. I can see that the taskbar icon shows up at the same time with the splash screen.

 

Doing a clean install doesnt help. The problem still comes back. Could it be a bug that i found? It might be.

 

What previous Anti-virus did you use?

 

After i tried that Manual LSP fix, nothing would run on my computer when i would boot up. I tried running Firefox, everything i could think of and the computer just sat their for like 10 minutes without doing anything. I did a system restore and everything works, including NOD32. No more slow start up. Thanks for your help. I have no other AV on my computer and no previous AV, just older versions of NOD32 as i upgraded.

 

I still think it had something to do with the LSP chain, have seen this before, sometimes you have to go through the manual fix twice, making sure you do both parts, and reboot after each.

Good to see it is fixed, and thanks for keeping us posted as to your results...

Cheers

 

I had the same problem as Snake using NOD32 v 2.12. I used a program called LSPfix (available at http://www.cexx.org/lspfix.htm) which repaired the chain and removed IMON.DLL. After a reboot I simply had to restart IMON.

This might be useful for others who experience this problem.

Cheers

 

The windows automatic distribute the IP address may cause the problem at startup.

 

Same problem here. I tryed your advice.
NOD32 needs 33 seconds now until its startet.
Normal?

 

Did you try Winsock Repair?

Cheers