XP slower shutdown?

[Grendel]

This is on XP-Pro with a gig of memory. Prior to installing Nod32, shutdown took about 10 seconds. Since then (including the very day I installed it), shutdown is now 25-30 seconds. I made no other changes to the system, hardware or software, before noticing this.

It's not a deal breaker (yet, at least), but it's pesky.

The details:
1. The install of Nod32 went flawlessly.
2. I did not have the mail scanner or realtime protection running.
3. All the latest updates to Nod.

What I've done so far:
1. Unloading Nod via the system tray; no change.
2. Killing the startup process nod32kui.exe via TaskManager; no change.
3. Stopping the process from even starting, and it has the switch /WAITSERVICE on it; no change.

I know it could just be coincidence, i.e. this issue could have arisen if I'd never installed Nod. But before I start trying some general slow shutdown fixes, I want to be absolutely clear, one way or the other, about Nod.

(Other than this issue, I''m totally pleased with Nod)

TIA!

[MorrisAO]

I installed the new vers 2 a few days ago and am also getting a slow shutdown - indeed it took so long I thought it might have frozen but then did shutdown ok eventually. Took a full minute at least to do so. This has only been happening since the install of Nod32 Vers 2 - no problems with vers 1. Apart from this comparatively minor problem I've also noticed a small slowdown in the computer generally but I assume this probably may be to do with having hueristics turned on. Nevertheless vers 1 ran with hueristics on but was very fast and did not slow the machine at all. As for the change in GUI I'm impressed - very easy to get to any part of the program from 1 icon. Nice, and looks good too. I am running XP Home.

Morris

[Grendel]

Morris---

Thanks! Although I'm sorry you're having the issue even more than I am, I'm glad to know I'm not alone ;D .

I've done a few things since I posted. I tried disabling nod32kui.exe and that had no effect (btw, since I discovered Startup Control Panel, one great little program, I've stayed away from msconfig). I also nosed some general XP slowdown pages from the MS MVP crowd, and in a fit of insanity I tried one of their suggestions, to disable Event Logging. Not only did it have no effect, but the results...well, let's just say it took a few minutes in Safe Mode to get XP functioning again. I'm going to try your heuristics idea.

Pesky...let's see what others say...and the Eset people ;) .

%%robert AKA Grendel

[jan]

Hi,

let's see your sysinfo - NOD32 CC>NOD32 System Tools>Information

Pls. post it here (all having this issue).

Thx., :)

jan

[radicalb21]

Jan,
I just started noteing some slowdown in my system any ideas? Here is my system information.

NOD32 Antivirus System information
Virus signature database version:***1.444 (20030623)
Dated:***Monday, June 23, 2003
Virus signature database build:***3745

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***512 MB
Processor:***Intel(R) Pentium(R) 4 Mobile CPU 1.50GHz (1495 MHz)

[radicalb21]

If any other information is needed let me know and I'll supply it.

[Paul Wilders]

It's heading to 10:00 PM in Jan's time zone - most probably he has called it a day for now ;)

regards.

paul

[Grendel]

The plot thickens!

I think there's good reason to say IMON is involved. This morning I ignored its dire warning and disabled it. And presto, my shutdown speed returned to about 10 seconds.

So it seems the issue is this. Given what Imon does, should this shutdown slowdown be normal? After all, it's got a fair amount of hooks to unload. So what we really need to know is: is IMON as optimized as it can be in this regard, or can the programmers wave their magic wands a bit?

Jan -- it will be a little before I can post my system info -- I temporarily (only temporarily!) took NOD32 off to confirm the observation I started with. It'll be back.

%%robert /Grendel

[jan]

Hi Grendel,

>Jan -- it will be a little before I can post my system info -- I temporarily (only temporarily!) took NOD32 off to confirm the observation I started with. It'll be back.

OK - I'd like to see it.

Thx., :D

jan

[MorrisAO]

Hi Jan

Here is the Nod 32 System info:

NOD32 Antivirus System information
Virus signature database version:***1.444 (20030623)
Dated:***Monday, 23 June 2003
Virus signature database build:***3745

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***512 MB
Processor:***Intel(R) Pentium(R) 4 CPU 2.40GHz (1792 MHz)


Hope it's of help :)

Morris

[Antarctica]

I experience exactly the same slow down on shut down. It takes about 50 seconds now and before I install NOD32 it was 12 sec.


NOD32 Antivirus System information
Virus signature database version:***1.444 (20030623)
Dated:***23 juin, 2003
Virus signature database build:***3745

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***512 MB
Processor:***AMD Athlon(tm) XP 1800+ (1564 MHz)

[spy1]

I have the problem, too.

Not only is the shutdown slower, but about one time out of three I'll also get a window during shutdown that Windows is trying to end Imon - complete with a little progress bar (even if I let it try to do that - let the little bar complete and disappear - it then comes up with a message that the task still hasn't been ended and I wind up clicking the "End Now" (or whatever it says) button.

