37

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?

ZygD
  • 2,459
  • 12
  • 26
  • 43
alex
  • 981
  • 2
  • 12
  • 18
  • Maybe you could give some examples of such services that fail to start. It's hard to guess what the issue may be without any details. – dxiv Jan 16 '16 at 00:12
  • 5
    If it makes you feel any better, you are not the only one. I have the exact same issue. The services are 32 bit. Custom software installed quite some time ago. So the WOW64 setting is there, turned on. I can start the services manually, but ever since upgrading from Windows 7 to Windows 10, the OS makes NO attempt to start the services. Their trace files show nothing, and the Event Log shows no attempt to start them, nor any problem with them. It is very frustrating. The Automatic Delayed is a lousy option, but I guess that's it for now... – Brian B Apr 05 '16 at 22:26
  • See also here: https://stackoverflow.com/questions/33238665/windows-service-not-starting-on-windows-10-upgrade – RenniePet Nov 25 '17 at 02:43
  • 1
    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 "MyUser@MyDomain.xxx.yy", solved the issue, although I have no explanation why. – MBWise Mar 14 '18 at 13:07

10 Answers10

15

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.

alex
  • 981
  • 2
  • 12
  • 18
  • If you are comfortable with regedit, I discovered that as long as the service has the key DelayedAutostart (DWORD), it will start. So I added this but set value to 0, as I did not want it delayed. Example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\DelayedAutostart – Brian B Apr 21 '16 at 15:26
  • 1
    I also found a thread on Microsoft technet, https://social.technet.microsoft.com/Forums/windows/en-US/a6e5d2b4-f591-40b0-825a-0818ea5bb254/windows-10-services-not-starting-up?forum=win10itprogeneral On that thread the OP says you can also use "restart on failure" as a workaround. – RenniePet Nov 25 '17 at 02:39
  • This worked for me in combination with de-selecting "Prefer 32-bit" as mentioned in the answer below by @Michael van der Horst – threadster Apr 15 '20 at 15:34
13

My 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

https://social.technet.microsoft.com/Forums/windows/en-US/b57ee42d-42ef-44a4-9670-be9088dbf9d4/reporting-server-error-1053-the-service-did-not-respond-to-the-start-or-control-request-in-a-timely?forum=sqlreportingservices

Good luck This is the source of the fix

Michael van der Horst
  • 1,483
  • 2
  • 11
  • 9
3

You can modify the startup from "Automatic triggered" to "Automatic" by command: sc triggerinfo w32time delete

Now, the service can start automatically after reboot

Ahmed Khaled
  • 31
  • 1
  • Trying to understand: is this new idiotic "feature" of Windows, or it existed long ago? Turned out my business-critical servers were not synching with ntp server 'cause Windows Time service has suddenly changed its start type from Automatic to Automatic (Trigger start) and of course any attempt of a scheduled task to synchronize time was failing. – Anatoly Alekseev Dec 23 '18 at 03:50
2

What 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    : 0
Michael van der Horst
  • 1,483
  • 2
  • 11
  • 9
1

Well, 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.

axys93
  • 379
  • 2
  • 11
  • 3
    Sorry friend , but maybe you have not understand what I'm saying. These services have Automatic Startup type , and are not System services. They are installed after some application's installation. Are working very well. If I shutdown windows , and turn on , these services start automatically and everything works ok. But the problem appear if I restart windows. After restart these services does not start automatically , and application related to them doesn't work. I can start manually and everything works fine until I do another restart and the problem appear again. – alex Jan 15 '16 at 01:01
  • Hmm, I guess you should really take a look at the Event Logger to see if the services generates some kind of error. So you can open it and look for messages near the timeframe you restarted your PC. If they are stopping prematurely because of an error, the description or code of that error might be found there and we can have a better idea of what the real problem is. – axys93 Jan 15 '16 at 01:58
  • 1
    No , no error at Event Logger. There's no log that describe a premature stop. The service just doesn't start. It seems that if I restart windows 10 , the system just ignore the Automatic Startup type of these Services. – alex Jan 15 '16 at 02:39
  • @alex There usually _are_ event log entries for services that fail to start. – dxiv Jan 16 '16 at 00:13
  • @dxiv The service doesn't fail to start. The Automatic Startup type is ignored by windows when a windows restart is made .It seems that this is an already know bug in windows 10 . The only solution that works is that I've posted below. – alex Jan 16 '16 at 00:22
  • @alex `The service doesn't fail to start.` I don't see proof of that in what you posted thus far, nor of `seems that this is an already know bug in windows 10` for that matter. Please edit your original question and provide the necessary details, otherwise it's all speculation. – dxiv Jan 16 '16 at 00:27
  • @dxiv I give you 1 example , reported to Microsoft : https://connect.microsoft.com/SQLServer/feedback/details/1873617/sql-server-not-coming-online-after-os-upgrade-to-windows-10-even-when-startup-type-is-automatic. This speak only for SQL server service , but I've detected several other services with the same problem. – alex Jan 16 '16 at 01:06
  • 1
    @alex Your link references a [discussion thread on technet](https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bb5f2199-f283-4249-a029-53978d637148/sql-service-stops-working-after-windows-10-upgrade?forum=sqldatabaseengine#a078082f-b734-477b-8abd-8d75aac73e92), where it is noted that there is an entry in the event log indicating that the service failed to start (`"The SQL Server (MSSQLSERVER) service failed to start ..".`). That's quite different from your claim `The service doesn't fail to start`. At the risk of repeating, your question is unanswerable as-is now, without any details. – dxiv Jan 16 '16 at 02:07
  • @dxiv That's your link. It's not mine. Please look at my link. anyway this is not important. The important thing is that some Automatic Services doesn't start automatically when windows 10 is restarted. – alex Jan 16 '16 at 02:47
  • 1
    @alex It's _not_ my link. Did you even _read_ the link you posted? The 2nd paragraph says `The issue is reported on below MSDN thread https://social.technet.microsoft.com/Forums/sqlserver/en-US/bb5f2199-f283-4249-a029-53978d637148/sql-service-stops-working-after-windows-10-upgrade?forum=sqldatabaseengine` which is precisely where I quoted from. Anyway, at this point I'll leave it to others to second-guess what the problem might be without any assistance from your part. – dxiv Jan 16 '16 at 03:05
  • @dxiv The problem exist , this is important. The only solution that I've tried on my Pc and has resolved the problem , is posted below on my answer. – alex Jan 16 '16 at 03:09
1

I 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

JEAN-MARIE
  • 11
  • 2
1

Try with the below command:

sc config "SVCNAME" start= delayed-auto
Scott - Слава Україні
  • 21,399
  • 46
  • 64
  • 121
BattleTested_закалённый в бою
  • 129
  • 15
1

If 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*
cybernetic.nomad
  • 5,415
  • 12
  • 25
Ludo
  • 11
  • 1
1

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 "MyUser@MyDomain.xxx.yy", solved the issue, although I have no explanation why. – MBWise Mar 14 '18 at 13:07

neflow
  • 11
  • 1
0

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

https://support.microsoft.com/en-us/kb/922918

Fernando Diaz Toledano
  • 111
  • 2