Adjust Service Control Manager Timeout in Registry
During system startup, Windows expects services to respond to the
Service Control Manager (SCM) within a default window of 30 seconds
(30,000 milliseconds). If a heavy or slow-loading service fails to start
within this timeframe, Windows logs an Event ID 7000 or 7011 error and
terminates the startup attempt. You can resolve these startup errors by
modifying the ServicesPipeTimeout entry in the Windows
Registry to extend the timeout period.
Steps to Increase the SCM Timeout Using Regedit
- Open the Registry Editor
- Press
Windows Key + Rto open the Run dialog. - Type
regeditand press Enter or click OK. - Click Yes when prompted by User Account Control (UAC).
- Press
- Navigate to the Control Key
- In the left-hand navigation pane, navigate to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the left-hand navigation pane, navigate to the following path:
- Create or Modify the ServicesPipeTimeout Value
- Check the right-hand pane for a value named ServicesPipeTimeout.
- If it does not exist:
- Right-click any empty space in the right pane.
- Select New > DWORD (32-bit) Value.
- Name the new value
ServicesPipeTimeoutand press Enter.
- If it already exists:
- Double-click ServicesPipeTimeout to edit it.
- Set the New Timeout Value
- In the Edit DWORD (32-bit) Value window, select the Decimal radio button under the Base section.
- In the Value data field, enter the desired timeout
duration in milliseconds:
60000for 60 seconds (1 minute)120000for 120 seconds (2 minutes)180000for 180 seconds (3 minutes)
- Click OK to save the changes.
- Restart the Computer
- Close the Registry Editor.
- Restart Windows for the Service Control Manager to apply the new timeout threshold.