NOD32 extremely slow on startup

[ja5983]

Hey guys

I am running a Dual core 3.8Ghz pentium D, 2GB ram, etc etc.

When I boot up, the entire system boots up fine but NOD32 takes nearly 3 minutes to start. All the text in the splash screen shows up except on the bottom right hand side. that text doesnt show until it is fully finished starting up. I love NOD32 but this is getting to be a real hassle. I have tried the following:

remove and reinstall NOD32
IMON repair
LSP repair
winsock fix

none have helped at all.

I have had no previous antivirus on this machine.

HELPP!!!!

[YeOldeStonecat]

What type of internet connection do you have? And how are you connected to it?
Do you have multiple network adapters? If yes...if one is not used..is it disabled?

[ASpace]

This seems to be a compatiability issue .
Do the following:

(1)Goto Start-> (All) Programs -> Accessories -> System Tools -> System Information . This will make Windows show all your system info . Now File-> Save and save this on your Desktop , for example .

(2) Download HiJackThis from here (www.tomcoyote.org/hjt)
Run it with Scan button only . Save a log file
DO NOT REMOVE ANYTHING ON YOUR OWN

Now , write an email to the ESET NOD32 TechSupport
support@eset.us USA
support@eset.sk Europe
with an manual explanation of the problem , details and system-info files (1) and log file(2)


Good luck !

[ja5983]

I have a wifi connection and ethernet. ethernet is rarely used and is not disabled.

I dont think this is a compatability problem as it didnt work even when i first installed it on a fresh OS install....

[ASpace]

Let me comment what you said .

{QUOTE-> I have a wifi connection and ethernet. ethernet is rarely used and is not disabled. <-QUOTE}

Although I have never seen this , if your connection is ON and something tries to go to the internet and something is blocking it , and NOD32 is scanning it , this can make a problem . Moreover if your NOD32 is set to check for updates on every user log on and your connection is not stopped but active , NOD32 will try to update . You may have a firewall blocking it not because you have set it so but because it is slow and it loads later .
That's why I suggest you send the Tech Support guys these log files so that they see what you have loaded and things like that and help you .This is absolutely anonimous and nothing in it can identify you personally.

I guess YeOldeStonecat meant that you should try to turn OFF your connection and then see what is the result . In XP , goto Control Panel-> Network connections -> right click on all i-net connections and choose Disable. Restart and how is now ?


{QUOTE->
I dont think this is a compatability problem as it didnt work even when i first installed it on a fresh OS install.... <-QUOTE}
I think you don't understand what a compatiablity issue is ? This is ^incompatiablity^ or sutuation in which you see them on the stadium
NOD32 vs Software XYZ


As I said , the files that I suggest you send them will definitely help them understand a lot about your setup and it is anonimous. They can also ask you send them even more info by a diagnostic tool . So I think you can try what you were suggested , it won't hurt ;D

Good luck !

[alglove]

Go to Update --> Setup --> Advanced --> Internet Connection. If it is set to "LAN/fixed line", try changing it to "Dial-up".

It could be that NOD32 is trying to update itself through the disconnected ethernet connection, and this is responsible for the delay. By changing it to dial-up, this changes the update behavior, and the wifi connection acts more like a dialup connection, anyway. (At least is does for WinXP, this is supposed to change in Vista.)

[ja5983]

hi tech,

i have probably worked in IT longer than you have lived. i know what compatability is. i forgot to add that last windows install it worked fine.

{QUOTE-> Let me comment what you said .



Although I have never seen this , if your connection is ON and something tries to go to the internet and something is blocking it , and NOD32 is scanning it , this can make a problem . Moreover if your NOD32 is set to check for updates on every user log on and your connection is not stopped but active , NOD32 will try to update . You may have a firewall blocking it not because you have set it so but because it is slow and it loads later .
That's why I suggest you send the Tech Support guys these log files so that they see what you have loaded and things like that and help you .This is absolutely anonimous and nothing in it can identify you personally.

I guess YeOldeStonecat meant that you should try to turn OFF your connection and then see what is the result . In XP , goto Control Panel-> Network connections -> right click on all i-net connections and choose Disable. Restart and how is now ?



I think you don't understand what a compatiablity issue is ? This is ^incompatiablity^ or sutuation in which you see them on the stadium
NOD32 vs Software XYZ


As I said , the files that I suggest you send them will definitely help them understand a lot about your setup and it is anonimous. They can also ask you send them even more info by a diagnostic tool . So I think you can try what you were suggested , it won't hurt ;D

Good luck ! <-QUOTE}

[YeOldeStonecat]

