

Right-click the value and select Modify.Rename the new value to WaitToKillServiceTimeout.A new value named New Value #1 appears in the right pane.Right-click this key and choose New > DWORD (32-bit) Value.If the problem occurs frequently, follow the steps below to extend the service closing timeout:
WIN7 STARTUP TIME WINDOWS
See this Knowledge Base article for details. In Windows 10, I went to services and enabled Windows Time service w32time to be automatic, that solved it for me. If the problem happens for the first time and you are not able to close the service from within Windows Services manager ( services.msc) or Task Manager, you can kill the service using the taskkill command. It is permissible to set a higher value - it should not have any impact on performance. In our test environment, we set the value ( Fig. 3.) to 240000 ms (4 minutes), and this enabled the service to start correctly. In the Value data field, type the value (in milliseconds) of time allowed for the service to start, and click OK. Right-click the ServicesPipeTimeout value you created, and choose Modify.Change the name of this new value to ServicesPipeTimeout.A new value named New Value #1 appears on the right.Right-click this key and select New > DWORD (32-bit) Value.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
WIN7 STARTUP TIME HOW TO
How to increase the timeout value for the service startupĪdditionally, you can change the timeout value for the service startup in the Windows registry:
