Serviio won't start after Win 10 update

On 15 September, Microsoft performed a massive update of my Win 10 computer. This update took over 1 1/2 hours. After this update, I was unable to start Serviio (version 1.6). While checking the Serviio website to see if other people also had this problem, I noticed that Serviio 1.7 had been released. So I downloaded and installed this and Serviio did immediately start. But I had the same problem again following a reboot. Serviio would not start even after waiting more than an hour. I tried to manually start it via the start button, but that didn't work either. I also manualy stopped the service and then started it again. That also didn't work. The Serviio console also did not work correctly. When I opened it, the error message "Firefox can’t establish a connection to the server at localhost:23423" was evident. A check in the Task Manager shows that Serviio is not running.

So I went back and reinstalled 1.7 again. This was effective in starting Serviio on it's own. So I repeated this experiment; rebooted computer and waited for Serviio to start. Again the same problems as noted above were evident. It seems like the only way I can now get Serviio to start at all is by reinstalling 1.7 every time. (SEE UPDATE BELOW)

Does this Windows update have a bug that causes problems for the Serviio app? Do other people have this problem and is there a solution yet?

UPDATE Sept 26: This is what has happened since the original post:

1. I've updated to Java 8 version 102;
2. For your information, this is Windows 10 HOME edition;
3. The update involved is Update for Windows 10 Version 1607 for x64-based Systems (KB3176936).
4. I am now able to start Serviio, but I have to double click on the file serviio.bat in the folder C:> Program Files> Serviio> Bin.
5. Even though the service will start, it will not restart when my laptop awakes from sleep mode. Serviio used to restart automatically when I simply opened my laptop. When starting from sleep mode, I have to first open the console and then stop the server and then start it (the console says that the server is running). This will then restart Serviio.

I've checked quite a bit in the forum for a solution but have not come up with one. Overall, I still have a situation where Serviio does not start automatically when my Windows computer boots. Does anyone have a thought on how to solve this???

You don't say whether you're running Win10 or Win10 AU (anniversary edition). The two are different builds and version numbers and use different updates. I've had no problem running either Serviio 1.61 or 1.7 on Win10 AU with all available updates.

You don't say whether you're running Win10 or Win10 AU (anniversary edition). The two are different builds and version numbers and use different updates. I've had no problem running either Serviio 1.61 or 1.7 on Win10 AU with all available updates.

Hello NickJP, It's Windows 10 Home edition. Furthermore, the problem started after installing Update for Windows 10 Version 1607 for x64-based Systems (KB3176936).

I continue to have the same problems. It's really confounding me. Any suggestions?

You don't say whether you're running Win10 or Win10 AU (anniversary edition). The two are different builds and version numbers and use different updates. I've had no problem running either Serviio 1.61 or 1.7 on Win10 AU with all available updates.

Hello NickJP, It's Windows 10 Home edition. Furthermore, the problem started after installing Update for Windows 10 Version 1607 for x64-based Systems (KB3176936).

I continue to have the same problems. It's really confounding me. Any suggestions?

Hello NickJP,

I've now updated Java to Java 8 102. After a reboot, waited an hour for Serviio to start. Unfortunately, no joy. If you look at my original post, you'll see that I've written an update about what I've tried, what's worked and what's not worked.

Do you have any new suggestions to try??

[DenyAll]

While I don't run Serviio on a Win10 PC, my thoughts are that perhaps the Serviio service isn't starting because something it is dependant on hasn't as yet started. Try the following:

• Firstly ensure that the Serviio Service is set to run correctly. In services.msc click on the Serviio service and ensure that:
  
  • The StartUp Type is set to start Automatically
  • Under Dependencies, the service is dependant on HTTP
    If the either of the above isn't set, set it and try a reboot.
• If the above is correct and its still not working on reboot, try setting the StartUp Type to Automatic (Delayed Start)

See if this helps your reboot. Not sure what to do about restarting from sleep (is it actually sleeping or is it hibernating?) but one step at a time - see if this works for reboots.

If the above doesn't work for reboots you need to check your Windows Event viewer for errors or warnings related to the Serviio service and see if that tells you anything. Also try starting the service manually from services.msc as that may help diagnose the problem.

[atc98092]

By the way, 1607 is the Anniversary Edition. I am using Serviio on it with no issues.

While I don't run Serviio on a Win10 PC, my thoughts are that perhaps the Serviio service isn't starting because something it is dependant on hasn't as yet started. Try the following:

• Firstly ensure that the Serviio Service is set to run correctly. In services.msc click on the Serviio service and ensure that:
  
  • The StartUp Type is set to start Automatically
  • Under Dependencies, the service is dependant on HTTP
    If the either of the above isn't set, set it and try a reboot.
• If the above is correct and its still not working on reboot, try setting the StartUp Type to Automatic (Delayed Start)

See if this helps your reboot. Not sure what to do about restarting from sleep (is it actually sleeping or is it hibernating?) but one step at a time - see if this works for reboots.

If the above doesn't work for reboots you need to check your Windows Event viewer for errors or warnings related to the Serviio service and see if that tells you anything. Also try starting the service manually from services.msc as that may help diagnose the problem.

Hello DenyAll,