NOD32 Antivirus System information
Virus signature database version:***1.444 (20030623)
Dated:***Monday, June 23, 2003
Virus signature database build:***3745

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***768 MB
Processor:***AMD Athlon(tm) Processor (1325 MHz)

It's irritating, to say the least. Pete

[Antarctica]

Hi all,

I don't know if it is related or not but I just fix my shutdown problem. That's what I did.
I first run Hijackthis and I found out from the log that I had a problem with "Winsock-Imon.dll missing"

Then I run the utility call Winsockfix, reboot and now instead of taking 50 seconds to shutdown, it takes just 14 secconds which is almost like it was before! ;) :)

[StAnger]

I don´t know if that was a smart move. Imon.dll is always listed as missing by HijackThis.
http://www.wilderssecurity.com/showthread.php?t=9811

[Antarctica]

Thank you for the thread StAnger. Well so far I don't have problem with my PC and the shutdown time it still 14 seconds.

Wait and see, nothing else I can do. :-\ :)

[jan]

Hi,

is anyone here having NOD with XP and shutdown not delayed?

Thanks, :)

jan

[dave s]

No change in shutdown times here...still averaging 28 seconds.

Dave

NOD32 Antivirus System information
Virus signature database version:***1.446 (20030626)
Dated:***Thursday, June 26, 2003
Virus signature database build:***3749

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***512 MB
Processor:***x86 Family 6 Model 8 Stepping 6 (863 MHz)

[asdf]

Xp Pro with latest updates, 256 ram, 1.1 gig processor and shutdown of 35 seconds.
Much the same as always. :)

[linney]

No Shutdown problems here either.

NOD32 Antivirus System information
Virus signature database version:***1.446 (20030626)
Dated:***Thursday, 26 June 2003
Virus signature database build:***3749

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***511 MB
Processor:***x86 Family 6 Model 8 Stepping 3 (564 MHz)

[controler]

I think back in April Microsoft released a tool for startup shutdown problems.

I think this link is still good.

http://www.microsoft.com/whdc/hwdev/platform/performance/fastboot/BootVis.mspx

con

[Antarctica]

Controler,

I have Bootvis install. And what is strange is before I had NOD32 installed, my shutdown time was 13 seconds.Now it is about
45 seconds.
And Ididn'd had this problem with the Version 1 :(

[StAnger]

I may be totally wrong here, but at the off chance that I am on to something. Mine is no slower then before, but it has also been slow in shutting down.
Main reason because I have the pagefile cleared at shutdown.
What I noticed is that for those where it was always slow there is no extra time added, but for those that had a quick shutdown, there has been an impressive change. Am I right?
Does NOD try to scan the pagefile at shutdown?

[Antarctica]

-{ Quote: " quoting: StAnger link=board=39;threadid=10605;start=15#msg70119 date=1056804307]

Does NOD try to scan the pagefile at shutdown?
" }-

Good point StAnger. Let's wait if someone from Eset can confirm this

[Grendel]

'Whiles back, Jan asked me for my system information. I've been a bit delayed...but that's no excuse, since I started this thread :) .

Have reinstalled; same slower shutdown times I previously reported, same "cure".

(Jan -- I know you're away for a bit). So without further ado:

NOD32 Antivirus System information
Virus signature database version:***1.449 (20030630)
Dated:***Monday, June 30, 2003
Virus signature database build:***3757

Information on other scanner support parts
Extended heuristic module version:***1.002 (20030606)
Extended heuristic module build:***1030
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600
Version of common control components:***5.82.2600
RAM:***1024 MB
Processor:***Intel(R) Pentium(R) 4 CPU 2.26GHz (2271 MHz)

[sig]

I just did a clean install of NOD 2 and am having exactly the same experience as Spy1 noted. I too get the notice that IMON is taking time to close, and it still won't as it says it's not responding and then I have to manually end the process via the info box before shutdown will proceed. Then the shutdown takes considerably longer than previously. ???

[sig]

Here's my system info also:

NOD32 Antivirus System information
Virus signature database version:***1.453 (20030704)
Dated:***Friday, July 04, 2003
Virus signature database build:***3766

Information on other scanner support parts
Extended heuristic module version:***1.003 (20030703)
Extended heuristic module build:***1031
Archive support module version:***1.001 (20030526)
Archive support module build version:***1032

Information on installed components
NOD32 For Windows NT/2000/XP - base
Version:***2.000.2
NOD32 For Windows NT/2000/XP - Internet support
Version:***2.000.2
NOD32 for Windows NT/2000/XP - standard component
Version:***2.000.2

Operating system information
Platform:***Windows XP
Version:***5.1.2600 Service Pack 1
Version of common control components:***5.82.2800
RAM:***512 MB
Processor:Intel(R) Pentium(R) 4 CPU 2.00GHz (2019 MHz)

[spy1]

sig - I used the "Repair now" button and followed that up with a run of NTREGOPT ( http://home.t-online.de/home/lars.hederer/erunt ) and I haven't seen that particular problem again for awhile (the IMON hang, that is).

Give it a try. Pete

[balbanebeoulve]

Err...well mine does shut down slower but I know why...Maybe it's a different reason but NOD32 is set-up to scan your boot-sectors on shutdown, well that's how it is on my computer o.O;;...Err try this and see if it works:

1. Open NOD32
2. Go to AMON
3. Click Setup
4. Under the tab detection look under "Scan Boot Sectors on" and see if shutdown is checked ;) If it is, you know NOD32 is just doing its job and saving you from a virus that activates on startup, hehe.

Let me know how it goes.

Regards,
-BB.

[sig]

OK, Pete, I tried out your suggestion and so far at least it seems to have stopped the IMON hang. Yay! So thanks very much for the tip! :)

I still have the longer shutdown although I previously had unchecked the boot sector scan at shutdown. That still didn't seem to make much of a difference.

But it's great to have gotten rid of the IMON hang, that added a loooong time to the shut down process. Whooee! ;D

[Grendel]

Good idea, BB!

Tried it, no difference, alas.

As I look over this thread, what's puzzling (to me) is that some solutions work for some, others for others...and some not at all. This may be saying something, but I'm not sure what :) .

