Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
With respect, I find the above confusing. The zombie workaround is not as you describe, the zombie workaround is to do with unregistering bushell.dll. Specifically type regsvr32 /u buShell.dll. If your thread subject excluded Zombie processes and all references to Zombie's, I would consider it nearly definative
The HungAppTimeout is interesting and has been referenced in another thread whilst explaining the 1st workaround. However, I have never heard anyone vary the HunAppTimeout, although I entirely see the reasoning.
The Waittokill, I have seen where a user reports that Symantec changed it to 10 secs.
I make the following further observations:
1. One user reports, that the application of the first fix did not fix the shutdown problem whilst the application of the third did. I cannot see the logic of how this could technically be the case.
2. I have not yet heard from any user that the application of the zombie workaround alone (without the application of the 1st fix) resolves the shutdown issue. I am awaiting someone to kindly check this.
Thanks cgoldman for you comments. I have modified the wording of the introduction in my thread.
>> 2. I have not yet heard from any user that the application of the zombie workaround alone (without the application of the 1st fix) resolves the shutdown issue.>>
I see here that you make reference to the zombie workaround, and the 1st fix, in the same instance. This is why I have mentioned the Zombie issue in the thread.
Replied to privately. The edited wording is much improved.
thanks Johna
very much appreciated. I will follow this suggestion when back in front of the troubelsome PC next saturday.
As an "innocent abroad" I'd be interested in comments on any downside to Item 3. I can see with 1 & 2 that if it's hung it's hung and those automate >Task Manager > End Process.
But what might be the downside of ending a service that has not yet shut itself down using its own procedure and yet is not hung? It still has something to do for an orderly shutdown.
There's a difference between going into Services and Disabling a Service or ending it through Task Manager in that you know what you have just done and if something complains you can reverse it -- you do only change one parameter at a time don't you? <g>
Over-riding the normal shutdown procedure could abort a number of services at the same time and be difficullt to troubleshoot.
"That's all I'm asking" ...
Usually I don't mind if Windows takes time to shut down because I hit WINKEY +U +U (in XP) or WINKEY +U +S +ENTER in VISTA and walk away. That shuts down my computer in its own sweet time and I come back later and turn off the UPS .....
It's a good point you raise, and one that has been discussed in many forums. To date, however, there has not been any case reported that I have seen of a corruption occurring due to the altering of this setting. In fact, some of the well known tune up applications are now adjusting this setting back to 5000 (5sec) as a way of an all round speed up process. As I stated, sometimes the adjusted setting will not stick, but there are ways around this as well.
For those who would like to leave the setting at the default 20000 (20sec), this step should be ignored.
Thanks for the clarification – reassuring.
Thanks, johna.
Applied all three fixes and appears to have solved my issues - the one that was bothering me most was Office apps not shutting down when I exited them.
Previously had seen fix #1 on the regular Norton website as solution to ccsvchst error at shutdown. Applied that fix and I was shutting down fine, but was still having problem with Office apps. Was particularly noticeable to me when using Outlook's backup feature, since the copy of the backup file won't start until Outlook's process is ended - had to end it manually every time.
Applied fixes #2 and #3 everything (for now) works like a charm.
Still wish I had returned 360 within my money-back window. Can't understand why Norton won't acknowledge the widespread nature of this Zombie process problem. It's like they got halfway there by acknowledging the ccsvchst issue, but clearly all this stuff is related.
Thanks Johna ! I was going nuts with this problem. Several zombie processes running for all my Office apps... Outlook telling me over and over again that the application was not properly shut down in my previous sesion and all kinds of headaches. My Shutdown time was also out of control: it could take 5 - 6 - 8 MINUTES !!!... Ridiculous.
I followed your three steps PLUS this one
and now I'm flying ! My shutdown time came down to 10-20 seconds and no more zombie processes !
Again, a million thanks !!!
Cheers
Hi Timmus
Great to hear it worked for you, and thanks for reporting back!
John
I just used this and it really made a difference in how fast or slow things were running.
I tried the first half first, and it made such a differnce that I just went and did the entire regisrty and I'm not regretting it.
Thanks!