long shutdown With V4 ?

with v3 no problem, but v4 need a long time to shutdown.

close outpost before shutdown, no problems. is outpost active, the shutdown needs till to 10min

 

I don't know how long it should take with programs active as I always close them prior to shut down.

 

so, new start no problem, after config NOD32 (realtime -> shutdown -> disable)

shutdown problems

 

In my experience long shutdown/bootup is caused by fragmented disk and/or registry or an incompatibility with a program. I suggest using both these tools in safe mode, below are some free options:

Hard Disk: http://www.kessels.com/Jkdefrag/
Registry: http://www.snapfiles.com/opinions/NTRegOpt/NTRegOpt.html

If the problem is still there, it may be a problem with outpost.

 

fragment disk .. no
problem from outpost.. no

without nod32 and with outpost shutdown is ok

 

Try adding the Outpost program folder to the NOD exclusions list.

 

Um, why do you bother posting here if you're not going to follow advice? Don't worry I won't bother.

 

hi..

sorry, i dont bother..

this was a new install of winXP, with new config from outpost.

at first i installed NOD32, then outpost. the first reboot was no problem, the second reboot still hang on the desktop picture for a few minutes, then the notice "windows shutdown" i wait a few minutes to, then reboot.

why is the problem only with V4 and not with V3
(outpost same config, how with V3)

btw. is the V2.7 sufficient?

and sorry for english.. it´s not the best

 

I had a similar problem with a previous version of Comodo and NOD32 V3.
If I installed NOD32 THEN Comodo the system was very slow.
If I installed the same versions, Comodo THEN NOD32, they both worked great.
Not sure if this will help in your case but may be worth a shot.

 

i´m back to V3.. now no problems

 

so, here are the answer from agnitum and now all ok

 

Thanks for getting back. I checked my Outpost settings for Winlogon and explorer and their settings are correct. I guess Auto Learn worked okay for me.