Fix A service does not start error with Event ID 7000, 7011, 7009 in Windows 10

If when you start your Windows computer, a service does not start and the event ID 7000, 7009 or 7011 is recorded in the Windows event log, this message may help you. In this article, we will suggest a workaround to resolve this problem.

Service does not start – Event ID 7000, 7009, 7011

Error events can appear in the application log in the following format:

Event 1

Type of event: error
Source of the event: Service Control Manager
Event Category: None
Event ID: 7000

the Name of the service the service failed to start due to the following error:
The service did not respond to the start-up or control request in a timely manner.

Event 2

Type of event: error
Source of the event: Service Control Manager
Event Category: None
Event ID: 7011

The description:
Timeout (30,000 milliseconds) waiting for a transaction response from the Name of the service a service.

Event 3

Type of event: error
Source: Service Control Manager
Event ID: 7009
Task category: none

A waiting time has been reached (30,000 milliseconds) while waiting for the Name of the service service to connect.

To work around this problem, you must modify the registry to increase the default timeout value to 60 seconds for the person responsible for service control.

The service control manager waits for the time specified by the ServicesPipeTimeout before logging events 7000, 7011, or 7009. Services that depend on the Windows Trace Session Manager service may take more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout appropriate value to give all dependent services enough time to start.

Since this is a registry operation, you must first back up the registry or create a system restore point in case the procedure does not work. Once you have taken the necessary precautionary measures, you can then proceed as follows.

1. Press the Windows key + R. In the Run dialog box, type regeditand press Enter.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl

3. In the right pane, locate the ServicesPipeTimeout Entrance.

If the ServicesPipeTimeout entry does not exist, you must create it. To do so, follow these steps:

• Click it Edit menu or an empty space in the right pane and then click New > DWORD value (32 bit).
• Type ServicesPipeTimeout, then press Enter.

4. Right click ServicesPipeTimeout, then click Edit to modify its properties.

5. Select the radio button to Decimal under Base, then type 60000 under Value data. This value represents the time in milliseconds before a service expires.

6. Click on Okay.

7. Restart the computer for the changes to take effect.

Your problem must be solved.

Read more: Troubleshoot Windows services does not start.