Situatie
The Microsoft Windows Service Control Manager controls the state (i.e., stopped, started, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.
By creating or editing the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, hence giving the service more time to start up and report ready for the Service.
So if you receive an “Error 1053: The service did not respond to the start or control request in a timely fashion” error message, this post is useful for you.
Solutie
Pasi de urmat
Press Windows Key + R then put regedit in Run dialog box to open Registry Editor. Click OK.
In the left pane of Registry Editor window, navigate to following registry key.
| HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
In the right pane of Control registry key, look for the registry DWORD (REG_SZ) named ServicesPipeTimeout. Double-click on this DWORD to modify its Value data. Now, set the Value data as 180000, making sure that select Base is Hexadecimal. Click OK.
Note: If the ServicesPipeTimeout value is not available, you need to create the registry DWORD (REG_SZ) named ServicesPipeTimeout. To do that, right-click in the pane on the right and select NEW > DWORD (32bit) Value. Name the new DWORD: ServicesPipeTimeout and set the Value data as 180000 (making sure that select Base is Hexadecimal) and click OK.
You can close the Registry Editor and reboot the machine to make changes effective.
Leave A Comment?