Windows system, we can modify the registry to adjust the corresponding options.
close shorten the waiting time before the service
home Xiaobian above mentioned systems, the shutdown process WindowsVista, the system first sends a warning to shut down loaded service, and then wait for these The shutdown signal given after the service is automatically turned off. If the shutdown signal is not received after the set waiting time period, the Windows system will forcibly close the corresponding service implementation.
to speed up the shutdown speed WindowsVista, first of all can be achieved by shortening the default service shut down the waiting time. Open the Registry Editor, find the following registry key:
HKEY_LOCAL_MacHINESystemCurrentControlSetControl
In the right panel, you can see a "WaitToKillServiceTimeout" registry entry called, double-click it to modify the Its value is adjusted from the default of 20000 (in milliseconds) to a smaller value, such as 5000 or even 1000, so that if Windows Vista does not receive service within 5 seconds (5000) or 1 second (1000) of the setting, Signal, the system will pop up a warning window to inform the user that the service can not be aborted, and give the option to force the abort service or continue to wait for the user to choose.
close shorten the waiting time before
applications and processes on and off the waiting time before a similar service, WindowsVista also have to wait a while before forcibly close the application process with the program or process itself off The time, only after the time limit, the Windows system will force it to abort.
therefore, shorten the default close the application or wait time, the same can speed up the shutdown speed of WindowsVista.
same setting method similarly to the above, the following branches found in the registry:
HKEY_CURRENT_USERControlPanelDesktop
double-click the right panel "WaitToKillAPPTimeout", its value from the default 20,000 (The unit is also in milliseconds) is modified to a smaller 5000 or 1000. In this way, if Windows does not receive an application or a shutdown signal after waiting for 5 seconds or 1 second after issuing a shutdown command, a corresponding warning signal will pop up. And ask if the user is forcibly aborted.
in the right panel also called "HungAPPTimeout" registry key that corresponds to the system after the user forced to shut down a process or application, the waiting time if the object is not responding . The default value is "5000", which can be changed to "1000".
Then, in the following registry branch:
HKEY_USERS.DEFAULTControlPanelDesktop
repeat the above operation, i.e., modify "WaitToKillAppTimeout" and "HungAPPTimeout" registry entries value.
automatically suspended after an application or process
at shutdown or log off, however, even if we will value "HungAPPTimeout" is set very small, does not mean WindowsVista waiting time exceeds the time limit The program or process is automatically aborted, and a dialog box will pop up to let the user confirm whether to abort. If you feel that this method is too cumbersome, you can modify the registry key to let WindowsVista automatically forcibly interrupt the process after the waiting time limit.
find the following registry branch:
HKEY_CURRENT_USERControlPanelDesktopregistry
can see there is a term for the "AutoEndTasks" registry key, the default value is "0" Modifying it to "1" means that Windows Vista automatically terminates all processes without the user's confirmation.
to ensure stability of the system is premised
While the above methods can in some cases significantly accelerated the shutdown speed WindowsVista. However, it should be emphasized that regardless of "WaitToKillServiceTimeout", "WaitToKillAppTimeout" or "HungAPPTimeout", it is a very important and indispensable parameter for Windows systems. Improper settings will affect the stability of the system or the consequences of losing important data of users. .
to "WaitToKillServiceTimeout" for example, use the Windows system WaitToKillServiceTimeout purpose is to give the corresponding service for some buffer time, so that the implementation of these services will be able to go back and write data in the cache before the system is shut down, if not retained With sufficient buffer time, the data may be lost and cause unpredictable consequences. Therefore, it is generally not appropriate to set the duration to be too short. It is even more inappropriate to set it to "0".