This post will show you how to fix A Service does not start due to timeout error with Service Control Manager, Event ID 7000, 7009 or 7011 when you start Windows 11/10 computer. These events are logged in the Windows Event Log. In this post, we will offer a workaround to address this issue.
A timeout was reached while waiting for the Service to connect
The service did not respond to the start or control request in a timely fashion
The error events may appear in the Application log in the following format:
Event 1
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000The ServiceName service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event 2
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.
Event 3
Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: NoneA timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect.
To work around this problem, you need to modify the Registry to increase the default time-out value to 60 seconds for the service control manager.
Fix Service Control Manager Event ID 7000, 7009, 7011
The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000, 7011 or 7009. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.
Related read: Fix Event ID 7031 or 7034 error when a user logs off.
Since this is a registry operation, you should first back up the registry or create a system restore point in case the procedure goes wrong. Once you have taken the necessary precautionary measure, you can then proceed as follows.
1. Press Windows key + R. In the Run dialog, type regedit, and hit Enter.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry.
If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
- Click the Edit menu or an empty space in the right pane, then click New > DWORD (32-bit) Value.
- Type ServicesPipeTimeout, and then hit Enter.
4. Right-click ServicesPipeTimeout, and then click Modify to edit its Properties.
5. Select the radio button for Decimal under Base, then type 60000 under Value data. This value represents the time in milliseconds before a service times out.
6. Click OK.
7. Restart the computer for the changes to take effect.
Your issue should be resolved.
Read more: Troubleshoot Windows Services will not start.