Just for a little test....plug in your wired connection.....disable your wireless...reboot..and see what happens.

My "hunch" is...you have 2x things going on...one "unused" connection is not disabled...and your wireless connection is your primary. Wireless takes quite a bit longer to fully "load up". Even though you're looking at your desktop...takes a while for WZCSVC to fully fire up and get traffic flowing.

When you reboot each time..you'll see the NOD32 load screen as it checks the public update servers for updates...it'll sit there for a bit until it downloads them...or time out after a bit.(depending on which connection type you choose...dial up selection would nix this)

[ja5983]

my only question then is why do my other PCs not exhibit this problem and why did this PC only exhibit it after reload? I did try disabling wireless and disabling both connections and neither helped.

[YeOldeStonecat]

{QUOTE-> nd why did this PC only exhibit it after reload? <-QUOTE}

Define what your "reload" was. Guessing you are referring to a reinstall of Windows? On top of itself? Or was this a fresh reinstall? Did you just do a "quick format" or a full format prior to reinstalling Windows?

Appropriate chipset drivers, latest in all other drivers (Device Mangler isn't loaded with yellow ? marks) service pack 2 and all windows udpates?

[Blackspear]

{QUOTE-> Go to Update --> Setup --> Advanced --> Internet Connection. If it is set to "LAN/fixed line", try changing it to "Dial-up".

It could be that NOD32 is trying to update itself through the disconnected ethernet connection, and this is responsible for the delay. By changing it to dial-up, this changes the update behavior, and the wifi connection acts more like a dialup connection, anyway. (At least is does for WinXP, this is supposed to change in Vista.) <-QUOTE}I'll 2nd this advice.

Cheers ;D

[ja5983]

dial up and disabling unused network connections did not fix.

[YeOldeStonecat]

See my question 3 posts up. ^^^ ;D

[ja5983]

full reformat - over an hour of waiting for the format to finish since i have a 1TB raid...all drivers are from the MFG website, newest non beta drivers.

[NOD32 user]

Your issue sounds like a issue with the startup of network drivers as others have hinted towards and as has been seen occasionally in the past.

What OS are you running there? I'm guessing if it's a server OS then you have IMON totally disabled (grey icon and reboot) right?

I'm very inclined to agree with anything Blackspear suggests. Ordinarily for WiFi links I personally use the 'Other eg. portable' setting in the update advanced settings - same as if the link is via VPN that does not 'dial in' via windows DUN...

If the above offer no improvement, I would be interested to know what the result of using something like 'Startup Delayer' from r2 Studios (http://www.r2.com.au/) to space the starting of your WiFi from NOD32. My suggestion would be to have NOD32 start first and your WiFi as late as necessary to enable NOD32 to fully start before your PC even looks at the WiFi startup and with only applications dependant on the WiFi (often there's none) starting after it. Other network utilities can also interfere greatly at startup. HTH.

Cheers :)

[ja5983]

It is XP pro, i have IMON enabled but have tried with it disabled and had the same issue.

I have tried with wifi disabled and it hasnt helped at all. also changed the update pattern.

The other thing is, I have 3 other computers, all on wifi, running NOD32 and none have the same issue.

[NOD32 user]

{QUOTE-> It is XP pro, i have IMON enabled but have tried with it disabled and had the same issue.

I have tried with wifi disabled and it hasnt helped at all. also changed the update pattern.

The other thing is, I have 3 other computers, all on wifi, running NOD32 and none have the same issue. <-QUOTE}Ok.

Other 3 computers on the same WiFi hardware and drivers?

Also Windows is known to make it's own deciscions about startup order as it sees fit via boot optimisation 'feature' (and change it periodically) so there's really nothing to say that the same install process will result in the same startup order.
Ruling out hardware issues as highly unlikely it really leaves just 2 things - drivers and applications. Given what you've already tried, I would really recommend trying Startup Delayer - just take a stroll through it's inbuilt help for direction where needed.
You can do a basic configuration just to set the order you want (remembering the suggested order above) without worrying too much about the time each item is given. Then sort the list by time and hit 'Space Evenly' from the advanced menu. Usually 2 to 4 seconds is more than ample but for the purpose of getting your issue sorted please try going with even as much as 8 or 10 seconds initially. This can be reduced later if it's successfull in getting NOD32 up and running.

If you find in trying it that you don't get any change in your NOD32 startup I'd be glad if you'd post us a screenshot of your Startup Delayer config to help get a better idea of what may be going on.

If others disagree I'd be glad to hear their thoughts...

Cheers :)

[ja5983]

one is on the same wifi hardware and driver, the other are on different.

