Windows error 1053
ERROR_SERVICE_DID_NOT_RESPOND
What it means
Windows asked a service to start or stop and the service did not answer in time.
Common causes
- The service is stuck or crashing
- A dependency is missing
- The service executable is damaged
How to fix it
- Open
services.mscand start the service manually to read the error. - Check Event Viewer > Windows Logs > System for the service crash.
- Use a clean boot: in
msconfigopen Services, tick "Hide all Microsoft services", disable the rest, restart and turn them back on in groups. - Run
sc qc <service>to see its dependencies and start them first. - Reinstall the program that owns the service, or run
sfc /scannowfor a Windows service.