Timeline for Automatic services doesn't start automatically after windows restart
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2016 at 3:09 | comment | added | alex | @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. | |
| Jan 16, 2016 at 3:05 | comment | added | dxiv |
@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.
|
|
| Jan 16, 2016 at 2:47 | comment | added | alex | @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. | |
| Jan 16, 2016 at 2:07 | comment | added | dxiv |
@alex Your link references a discussion thread on technet, 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.
|
|
| Jan 16, 2016 at 1:06 | comment | added | alex | @dxiv I give you 1 example , reported to Microsoft : connect.microsoft.com/SQLServer/feedback/details/1873617/…. This speak only for SQL server service , but I've detected several other services with the same problem. | |
| Jan 16, 2016 at 0:27 | comment | added | dxiv |
@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.
|
|
| Jan 16, 2016 at 0:22 | comment | added | alex | @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. | |
| Jan 16, 2016 at 0:13 | comment | added | dxiv | @alex There usually are event log entries for services that fail to start. | |
| Jan 15, 2016 at 2:39 | comment | added | alex | 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. | |
| Jan 15, 2016 at 1:58 | comment | added | axys93 | 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. | |
| Jan 15, 2016 at 1:01 | comment | added | alex | 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. | |
| Jan 14, 2016 at 22:36 | history | answered | axys93 | CC BY-SA 3.0 |