Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, August 2, 2016 9:45 PM | 2 votes
Hello community, I'm posting to find out who has had this problem and who is experiencing this problem. The problem is that windows 10 isn't starting services that is marked for automatic startup. These services are mostly non windows services but services that goes with certain applications and software, that we need to start up with windows. Now i have seen this happen with two different kinds of applications that we are running and this issue caused us to revert back to 7 on a few of our computers because those are what runs our company. I have to computers in front of me, one computer works and start the services and the other will not even on a delayed start up. These computers are exactly the same the only difference is one is an i7 and the other is an i5. Another one of computer is an alienware and it is experimenting this issue of not starting services. These services are set to automatic start up. I also did some looking in to these issues as well and found that it can be an issue with .net, regitary keys, 32bit applications, also boot loadups from msconfig. I already tried msconfig with the different load types still no luck. Does anyone know what the underlying issue here is?
All replies (7)
Tuesday, August 16, 2016 3:52 PM âś…Answered
I discovered that if i modify the service to automatic restart on failure they will run. Or if i choose Automatic delayed they will run. If the services isn't Microsoft based then you may have to modify the services to make them start.
Wednesday, August 3, 2016 2:43 PM | 1 vote
I'm just trying to figure out WHY the services don't start up automatically!?! And What Else has been decided to be turn off and not starting up as well?
Thursday, August 4, 2016 6:45 AM | 1 vote
Hi JimmyWin10,
Since the issue occurred after upgrading to Windows 10, those apps may be not compatible with Windows 10. Please verify whether they are compatible with Windows 10 from the software developer.
Try to reinstall them to have a troubleshoot.
We could try to run "shell:startup" to open the startup folder and put those apps` shortcut in that folder.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, August 4, 2016 9:03 AM | 1 vote
perhaps the are started, but just fail to start, so can you start them manually?
Have a look in event viewer, "system" log, search for event by source "Service Control Manager".
In powershell, run this command:
Get-EventLog -LogName System -Source 'Service Control Manager' | Out-GridView
Monday, August 8, 2016 2:31 PM
Sorry for the late response here. With software i was working with i need to put restart parameters on the services to kick them in for automatically. The software is rated for windows 10 as well. I just seen/ been noticing a few things that windows 7 has done better then windows 10. Services start and run more efficiently on 7. With 10 you have to go in to the services and put the restart services if failed on. That seems to work like a charm or delayed. Im hoping the 1607 update has more fixes then errors this time around and may resolve this issue as well.
Wednesday, August 10, 2016 2:39 AM
Hi,
How about the issue, is there anything to update?
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Sunday, March 18, 2018 9:32 PM
This one has been driving me crazy too. For me it is on Windows Server 2016. A simple C# DotNet 4.0 Service starts manually just fine, but does not start automatically unless I set it to DelayedAutoStart. As a test I put an EventLog.WriteEntry as the first action in Service Main routine and OnStart routine. When I reboot, that log entry does not appear, even though the System log says "the service did not respond in a timely fashion". There is definitely something funcky going on with the Service Control Manager in Window 10 and Server 2016.