im gonna give startup delayer a try. see if that fixes it right now.

[ja5983]

if anything, that slowed it down. i set the wifi to a 15 second delay and nod32 to immediate startup.

[NOD32 user]

{QUOTE-> if anything, that slowed it down. i set the wifi to a 15 second delay and nod32 to immediate startup. <-QUOTE}and everything else spaced nicely as well? Since the Wifi is the most likely thing mentioned so far, but it could be most anything running at startup.
Otherwise try it the other way around - WiFi first and NOD32 Control Center late enough that the Wifi would have enough time to entirely start before NOD32 (not having the Control Center running does not impact immediately upon protection).
What we're trying to do is not just space the WiFi and NOD32 startup but find out if anything at all is causing a startup battle by spacing everything... ?

Cheers :)

[ja5983]

everything else is spaced out at about 4 seconds. ill try setting wifi first.

[pc-support]

What other programs do you have automatically starting up?

[ASpace]

{QUOTE-> What other programs do you have automatically starting up? <-QUOTE}

Well , guys , I have asked the OP to send HJT log and System info file to the TechSupport so that they will understand what he has auto-starting .

[ja5983]

i sent them system info, belarc, and HJT. they have so far been pretty much telling me to do exactly what you guys already said..just a few steps behind

my startup items are:
AIM95
CFTMON
PrevxOne
Startup Delayer
CCleaner
Nod32
Nvidia nTune
DeadAIM
Nvidia Control panel
sound manager
smart wizard for netgear wireless
spyware doctor
diskkeeper systray

[pc-support]

Try the following:

Disable half of the autostart programs (apart from the wireless)

if NOD still starts up slowly then enable those disabled and diasable the half that was enable (apart from the wireless).

If NOD still starts up slowly then diasble them all (apart from NOD and wireless) and see what happens.

Are you using windows to manage your wireless connection or the netgear software? Try using Windows for it.

Let us know how you get on

[pcaca]

