Shutdown and restart operations are very slow in Windows Small Business Server 2003


When you shut down or restart a Microsoft Windows Small Business Server 2003-based computer, the shutdown process may take a very long time, or Windows may appear to stop responding.


This problem occurs when you install or reinstall Microsoft Exchange Server 2003 directly from Windows Small Business Server 2003 CD 2 instead of using the integrated Windows Small Business Server 2003 Setup program. The Setup program for Exchange Server 2003 configures Windows to wait 10 minutes for the Exchange services to stop running before it shuts down. This 10-minute time-out is appropriate for Exchange servers on an enterprise network, where the Exchange databases generally take longer to shut down. However, for smaller organizations, this 10-minute time-out is longer than is necessary. Therefore, the Windows Small Business Server 2003 Setup program reduces the time-out value to two minutes.


To resolve this problem, change the value of the WaitToKillServiceTimeout registry entry to two minutes. To do this, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  1. Start Registry Editor. To do this, click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click the following registry subkey:
  3. In the right pane, double-click the WaitToKillServiceTimeout value.
  4. In the Value data box, type 120000, and then click OK.
  5. Quit Registry Editor, and then restart Windows Small Business Server 2003.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

ID articolo: 827610 - Ultima revisione: 15 mar 2008 - Revisione: 1