| Event Id | 7018 |
| Source | Service Control Manager |
| Description | Detected circular dependencies auto-starting services. |
| Event Information | According to Microsoft: ----------------------------------- Cause: Two or more services are configured with circular dependencies. For example, if Service A depends on Service B, Service B depends on Service C, and Service C depends on Service A, you will receive this event if you try to start any one of these services. This is a configuration problem. Course of action First, examine the dependencies of Service A, the service that you tried to start, to identify where the dependency loop occurs. To investigate further, run the command, sc qc Service A to receive a list of services that the service depends on, and then run the command sc qc Service B on all services in the chain to see if they exist. If one of the services depends on multiple services, you will have to trace through one or more dependency chains starting at that service. To repair and update the list, use the sc config command to correctly spell or remove the problematic service name. Event IDs 7019 or 7020 will also be logged in the Event Viewer System log; check them for more specific information. ----------------------------------- Explanation An auto-start service is dependent on a chain of other services. One of the services in that chain is dependent on another service that appears earlier in the chain. User Action Ask the person with administrative rights on your computer to check the configuration of your system to review the chain of dependencies. Your administrator should remove the dependency that loops back. |
| Reference Links | MS Document |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.