XP slower shutdown?

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)

 

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

 

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 ;;...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.

 

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!

 

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 .

 

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...

 

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.

 

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.

 

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

 

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

 

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.