Maybe Bootvis can give some light on the booting process. With help of Bootvis we can identify the application which is causing the startup slowdowns. Trace your booting process with Bootvis and you will see how much time is consumed by every process during the startup. Don't touch anything until the logging process has finished.
More info at Microsoft (http://www.microsoft.com/whdc/system/sysperf/fastboot/bootvis.mspx) and download here (http://www.majorgeeks.com/download.php?det=664)

[ja5983]

startup items isnt gonna help since this has been happening since windows and nod were the only things installed...im gonna try bootvis

[Blackspear]

Hi ja5983, could you please take a look at post number 25 and comment as to the suggestions.

Cheers ;D

[Cat-21]

Just to add, I also have the problem on select computers as well. I'm not sure what occurs but the end result is that NOD32 takes about 1 minute for the Tray Icon to appear and for NOD32 to start. There are no software conflicts and I have done all of the above fixes before (Reinstall, LSP, Settings changes, etc.)

If anyone figures this one out let me know. I even reinstalled previous versions with the same outcome so it's not the build or version that at issue. My guess is that one of NOD32's processes can become easily corrupted under day-to-day usage.

[Blackspear]

{QUOTE-> ...My guess is that one of NOD32's processes can become easily corrupted under day-to-day usage. <-QUOTE}I would disagree with you on this guess, from experience over a great deal of installs I would suggest that it is a software conflict, as to what software I couldn’t tell you…

Cheers ;D

[Cat-21]

Some more details about the slowdown:

1. I have found removing imon.dll from the LSP stack does speed things up a little bit but not enough to warrant this to be done.
2. I have always noticed that NOD32 has always waited on the splash screen for about 15-30 seconds on your first startup of the day. Once the build and definition info displays in the splash area NOD32 starts no problem. This time around the holdup is a little longer, sometimes about a minute.
3. NOD is about 5 seconds to start on subsequent logoff and logon to different accounts, my problems only show themselves on a reboot or startup.

Some Guesses on what is holding things up:


-NOD32 Kernal Service that launches at startup

-NOD32 starts before my network card acquires an IP Address so maybe NOD32 needs to communicate over the internet\network before it can start. Since the network has not started, NOD32 waits for it's arrival making a slow startup. Funny part is I disabled all the startup scans and updating and still will pause on the splash screen regardless.


I love NOD32 and think it's a great product, we should all take a deep breath on this one as nothing is perfect, even NOD32. Other than that, I have no problems with NOD32 and love the program.

[Blackspear]

{QUOTE-> -NOD32 starts before my network card acquires an IP Address so maybe NOD32 needs to communicate over the internet\network before it can start. <-QUOTE}Do you have a wireless connection?

Cheers ;D

[Cat-21]

I don't have a wireless connection on this computer. I wish it were that simple. I see other users with the issue so maybe it can be cleared up in a future release. I repeat again, no problems otherwise. I can also add that it usually effects the first login after my initial boot. If I log in as another user the subsequent user doesn't have the issue and startup is quick. It basically must have something to do with one of more of these:

1. Windows Services not yet started that are needed by NOD32 to start so NOD waits for their startup.
2. Internet connection is not yet established. NOD32 gets held up waiting for viable connection.
3. Something that occurs on a computer's startup that doesn't occur on subsequent log-ins.

Hopefully sometime soon you guys will come up with a fix on this one as it is a minor annoyance to have a P4 3.4Ghz w/2 GB RAM to have a close to 2 minute startup time due to NOD32. Without the NOD32 delay I am ready to go in less than 10 seconds as I have a streamlined setup tweeked for speed. It makes me sick to see my friend with McAfee crapware starting up before my NOD32...............................

[Metalmurphy]

I would like to add that i'm having the same problem as well. I do have an wireless connection and an ADSL connection to the internet, already set NOD32 to use Dial-Up connection, and already tried disabling and enabling (even in the bios) the wireless connection but still same thing happens. Takes about 3 minutes to load. Gonna try using BootVis now

[Metalmurphy]

Well that didn't help. Bootvis shows up even before NOD32 finishes booting. :S


Any ideas what i should do?

[beenthereb4]

I believe that this problem may be linked to specific network cards and their drivers. For example, in the past I have associated this with Dlink gigabit cards. The latest drivers seem to have fixed it. YMMV (By the way, it usually results in an error in event viewer stating that nod32 kernel service hung on startup --- however eventually the service does restart itself -- thus the long delay)

[Metalmurphy]

But if i disabled the card (and even in the bios) then it should have worked :S yet it didnt

[Cat-21]

I think I found the cause everyone. If you check out the registry entry in HKLM\Run a startup reference exists for NOD32 called "nod32kui"

If you open the string to modify you'll notice this path:
"C:\Program Files\Eset\nod32kui.exe" /WAITSERVICE

Basically the /WAITSERVICE switch is what's holding up the loading of
NOD32's tray application as well as the NOD splash screen hanging on your desktop for ages. If you remove the /WAITSERVICE reference from your registry entry NOD is golden.................

Registry Path for nod32kui reference:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]

Try it............

[Tommy]

{QUOTE-> I think I found the cause everyone. If you check out the registry entry in HKLM\Run a startup reference exists for NOD32 called "nod32kui"

If you open the string to modify you'll notice this path:
"C:\Program Files\Eset\nod32kui.exe" /WAITSERVICE
<-QUOTE}

IMHO this parameter is necessary, because the GUI has to wait until the nodkrn32.exe service is loaded completly. If not, the start of the GUI will result in a error message that it can't connect with the kernel service.

So that could mean that the service itself has a slow startup.

[nameless]

I have the same sort of issue on my desktop, running NOD32 2.51.26. Sometimes, the NOD32 tray icon doesn't appear for some time after logon. I've never timed it, and I don't think it's a full 3-minute delay, but it's at least a minute or so.

Go in the Scheduler/Planner and disable every item there. Then see if the issue remains. This should be the first step in diagnosing this problem.

For me, I think the issue has to do with the scheduled scan of startup objects that occurs at logon. The problem may have to do with that, or with updating at user logon. Either way, disabling the schedules--temporarily--will tell you. To me, you shouldn't go screwing around with update settings if you don't know that it's a problem with the update process in the first place.

Also, check the event log. I have, many, many times seen the follow error message appear there:

{QUOTE-> The NOD32 Kernel Service service hung on starting. <-QUOTE}
I never bothered to ask Eset what would be the cause of this, but every shred of experience I have tells me that asking would be a complete waste of time (mainly due to the nature of the problem).

[Redduck]

I am having much the same issue and have tried all the suggestions made in this forum to no avail. I am experiencing the same slow startup issues, with my machine sometimes taking more than 5 minutes between logon and when it has returned control to the user. One additional thing that I have noticed is that during the entire time that I am waiting for the NOD32 splash screen to disappear, the hard drive is under constant activity. Is it possible that NOD is scanning all the files on the drive and that is what is causing the slowdown?

EDIT:
Some additional information. If I uninstall NOD32 the problem goes away completely, leading me to believe that the problem is entirely a product of NOD32. After re-install, the problem is back. Disabling all networking on the machine has no effect, so it does not appear to be a problem with an attempted update or network connection issue.

[Blackspear]

Hi Redduck, welcome to Wilders.

{QUOTE-> If I uninstall NOD32 the problem goes away completely, leading me to believe that the problem is entirely a product of NOD32. After re-install, the problem is back. Disabling all networking on the machine has no effect, so it does not appear to be a problem with an attempted update or network connection issue. <-QUOTE}What previous antivirus was installed on your system?

Cheers ;D

[Redduck]

{QUOTE->
What previous antivirus was installed on your system? <-QUOTE}

Thanks for the welcome, and I must say that on my other PC NOD is working great. On this machine there had not been a previous antivirus product, it is a fresh install of WinXP Pro. At this point though I have loaded SAV CE 10 since I needed *some* antivirus protection while I figured out the NOD issue. Any help would be greatly appreciated since I would much rather have NOD than SAV.

Thanks!

[nameless]

Yes, the problem really, truly can be due to NOD32, and not some other AM product, or the weather, or the alignment of the stars...

[Blackspear]

How about trying Process Explorer (http://www.sysinternals.com/) from Sysinternals to see if this sheds any light on what is going on.

Do you have a wireless connection?

Cheers ;D

[Blackspear]

{QUOTE-> Yes, the problem really, truly can be due to NOD32, and not some other AM product, or the weather, or the alignment of the stars... <-QUOTE}It's just having installed NOD32 on close to 1000 machines, I have never, and I mean NEVER seen this issue, so I'm wondering what is localized to that particular machine in order for this issue to occur.

Cheers ;D

[Redduck]

UPDATE:

Following Blackspear's request, I restored the system back to a clean install and loaded NOD32 again with the same results. The system will start to load, the NOD splash screen will appear and the hard drive will go to constant access (hard drive light constantly on with only split-second flashes of non-activity). After about 5 minutes the hard drive will stop access, the splash screen will go away and the system will be back to normal. I loaded Process Explorer and set it to load at startup and restarted the machine again. The results were the same with the extremely slow startup and hard drive activity, the Process Explorer would load after the hard drive activity stopped.

The problem is that once the hard drive activity starts, and this looks very much like a full scan, nothing else can be accessed, not Process Explorer, not Task Manager, nothing! This makes it very difficult to see what is accessing the hard drive. The thing that makes it appear that it is a NOD problem is that the problem starts when I load NOD and goes away when I uninstall it. The problem does not appear with other antivirus programs (tried SAV and KAV without the problem appearing).

Again, I would certainly like to resolve this problem, since I like using NOD on my other machine and it is working well, but I am starting to think that there may be no solution. Any help or direction in where else to look would be appreciated.

[alglove]

What happens if you disable AMON and then reboot?

Also, what about NOD32 System Tools --> Scheduler/Planner --> uncheck "System startup file check" at user logon?

These are troubleshooting tips, by the way, not final solutions.

[NOD32 user]

{QUOTE-> What happens if you disable AMON and then reboot?

Also, what about NOD32 System Tools --> Scheduler/Planner --> uncheck "System startup file check" at user logon?

These are troubleshooting tips, by the way, not final solutions. <-QUOTE}Nice tip, be interesting to see if that helps :thumb:

Blackspear has given you some very good advice to help you troubleshoot this. Please download and install Startup Delayer from r2 Studios (http://www.r2.com.au/software.php?page=2&show=startdelay) and then set process explorer to load first, at least a couple of seconds before any other thing and then hopefully you might be able to better see what is going on during startup.

Usually when I have seen this it is because the NOD32 Kernel is waiting for the network drivers or similar to load fully before it can start up. I also had a tip from a colleague earlier who suggested similarly.

Cheers :)

[Redduck]

{QUOTE-> Nice tip, be interesting to see if that helps :thumb:

Blackspear has given you some very good advice to help you troubleshoot this.
<-QUOTE}
I agree, it has been excellent advice, just not successful as of yet.

{QUOTE-> Please download and install Startup Delayer from r2 Studios (http://www.r2.com.au/software.php?page=2&show=startdelay) and then set process explorer to load first, at least a couple of seconds before any other thing and then hopefully you might be able to better see what is going on during startup. <-QUOTE}
Great idea! I will be downloading that now and seeing what I find.

{QUOTE->
Usually when I have seen this it is because the NOD32 Kernel is waiting for the network drivers or similar to load fully before it can start up. I also had a tip from a colleague earlier who suggested similarly.

Cheers :) <-QUOTE}
I has seen the previous suggestion about the network drivers, so I disabled all the network devices. The problem persisted, and the constant hard drive activity suggests, rather graphically, that the slowdown is in the disk subsystem, not networking, although I am sure it is a possibility.

Thanks for all the great ideas, I am off to do some more testing.

[Redduck]

OK, I think that I have found the conflict, although it will make me choose and compromise my security options. First, a rundown of the hardware involved.

The machine that I am working with is a Sony Vaio laptop, model VGN-SZ330P. The critical thing about this is the built in fingerprint scanner and the disk encryption chip and software associated with this laptop. The software in question is the MenuSW software which runs at startup as menusw.exe. If this software is running, and NOD32 is running, I experience the heavy disk access and slow boot. If I disable either software, the boot times return to normal. There must be some conflict between the two. Unfortunately, it means I either have to disable the encryption software, which I do not want to do, or I move to some other AV program other than NOD, which I also do not want to do.

I am sure that this is a rather specific case, but I still hate having to make this choice. Any advice out there?

[NOD32 user]

Now that you are aware, couldn't you use the tool from r2 Studio to configure your startup more efficiently? At least until you hear any better suggestions from others?

Cheers :)

[Redduck]

{QUOTE-> Now that you are aware, couldn't you use the tool from r2 Studio to configure your startup more efficiently? At least until you hear any better suggestions from others?

Cheers :) <-QUOTE}
I used the tool from r2 to make the discovery, and it was very helpful. Unfortunately the problem is not when the programs start, but simply that they are in conflict with each other. No matter where I move them in the startup sequence, or how long I delay their start times, the problems exhibits when one or the other of them starts. I believe that this leaves me with little choice other than to choose which one I want to remain. At this point, since there are other AV choices out there, but really no other options for the disk security, I will have to choose another AV program. I hope that someone at ESET is aware of this so they can find a fix.

[NOD32 user]

{QUOTE-> I used the tool from r2 to make the discovery, and it was very helpful. Unfortunately the problem is not when the programs start, but simply that they are in conflict with each other. No matter where I move them in the startup sequence, or how long I delay their start times, the problems exhibits when one or the other of them starts. I believe that this leaves me with little choice other than to choose which one I want to remain. At this point, since there are other AV choices out there, but really no other options for the disk security, I will have to choose another AV program. I hope that someone at ESET is aware of this so they can find a fix. <-QUOTE}Please send an email to support AT eset DOT com and include a link to this thread and as much information as you have available including your system specs, software versions and any other thing that may be helpful.
Also, please post back here and keep us in the loop if there is any progress so we can all learn some more.

Cheers :)