[Antarctica]

Hello Grendel,
I think this will answer part of your questionning.

The solution that had solved my problem (repair the Winsock-imon.dll missing) with HijackThis was only temporary. In fact it creates another problem with Imon.

I had to use the tool WinsockFix afterwards to get Imon working
again.

So now everything is working fine on my P.C but my shutdown time is back to 45 seconds again...

[sig]

Dang! I knew I cursed it by speaking about it. The IMON hang is back, not quite as bad as before evidently, so far at least. "Not quite as bad" means I apparently can end the program in one attempt rather than taking two or three tries before it will actually shut down and let the OS' shut down process proceed. We'll see if that continues to hold true or not.

(Oh and previously I did try actually closing IMON before hitting the XP shut down button and even that didn't work. I would still get the "IMON is attempting to close" and "IMON is not responding" messages. So obviously something [presumably a service?] is still running even if one has closed IMON previous to commencing lthe XP shut down.)

This is rather irksome.

[ronjor]

I sent a note to Eset about the slow shutdown on XP. Had a timely reply. However, it doesn't cure the problem.
I just purchased a license for one year, but, I have removed the program from my computer until the problem is solved.
Nod32 is by far the best running antivirus out there. We need this shutdown problem fixed---please. >:(

[Grendel]

I take sort of a proprietary interest in this thread, since I started it :).

Antartica -- thanks for the further points!

Its seems my problem isn't isolated...but we obviously have no way of knowing how many out of the population of users are having, or not having, the issue. Still, it would seem that we've got enough of a critical mass that our issue could go into the development team's to-do list. Perhaps it already has.

In larger perspective. This is the only glitch I've encountered in a superior program. And I've been through a number of AV programs (naming no names, no dissing!) whose problems were enormous in comparison. So for me, thus far, this slow shutdown isn't a deal-breaker. OTOH, I've not lived with it all that long either, so time will tell!

Of course, as I read the forum posts, others' problems could understandably be consuming more of the developers' energies. All the same, here's hoping that one of them will let us know where this issue -- admittedly not a deal-breaker for most of us -- stands in their to-do list.

[MorrisAO]

I've been watching this thread with interest since Grendel began it (and my own post soon after). As Grendel states the same applies for me. Apart for the slower shutdown time this program works perfectly for me - I like programs that just quietly go about their business in the background without me having to worry what's happening. In short, set & forget - apart from the ocassional checking to see that updates are continuing without problems. The only other very minor quibble is losing the right-click context option. But that is no big deal either as far as I'm concerned. The important thing is that it does what's claimed, and it certainly does that in spades. It has already caught a couple of non-dangerous viruses that were sitting in files in my archives that my previous AV (supposedly a good one) had missed. So ESET has got a winner here IMHO. ;)

Morris

[Thorz]

Hello m8s.
I have had also problems with slow shut down caused by IMON. I have just found this thread. Are you still having issues about this? There is some people that has posted in this other thread with the same problem. Take a look here if you like to give us a hand. TIA.

http://www.wilderssecurity.com/showthread.php?t=19799;start=0

[MorrisAO]

I had a look at the link posted by Thorz (thanks Thorz) and decided to remove that M$ Hotfix 811493. It worked - problem fixed. Thanks.

Morris

[Thorz]

-{ Quote: " quoting: Morris link=board=39;threadid=10605;start=30#msg123961 date=1075078034]
I had a look at the link posted by Thorz (thanks Thorz) and decided to remove that M$ Hotfix 811493. It worked - problem fixed. Thanks.

Morris
" }-

Glad you fixed your problem. I have even tested in a totally clean machine (without any update or driver even) and the shut down problem was still present. It appears that the problem is only been presented by some people here. I have tested in 2 very different machines with the same results.

[Paul Wilders]

Gents,

In order to avoid confusion, I suggest this slow shutdown issue will be addressed in just one thread - the other one (see link above). ;)

Thanks in advance,

paul