I've done what you've said and have achieved a partial result. Serviio will now start automatically after Windows boots up. I achieved that by changing the StartUp Type to Automatic (Delayed Start) in Services. I can also confirm that this was previously set to Automatic, and that the service was dependant on HTTP as you indicated above.

However, Serviio will still not connect to my TV after my laptop restarts from Sleep mode (or hibernation). I open the Serviio console and can see that the server is running. However, it will not connect to my TV. I have to manually turn the server off and then back on again in order to get the connection.

Do you think that there is a way to solve this?

Thanks in advance!

[DenyAll]

Before we leave the reboot issue, can you please:

• check that the file %WinDir%\system32\drivers\HTTP.sys actually exists in this latest Win (may also be in a different folder).
• advise what the dependencies that Windows Media Player Network Sharing Service has under Win10 - this may have changed.

For the sleep issue, check your log file after it awakes from sleep (ps. give it a t least 5 minutes asleep). You should get something along the lines:

  Code:

2016-09-25 17:27:16,522 INFO  [DiscoveryManager] System wake up detected, restarting UPnP services for network re-discovery
2016-09-25 17:27:16,523 INFO  [EventDispatcher] Leaving EventDispatcher
2016-09-25 17:27:16,523 INFO  [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2016-09-25 17:27:16,705 INFO  [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2016-09-25 17:27:16,629 WARN  [MultiCastUtils] Could not find NIC with name 'eth3-0'
2016-09-25 17:27:28,110 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth3-0, will try again 9 times
2016-09-25 17:27:16,557 WARN  [PortMapper] Could not add port mapping to the router: No route to host: connect
2016-09-25 17:27:16,523 INFO  [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2016-09-25 17:27:28,157 INFO  [Device] Updated bound IP address of Device with UUID: c41c5514-0d79-3774-967b-023b9e31d01f, bound address: 192.168.0.2
2016-09-25 17:27:28,157 INFO  [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2016-09-25 17:27:28,157 INFO  [EventDispatcher] Starting EventDispatcher
2016-09-25 17:27:28,157 INFO  [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2016-09-25 17:27:28,225 INFO  [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Intel(R) 82566DM-2 Gigabit Network Connection) and address 192.168.0.2, timeout = 0

Look for the first and last lines in particular.

Try binding your adaptor (on Serviio Console, Status tab toward the bottom - may be off-screen) rather than setting it to Automatic and see if that helps.

ps. ' I have to manually turn the server off and then back on again in order to get the connection.' - I assume you mean from within Serviio Console you press the Stop Server button?

Before we leave the reboot issue, can you please:

• check that the file %WinDir%\system32\drivers\HTTP.sys actually exists in this latest Win (may also be in a different folder).
• advise what the dependencies that Windows Media Player Network Sharing Service has under Win10 - this may have changed.

For the sleep issue, check your log file after it awakes from sleep (ps. give it a t least 5 minutes asleep). You should get something along the lines:

  Code:

2016-09-25 17:27:16,522 INFO  [DiscoveryManager] System wake up detected, restarting UPnP services for network re-discovery
2016-09-25 17:27:16,523 INFO  [EventDispatcher] Leaving EventDispatcher
2016-09-25 17:27:16,523 INFO  [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2016-09-25 17:27:16,705 INFO  [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2016-09-25 17:27:16,629 WARN  [MultiCastUtils] Could not find NIC with name 'eth3-0'
2016-09-25 17:27:28,110 WARN  [LocalAddressResolverStrategy] Haven't found IP address for NIC eth3-0, will try again 9 times
2016-09-25 17:27:16,557 WARN  [PortMapper] Could not add port mapping to the router: No route to host: connect
2016-09-25 17:27:16,523 INFO  [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions
2016-09-25 17:27:28,157 INFO  [Device] Updated bound IP address of Device with UUID: c41c5514-0d79-3774-967b-023b9e31d01f, bound address: 192.168.0.2
2016-09-25 17:27:28,157 INFO  [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2016-09-25 17:27:28,157 INFO  [EventDispatcher] Starting EventDispatcher
2016-09-25 17:27:28,157 INFO  [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2016-09-25 17:27:28,225 INFO  [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Intel(R) 82566DM-2 Gigabit Network Connection) and address 192.168.0.2, timeout = 0

Look for the first and last lines in particular.

Try binding your adaptor (on Serviio Console, Status tab toward the bottom - may be off-screen) rather than setting it to Automatic and see if that helps.

ps. ' I have to manually turn the server off and then back on again in order to get the connection.' - I assume you mean from within Serviio Console you press the Stop Server button?

Hi DenyAll,

I think that we may now have solved this problem completely. The dependencies for the Windows Media Player Network Sharing Service was set to MANUAL and I changed the to automatic. I also bound the adaptor in the Serviio Console (Status tab toward the bottom - may be off-screen) rather than Automatic. That seems to have solved the problem completely. Serviio now starts after the computer boots up and will restart by itself when the computer awakes from sleep mode.

Thanks for your help, and for the interest of all others who either reviewed my request for help or wrote a comment in this post.

After doing what is told in this tread, my service is still NOT running.
I updated Java, looked at the dependencies for the serviio service, they all are working.
That is also the case for Windows Media Player.
I tryed everything I know, but nothing works.

So if somone knows the answer? please let me know.
And sorry about my bad English