I have Windows 10 built 1511 with all the updates.
After I make a system restart some of the services with startup type Automatic don't start automatically.
But I can start them manually and after that everything is ok. But if I make a system restart, the problem appear again.
If I start the service manually, and after I do shutdown, everything is ok when I turn on again the PC. So the services are automatically started as should be. The problem appear only if I restart Windows. After restart, these services are not started automatically.
This problem appears only to some services that are related with applications (not those that are system services). These services don't depend to any other.
What can I do?
410 Answers
The only solution that works for the moment is to change the startup type of these services from Automatic to Automatic Delayed. I don't know if this is the best solution , but is the only that works for now.
3My previous answer did not fix our problem. In the end, we fixed it by setting the time out of the services to a higher value. Try this solution:
Go to Start > Run > and type regedit
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
With the control folder selected, right click in the pane on the right and select new DWORD Value
Name the new DWORD: ServicesPipeTimeout
Right-click ServicesPipeTimeout, and then click Modify
Click Decimal, type '180000', and then click OK
Restart the computer
Cause:
The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, 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 editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.
Reference case:
Reporting Server Error 1053: The service did not respond to the start or control request in a timely fashion
Good luckThis is the source of the fix
You can modify the startup from "Automatic triggered" to "Automatic" by command: sc triggerinfo w32time delete
Now, the service can start automatically after reboot
1What fixed it for us is, if you can change the service executable yourself:
In the project file change the Prefer 32-bit flag to false, then reinstall the service.
Check your service with CorFlags.exe. The 32BITREQ and 32BITPREF should be 0.
Version : v4.0.30319
CLR Header: 2.5
PE : PE32
CorFlags : 0x1
ILONLY : 1
32BITREQ : 0
32BITPREF : 0
Signed : 0Well, Windows can stop these services if they are not needed or if there is an instruction to stop the service after whatever it is doing. Some services depends on other services and they will only start when the first calls them.
An error can cause the service to stop prematurely too. You could go to the Event Logger and see if there are errors related to these services. If there is a "(Triggered start)" after it, these services usually are not required or they only start when it is needed to, for example, Biometric services.
You can also find further information about how services works here.
Unless you are noticing your PC is not working properly, it really shouldn't be a problem.
11I had the same problem. The services did not restart automatically after the machine was restarted. The reason is that the Windows 10 shutdown button does not mean (unlike Windows 7) a shutdown but can be considered as a standby if the "Set Power Buttons" configuration is as this.
In this case, if the services were stopped, they remain so. If they were started, they continue to run without being restarted (no initialization). Jean-Marie
1Try with the below command:
sc config "SVCNAME" start= delayed-autoIf someone still have issue about it : NSClient version 0.5 removed trigger detection from default service state. We have to add it manually :
*your_command* check_service -a "filter=is_trigger=0" *other_arguments* See the comment from MBWise:
For me when having this problem, changing "This account" in "Properties>Log On" for the service, to a network name in the form "MyDomain\MyUser" from "", solved the issue, although I have no explanation why. – MBWise Mar 14 '18 at 13:07
Try with this:
Run the following command to define a trigger event that suits your environment. In this example, the command determines whether an IP address is given to a host, and then it starts or stops the service.
sc triggerinfo w32time start/networkon stop/networkoff
where w32Time is your service name
or try this
2