[agoretsky]

Hello,

If you move the command to launch the NOD32 Control Center (the "%ProgramFiles%\Eset\nod32kui.exe" /WAITSERVICE string value) out of the [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run] key and place it into a shortcut located in the %ALLUSERSPROFILE%\Start Menu\Programs\Startup\ directory does the problem still occur?

Regards,

Aryeh Goretsky

[Redduck]

{QUOTE-> Hello,

If you move the command to launch the NOD32 Control Center (the "%ProgramFiles%\Eset\nod32kui.exe" /WAITSERVICE string value) out of the [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run] key and place it into a shortcut located in the %ALLUSERSPROFILE%\Start Menu\Programs\Startup\ directory does the problem still occur?

Regards,

Aryeh Goretsky <-QUOTE}

OK, I uninstalled the other virus program I was using and reinstalled NOD32, removing the above mentioned line from the HKLM\...\Run section of the registry as mentioned above. I rebooted and the problem was back, still booting up extremely slow (>5 minutes to boot).

So I got to thinking about what encryption was running on the computer. On the Vaio laptops with the fingerprint scanner, Sony adds a feature called My Safe which is essentially a virtual drive that contains encrypted information that is unlocked by scanning the fingerprint. I had enabled that feature and set its size to 2GB. I wondered if that could be the problem, so I unloaded NOD again, rebooted, disabled the My Safe feature, rebooted, loaded NOD again, rebooted and Voila! The problem is gone. So, I have narrowed it down to this particular feature and NOD conflicting with each other. I am willing to live without the My Safe feature in order to run NOD, but if there is anything else I can do in order to have both of these I would be willing to try it.

