Get Live Help
The Defender Log Receiver service fails to start and the following error events appear in the Windows Application log:
"The service did not respond to the start or control request in a timely fashion."
"A timeout was reached (30000 milliseconds) while waiting for the Defender Log Receiver service to connect."
Attempting to start the "Defender Log Receiver" service manually shows the error:
"Windows could not start the Defender Log Receiver service on the Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."
By default the time-out value for the service control manager to allow a service to start is 30 seconds (30000 milliseconds).
The Defender Log Receiver service may require more than 30 seconds to start and therefore fails due to not having enough time.
- Increase the time-out value to 60 seconds by following the steps in this Microsoft Article ID 922918
One Identity does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.