speed up shutdown?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

i have been informed that i can speed up system shutdown by adjusting the
value of 'WaitToKillServiceTimeout' in the registry. is this correct and
where do i find this in the registry.
kind regards.
 
seanpaul99 said:
i have been informed that i can speed up system shutdown by adjusting
the value of 'WaitToKillServiceTimeout' in the registry. is this
correct and where do i find this in the registry.
Click to expand...

To expand on Ted's answer, adjusting this will only help if your problem is
with services closing down.

Adjusting it wrongly could cause the same sorts of problems for your
computer and your data that "adjusting a slow stopping time" on your car by
yanking on the handbrake and jumping out blindly while still going at 45mph
would cause for you. Your computer and your bones but in both cases I'd
either find out where the problem really is, or live with the current time.

--
--
Rob Moir, Microsoft MVP for Security
Blog Site - http://www.robertmoir.com
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
I'm always surprised at "professionals" who STILL have to be asked:
"Have you checked (event viewer / syslog)".
 
Wow I'm blown away by these nay sayers. Yes there certainly are modifications
you can make to certain keys in the registry that will greatly reduce your
shutdown times. The biggest culprit of long shut down times are applications
that are set to clear pagefile when XP shuts down. I've take computers that
shut down in 2 to 3 minutes and get them to shut down in 15-30 seconds. Here
is one valuable resource that shows how and what you can modify to speed up
your shut down. In the example given you will see a value of 20,000 as the
default value. This is, in fact 20 seconds. Absolutely a life time in
computing terms. I have mine set to 500 which is 1/2 second. Now I certainly
don't advocate that drastic a drop. I have it set that way as I know my
system is safe with this setting. For you I would start with say 5000 which
is 5 seconds. A savings of 15 seconds from the default and ample time for XP
to do what is needed. There are other values like HungAppTimeout etc. that
you can also modify. Why not join the site that I linked to and then look for
me, The Unknown P and I will be delighted to help you. Contrary to what the
other posts say you can vastly improve shutdown times with simple registry
tweaks.
http://www.theeldergeek.com/increase_shutdown_time_for_services_to_close.htm
TTFN.
 
The said:
Wow I'm blown away by these nay sayers. Yes there certainly
are modifications you can make to certain keys in the
registry that will greatly reduce your shutdown times. The
biggest culprit of long shut down times are applications
that are set to clear pagefile when XP shuts down. I've
take computers that shut down in 2 to 3 minutes and get
them to shut down in 15-30 seconds. Here is one valuable
resource that shows how and what you can modify to speed up
your shut down. In the example given you will see a value
of 20,000 as the default value. This is, in fact 20
seconds. Absolutely a life time in computing terms. I have
mine set to 500 which is 1/2 second. Now I certainly don't
advocate that drastic a drop. I have it set that way as I
know my system is safe with this setting. For you I would
start with say 5000 which is 5 seconds. A savings of 15
seconds from the default and ample time for XP to do what
is needed. There are other values like HungAppTimeout etc.
that you can also modify. Why not join the site that I
linked to and then look for me, The Unknown P and I will be
delighted to help you. Contrary to what the other posts say
you can vastly improve shutdown times with simple registry
tweaks.
http://www.theeldergeek.com/increase_shutdown_time_for_services_to_close.htm
TTFN.
Click to expand...

As much as I like theeldergeek, I think that response is short
sighted and ignores that fact that something may be
broken/borked, and that needs to be assessed first.


Pop
 
LMAO. While I understand your need to be cautious I certainly don't see your
need to cast aspersions on anothers post. Paranoia maybe your thing and it's
ludicrous to automatically assume something is wrong. Shutdowns can be
lengthy, and can be that way for several reasons, only one of which maybe a
problem. It is extremely rare for a system with problems to only display
those symptoms during shut down. Extremely rare indeed. Shortening shut down
times is just one of dozens of ways of modifying XP to a style that suits
you. That's one of the things that makes XP so much better than previous Os's
from MS. The fact that you can configure it in nearly countless ways without
rendering it useless. Take it for a fact, that the modifications, to the
registry, that I have suggested have been thoroughly researched and
extensively tested and shown to cause no ill effects to the OS what so ever.
Even should a registry key be modified in a manner that XP doesn't like it
will simply be ignored and bypassed for the default settings. ERUNT is an
excellent tool that will do an entire copy of your registry for recovery if
necessary. Exporting the exisiting key to a folder of your choice, so that
you can merge it back to the original location should your modification prove
futile or cause any percieved issues is yet another simple, and easy to
learn, technique. The response was, of necessity, short and to the point. I
could give an entire, and very lengthy, post on the registry locations and
modifications necessary to improve shutdown time. Boot times as well for that
matter. Along with dispelling any myths regarding reg tweaks like the useless
clearing of the prefetch. So, while I may have been brief, I am far from
short sighted. TTFN.
 
The said:
Wow I'm blown away by these nay sayers.
Click to expand...

What is wrong with saying that adjusting the service timeout will only help
if the problem is with services?

You made a good point about checking that the page file isn't being cleared,
if it is that would certainly impact the shutdown time. But, for example,
that isn't a service and you can fiddle with the service timeout for a month
without changing one little thing if the pagefile is the item the user is
having a problem with.

I'm sorry if you consider it wrong to correctly diagnose a problem before
treating it, but I'm going to carry on suggesting that is the correct way to
go about things.

--
--
Rob Moir, Microsoft MVP for Security
Blog Site - http://www.robertmoir.com
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
I'm always surprised at "professionals" who STILL have to be asked:
"Have you checked (event viewer / syslog)".
 
Back
Top