I don't know how many others with these laptops are having this problem, but this seems to have eliminated the slow start up. Thanks for all the help everyone, and if anyone has any ideas on how to make these programs work together in harmony, or if someone at ESET needs a guinea pig for testing a potential fix I will be willing to help.

Ken

[Sonic999]

Sorry to reopen this discussion, but I'm having a similar problem.
I figured it had something to do with my network, because I knew that NOD32 ran just fine when I had no network settings... but when I installed it to a machine that shares internet with another pc over a hub, and is connected to the internet thru a cisco adsl modem, windows startup takes up to 1:46 to load on a PIV, 3.0Ghz, 768MB RAM. So what I did was, unplug my two network cables (one comes from the hub, into one of my NICs; the other one comes from the adsl modem -not wifi- and plugs to the motherboard's onboard ethernet port). What happened? Startup time went from 1:46 to 50sec total. Then I tried disconnecting the Home Network cable (the one that plugs to the extra Nic I installed in my machine), and leave just the modem connected to the usual ethernet port (the motherboard's)... time went again to 1:46. Next I tried leaving connected the Home Network cable, and disconnecting the modem's cable... time went to 50sec again.

So, my guess is that the problem's with the modem's local area connection or its driver loading... someone with more knowledge on networking stuff will be able to tell what it is.

