I am experiencing delayed shutdowns immediately after upgrading to NIS 2011. Event Viewer indicates Event 1517 (Application or service was still using the registry during log off). Installed UPHClean, which returned shutdown time to normal and is telling me:
The following handles in user profile hive ... have been closed because they were preventing the profile from unloading successfully:
XP, SP3, 32-bit, no other real-time security, not happening with NIS 2010, online upgrade for balance of subscription. 75-90 second log off with NIS 2011 compared to 10-12 seconds with NIS 2010 or with UPHClean and NIS 2011.
I am experiencing delayed shutdowns immediately after upgrading to NIS 2011. Event Viewer indicates Event 1517 (Application or service was still using the registry during log off). Installed UPHClean, which returned shutdown time to normal and is telling me:
The following handles in user profile hive ... have been closed because they were preventing the profile from unloading successfully:
I have this problem too but for me it HASN'T gone away.
Shutdown with Norton 2010 was (I guess) 30 seconds to a minute, with 2011 it went up straight away to several minutes, the longest of which has been about 10 minutes.
No other real time security software operating. Windows XP sp3 32 bit. Upgrade was installed by Norton operative when I experienced a problem & used the live help function.
I have run two registry cleaners which I have used for ages, but these have made no difference to the shut down time. The problem occured IMMEDIATELY after installation of Norton 2011. It's driving me mad. The delay stops me leaving the house or going to bed while I'm waiting for it to happen! I've had Norton for years but to be honest I've already started looking at possible alternatives for when my subscription is up for renewal in a couple of months time. Is there a soloution to this?
I'm wondering if perhaps there is some sort of conflict between other programs and NIS.
Have you used msconfig before? With this you can do some testing, starting with only loading NIS related processes at startup (along with Windows of course) and see if the same problem occurs during shutdown.
If it works properly with only NIS loading at startup, then you can add one at a time back to the startup and determine if there is some sort of conflict.
This will help narrow the problem down.
If you are not familiar with msconfig, please see the following post for details on how to use it.