This is completely anecdotal (my own experience today) so it might not be relevant to anyone else's PC, but just in case it might be useful to someone else, I'll post it anyway.
With both Norton Internet Security 2009 and also the previous version (NIS 2007), I used to always and consistently get Norton's "ccSvcHst.exe" window when shutting off or restarting the PC, and the ccSvcHst.exe window took some time doing its thing before it would go away (on its own - so far there was only one time it froze up) and normal Windows shutdown would resume. I used to always wonder why that window even showed up in the first place, and why it made me wait until it finished whatever it was doing.
However, earlier today I upgraded the RAM from a measly 256 MB RAM (totally RAM-starved, poor thing) to a much nicer amount: 2 GB RAM, and then I disabled Virtual Memory (figured I wouldn't be needing VM anymore). Besides all the usual expected benefits of having plenty of RAM (plenty for XP, anyway), I noticed that the PC's shutdown procedure also occurs much more quickly now, including that Norton's ccSvcHst.exe window doesn't appear at shutdown anymore - it doesn't show up at all now, not even for an instant.
I made no other changes to the system/apps/prefs/etc., so I can only conclude that the disappearance of "ccSvcHst.exe"-at-shutdown must be because of the extra RAM and/or disabling Virtual Memory. (I didn't think to try this earlier and I'm not sufficiently motivated right now to try turning VM back on to see if ccSvcHst.exe reappears at shutdown - hopefully it will be at least another week before I have to reboot to have occasion to test the VM-on thing.)
(Yeah I know, it's kind of a trivial thing since, at least in my case, the ccSvcHst.exe was merely a nuisance and it wasn't ordinarily causing any problems for me other than the extra time waiting for it to finish up, but it's nice that it doesn't show up at all now... an unexpected benefit of adding more RAM.)
-------
Windows XP Pro, SP2 Norton Internet Security 2009, version 16.2.0.7 P4 2.4 GHz Dell Optiplex GX260, now with 2 GB RAM (I'd have upgraded the memory long ago but I didn't realize RAM prices were so cheap nowadays)
Incidental note: All other aspects of NIS 2009 worked fine (super-fast, compared to NIS 2007) even with only 256 MB RAM.
I can make any pc shutdown very quickly regardless of RAM. There are a few registry settings to change.
Step 1
Open regedit and goto 'HKEY_CURRENT_USER\Control Panel\Desktop\'
Select the "WaitToKillAppTimeout" value.
Change it to "1000?.
Next select the "HungAppTimeout" valu.
Change it to "1000? also.
Step 2
Open regedit and goto "HKEY_USERS\.DEFAULT\ControlPanel\Desktop"
Select the "WaitToKillAppTimeout" value. Changet it to "1000?. Next Select the "HungAppTimeout" value. Change it to "1000? also.
Step 3
Open regedit and goto "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\"
Select the value "WaitToKillServiceTimeout"
Change this value to "1000."
Thanks for the info - I will try that sometime when I'm feeling adventurous. I haven't yet tried any regedit stuff, having heard all the dire warnings about it; although finally a few months ago I finally worked up enough nerve to do my very first command-line thingie (at least I think that's what it's called, hope I'm using that term correctly, anyway it's the Start,Run thing) and I poked around in "gpedit.msc" and "services.msc" and changed some stuff (the gpedit thing was motivated by my desire to entirely disable cd autorun, for security reasons) and I figured while I was at it, I might as well see what else was in there too. Reading everything carefully, of course, before changing anything. Lots of neat stuff in there.
I like your regedit info because it gives me a valid excuse to finally try regedit, which I've been curious about for a long time, but lacking an actual reason to mess with it, I hadn't got around to trying it. So now I have a reason to play with it.
Yes, of course, I have good backups - in the past I've inadvertently trashed my system so many times due to my own errors and my mistakes in judgment (like, deleting things that I shouldn't have - oops, guess Windows needed those files after all - darn), that I've gotten pretty good at formatting and reinstalling. That was before someone clued me in to the Windows "repair" thing, but even so, repair isn't necessarily always able to rescue me from my errors (depending on exactly what I've done), and Restore Points don't necessarily always work right either, for some of the grievious boo-boos I've made. (And formatting/reinstalling is usually faster than troubleshooting anyway, at least for me.) So as a result of that I make sure I have good backups before I play with any of the Windows settings.
malwareman wrote: Your better off keeping virtual memory on.
Hmm... looks like you might be right... I had assumed, apparently incorrectly, that Windows XP was like my ancient Macs, where if you have boatloads of RAM you don't need VM anymore, especially for running stuff like audio-editing apps where VM is a liability (I understand that newer Macs are different, but I have no personal experience with newer ones - my 'newest' Mac is from the pre OS X, and pre-OS 9, eras).
However, about Windows, after reading your post, I did a Google search using the search string: "virtual memory", "lots of ram" and the first few Google hits I've read seem to agree with you. Some of the other hits, disagree - one of the websites I found mentioned about XP (that's what I'm running on this PC here) and virtual memory, which makes me inclined to go ahead and leave it turned off.
I think what I'll do, is just push my luck and leave VM off for a while, see how it goes... This PC isn't running any memory-intensive stuff like Photoshop etc (I do all that stuff on the ancient Mac), but if I start getting weird problems on this PC then I'll follow your advice to turn VM back on again.
Anyway I appreciate your warning, because if I do start having problems, I'll know the first thing to try, would be to turn VM back on, because that's not something I would ever have thought of (I didn't know it could cause problems, having it turned off). So that could conceivably save me from many hours of futile troubleshooting etc. So, thanks again
(my own experience today) so it might not be relevant to anyone else's PC, but just in case it might be useful to someone else, I'll post it anyway.
poor thing) to a much nicer amount: 2 GB RAM, 
and then I disabled Virtual Memory (figured I wouldn't be needing VM anymore). Besides all the usual expected benefits of having plenty of RAM (plenty for XP, anyway), I noticed that the PC's shutdown procedure also occurs much more quickly now, including that Norton's ccSvcHst.exe window doesn't appear at shutdown anymore - it doesn't show up at all now, not even for an instant. 
to finally try regedit, which I've been curious about for a long time, but lacking an actual reason to mess with it, I hadn't got around to trying it. So now I have a reason to play with it.