I've just uninstalled NOD32 and the problem persists... it takes 1:46 to start (everything - except MSN - was started at 45sec, and I double clicked my inet connection to log in, but the screen only came up at 1:46, when MSN's window loaded as well, and you could tell that something "else" on the background had definitely finished loading).

My adsl connection is pppoe and I'm using raspppoe v0.98b (latest stable build), I've two local area connections:

1) Local Area Connection: Ethernet VIA PCI 10/100Mb (the one from the motherboard), which has the following:
- Client for MS Networks
- Share printers and files
- PPP over Ethernet Protocol
- TCP/IP (obtains IP automatically)
ALL BOXES CHECKED

2) Local Area Connection 2 (used for my home LAN) NIC Fast Ethernet PCI Family RTL8139 Realtek :
- Client for MS Networks
- Share printers and files
- PPP over Ethernet Protocol
- TCP/IP (192.168.0.1; 255.255.255.0)
ALL BOXES CHECKED

Nothing strange there. And when I "dial" my internet connection (it's not "always on", you have to use login and password after you double click the connection's shortcut on the desktop), I get a pop-up saying "Connecting to Wan Miniport" or somth like that. It's that Wan Miniport thingie what's causing everything... I think... cause it may be taking too long to start at Window's startup.

I didn't have to configure anything network related. I just installed the extra nic in my PC, set up the cable for the other pc and connected them... then assigned 192.168.0.1 to my PC and 0.2 to the other one. They see each other, they both connect to the internet... no problem whatsoever. After installing raspppoe, I just had to set up the internet connection, which was easy to do, and then share it thru local connection 2.

My internet connection's settings:
WAN Miniport (PPPOE) (this is what Windows tells you on the bottom left-hand side when you click once the connections icon), then right-clicking, properties:
the Network tab has the following:
Type of Broadband Connection: Point to Point Ethernet Protocol (PPPoE); LCP box checked, software compression box checked. The other box is unchecked.

- TCP/IP (checked)
- Share printers and files (unchecked)
- Client for microsoft networks (unchecked)

Not sure if the other guys who have this problem tried what I did. It seems it's just something network related.

I hope someone can shed some light on this issue.

Cheers.

@Sonic999

[alglove]

{QUOTE-> I've just uninstalled NOD32 and the problem persists... it takes 1:46 to start (everything - except MSN - was started at 45sec, and I double clicked my inet connection to log in, but the screen only came up at 1:46, when MSN's window loaded as well, and you could tell that something "else" on the background had definitely finished loading). <-QUOTE}
OK, so it may not be an NOD32 problem, but we will see what we can figure out.

{QUOTE-> My adsl connection is pppoe and I'm using raspppoe v0.98b (latest stable build), I've two local area connections:

1) Local Area Connection: Ethernet VIA PCI 10/100Mb (the one from the motherboard), which has the following:
- Client for MS Networks
- Share printers and files
- PPP over Ethernet Protocol
- TCP/IP (obtains IP automatically)
ALL BOXES CHECKED

2) Local Area Connection 2 (used for my home LAN) NIC Fast Ethernet PCI Family RTL8139 Realtek :
- Client for MS Networks
- Share printers and files
- PPP over Ethernet Protocol
- TCP/IP (192.168.0.1; 255.255.255.0)
ALL BOXES CHECKED <-QUOTE}
Try this configuration, as per http://www.windowsnetworking.com/articles_tutorials/adslpoe2.html .

1) Local Area Connection: Ethernet VIA PCI 10/100Mb (the one from the motherboard), which has the following:
- Client for MS Networks (no check)
- Share printers and files (no check)
- PPP over Ethernet Protocol (check)
- TCP/IP (obtains IP automatically) (no check)

2) Local Area Connection 2 (used for my home LAN) NIC Fast Ethernet PCI Family RTL8139 Realtek :
- Client for MS Networks (check)
- Share printers and files (check)
- PPP over Ethernet Protocol (no check)
- TCP/IP (192.168.0.1; 255.255.255.0) (check)


The reasoning behind this is that the "external" network card (1) is used only to establish a PPPoE connection through the external ADSL modem. It is used as an interface. All the "networking" info on that interface, like the TCP/IP addressing, is handled by the "Dialup WAN Miniport (PPPOE)" connection.

The LAN network card (2) handles all its "normal" networking directly. You can disable "PPP over Ethernet Protocol" for that network card, since it is not used to connect to the DSL modem.

[Sonic999]

You nailed it, alglove!! :thumb: ;D That solved the problem, at least in my case. I can now connect to the internet within 50sec, and NOD32's splash screen stays on for about 8sec, then it disappears and Msn's window pops up.

I owe you a beer ;D

@Sonic999

[alglove]

Mmmmm... beeeeeer... :P

Glad it all worked out, Sonic999. :)

[alex_nicoara90]

If this problem still occures, and you do not have ADSL connection, and u use internet PPoE or just LAN, i was using Onboard nvidia mcp network controller, that what's caused my Nod32 to startup slow, so i disabled it from System bios, and added a PCI Surecom EP320X-S1 Ethernet adapter, works excellent. So in conclusion the Onboard ethernet controller is the problem...

[ankupan]

any firewall on your computer ?

[scottls]

I am a home software tech, and install N32 exclusively on MANY computers (Sony Vaio laptops, too!)!
DELL 9150 desktop, 3.2ghz Pentium D, 4 gig memory, 10k rpm WD Raptor C HD (not raid- !fast/WOW!).
Windows XP (I HATE "slow/buggy..." Vista!). I refuse to work on a Vista computer!- Only after I install XP!

:o Pre-note- XP LOVES restarts!- NO process..., is FULLY completed (only flagged...!), until AFTER a restart!
Restart (never shutdown!) after EVERY install/uninstall/setting change... (wait a few seconds for your HD light to stop flashing...!- SLOW DOWN!)!
~~~
;D This is how I get then get FAST N32 startups (Yes I have a FAST computer, but this setup... works VERY GOOD on ALL my clients comuters!)!-

:thumb: - Run safe freeware CleanUp disk file cleaner utility (I disable their cookie cleanup)-
First run will safely delete THOUSANDS of old useless files...! (then restart "manually" ONLY!- "never" use their pgm restart/NO!)!
I only run CleanUp (daily), "AFTER" a fresh restart, and restart "manually" again immediately (slow down!)!

:thumb: 1. Install "fast" Diskeeper Pro Premier "10" ("NOT" 2007! :thumbd: ) disk defragmenter (read my Amazon.com review, for full install instructions!)!!!

Defragment HD & then optimize MFT (manually enter a MUCH smaller # than recommended!- about 20k more than is currently used, after full install), and then enable Ifaast.
Ifaast arranges the programs you use the most, at the front of the HD!
:thumb: Your computer will now be a 20-40% faster on ALL applications... (!TRUE!)!

2. On startup, "after" your logon icon appears!- Wait a few seconds (at least15) for your HD light to flash, before clicking!
N32, and ALL your startup programs will now load FAST!

3. Now I wait a few seconds for my freeware Comodo firewall icon to stop flashing (works good with N32!- & passes tests...!), before you compute...
N32 sometimes has ALLOT of firewall activity on startup (probably some kind of pre-checking?)?
ENJOY!
~~~
The only other AV program I use/recommend is a distant freeware Avira Avtivir (on my backup comuters only- no POP3...!).
:thumbd: Kaspersky AV (or freeware AOL!), is a REAL/slow resource hog...!- "NOT" recommended!
:thumbd: NEVER install AOL "anything" on your computer!- You'll be sorry (impossible to FULLY uninstall...!)!
~~~
:thumb: I also recommend Counterspy anti-spyware!
:-\ SpySweeper is good too, but their pgm updates are "!ALWAYS!" BUGGY (I wait until they "settle down...", to apply them!).
:thumbd: SpyWareDoctor 4.0 was good, but 5.0... has "permanent" BAD bugs!
~~~
:thumb: Before testing new critical... software!- I "first" do a full system image chkdsk/backup/validation, using Acronis True Image 9.0!- Full system restore(restart) in 2min.! Then I also run chkdsk (always follow chkdsk, with "2" restarts!- slow down!)),
Pre-disable internet, & don't enable until after chkdsk- You will probably have to do a "manual" N32 update, to get it going!