Skip to content

Learn how to fix Error 1053: The service did not respond to the start or control request in a timely fashion or error 0x8007041d for Windows Defender.

This fix applies to all those services, which are giving Error 1053 when you start them.

We all know that when you start your Windows operating system, there are many background services which contribute altogether to make this possible. These background services can be observed from Services window (run services.msc command to get this). In various scenarios, if one of these services fails to start or work properly, the associated feature or software gets affected.

Recently while turning on Windows Defender for protection of a system, we came around the Windows Defender service related issue. In this case, when we tried to start Windows Defender, this error resulted:

The service couldn’t be started

The service did not respond to the start or control request in a timely fashion.

Error code: 0x8007041d

FIX The Service Did Not Respond To The Start Or Control Request In A Timely Fashion

Also by manually starting the Windows Defender service, we received the same error message with different error code:

Windows could not start the Windows Defender service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.

FIX The Service Did Not Respond To The Start Or Control Request In A Timely Fashion

Recommended : Go here if you’ve received error 577 with Windows Defender Network Inspection Service.

By investing things technically, we found that the root cause behind this issue is Service Control Manager. Actually when a service starts, I has to do communicate with Service Control Manager. If the Service Control Manager doesn’t receives a ‘service started‘ signal from the service within a pre-specified time which is typically less than 30 seconds, the time-out occurs. When the time-out occurs, Service Control Manager has no option, other than to terminate the service. So if you’re receiving the above mentioned error, that means Windows Defender or the other service is sending ‘service started‘ signal in time beyond pre-specified time (taking more than 30 seconds or so). As a result of this, service couldn’t be started at all. If we adjust this pre-specified time, then we can solve this problem very easily.

Here are the steps you need to follow:

FIX : ‘The Service Did Not Respond To The Start Or Control Request In A Timely Fashion’ For Windows 10/8/7

Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.

1. Press W8K + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.

RegistryEditor

2. In the left pane of Registry Editor, navigate here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

FIX The Service Did Not Respond To The Start Or Control Request In A Timely Fashion

3. At this registry location, highlight the Control key in the left pane of above shown window. In the corresponding right pane, right click and select New -> DWORD Value. Name thes newly created DWORD as ServicesPipeTimeout and double click on it to get this:

FIX The Service Did Not Respond To The Start Or Control Request In A Timely Fashion

4. Finally, in the Edit DWORD box as shown above and set the Value data to 6000, making sure that select Base is Decimal. Click OK and close the Registry Editor and reboot the machine to make changes effective. After restarting the system, re-try to start the service with which you were facing the error, it should start fine by now.

That’s it! Go here to read how to disable automatic removal of scan history items for Windows Defender.


Facebook Google+ Twitter

23 Comments

  • Thank you for the suggestion. However, I get the error when running regedit too. Is there an alternate solution??

  • Kapil Arya

    ^^ Try SFC /SCANNOW command in administrative Command Prompt, see if it helps:

    https://www.kapilarya.com/how-to-use-system-file-checker-to-repair-windows

  • I am getting same error in windows 10,
    i can open windows defender..
    Once i clicked on START
    Exactly same error will appear,
    “0x8007041d”

    Windows 10, home edition,
    no antiviruses installed except defender….

  • Kapil Arya

    ^^ Did you get same error message with that error code?

  • I am getting error on my window 10 the service did not respond to start or control request in timely fashion how can I solve it plz. Help me

  • HOW IN THE HELL are we supposed to follow these instructions if services.msc AND regedit BOTH ARE INCLUDED IN THIS PROBLEM??

  • Kapil Arya

    ^^ Didn’t get your question! Can’t you start Registry Editor/Services snap-ins?

  • This solution seems to be working for me.

  • Kapil Arya

    ^^ Glad we could help 😎

  • Can’t start regedit

  • Nothing is able to open. Task manager, regedit, msconfig, or if i try to install or unistall any program can’t be done. I have issue like other too….. Not able to restore computer. Chrome is not opening.
    But internet explorer can be open. Command prompt cant be run as administrator. Try to install some program like cleaner, repair system tool, but error message got at initiall install. What should i do need help microsft windows product.
    And aslo please tell me about this problem. What is the cause of this problem.
    The process opening regedit, shows same error message…..
    Need help……
    Plz help help
    Thank you

  • No the above solution is not able to work on my system.
    Still getting the same ERROR.
    {ERROR}Windows could not start the Windows Defender service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.
    {ERROR}
    Can anyone help on this.

  • Worked great for me!

  • Kapil Arya

    ^^ Happy to help 😊

  • I think you need to change the value in your example. You are showing 6000. The default is 30000 milliseconds (or 30 seconds). You are recommending 6000 milliseconds (or 6 seconds). Most other articles I’ve read are showing anywhere from 120000 to 180000 milliseconds (2-3 minutes).

  • Kapil Arya

    ^^ Agreed. You can here use the value equal to 6 seconds or above but less then 30 seconds 😎

  • Windows 10, 1607
    Has not worked. Tried 6000 and 120000 values

  • Did not work for me

  • hello sir,

    Thank you for your kind reply

    For me your 1st method as your showing in the screen regestry not familier with mine for other’s you have given 2nd method

    but the 2nd method looking so difficult can you please send any easy method to solve my problem

    Thank you

  • Kapil Arya

    ^^ Registry method is easiest method if you carefully follow the instructions. If you’re not comfortable editing registry, create System Restore point first so that you can go back if something went wrong,

  • I tried but my win 2016 server does not have the ServicesPipeTimeout option under the Control setting.

  • Hi, I have tried the above process by giving ServicesPipeTimeout to 180000 and then restarted the system, but still I get Error 1053 while starting the service.

    This service worked fine in Windows7 but having issues on both of my Windows10 pro.

  • Kapil Arya

    ^^ Have you tried the value 6000?

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    Recent Comments

    • Sahul Hameed : Hi, this snapin may not be used with this edition of wind...

      3 hours ago

    • Kapil Arya : ^^ Glad it helped you, Samsul 😊...

      1 day ago

    • Samsul Arif : Thank you so much! This tutorial is worked for me :D...

      1 day ago

    • Dew : Didnt work tried everything my EPSON Stylus 670 Only way to...

      2 days ago

    • Jeff : fix 1 worked. thank you very much....

      2 days ago