Serviio

Serviio (2.0) doesn't startup when Windows 10 starts. I have this problem only on my Windows 10 laptop. On another one running XP I have no such problem.
Also, I already read and done everything in the thread:
viewtopic.php?p=40166

Any new idea please ? (I found nothing useful on google)

Also, I can't verify my Java version! It seems I have none installed on Windows and Serviio runs the Java program coming with it (\programs\Serviio\jre\bin) !

Lastly, as a workaround, can a user (not admin) launch Serviio.bat in \programs\serviio\bin ?

thanks

Please upload your Serviio log here as an attachment. You will find in in C:\Program Files\Serviio\log. It will explain why Serviio isn't starting.

Serviio installs its own version of Java, so it doesn't matter what version you have on your computer.

Sorry but nothing appears in the log exactly because Serviio doesn't start!

The last log I have is from when I started it manually. I can send it if you think useful.

Again my question: can any user (with no priviledge) can run Serviio.bat as a workaround in order to start the server (when admin isn't there) ?

thanks

It happens that after Windows 10 reboots, I have two processes 'ServiioServices.exe (32bit)' running.
I kill one of them and both disappear.
Then I start manually (serviio.bat) the server. Everything is ok as I can see from Serviio Console. This results in the attached log file.

Please understand that I cleared the log file before launching the server so you can see the server startup logs, yet I don't think it is useful because I started it manually and I'm looking to understand why it doesn't start as a Windows service automatically.

But, the fact that after reboot I have ServiioServices running may help...

A failure to start Serviio still creates a log file, unless it's completely blocked from starting. Can a non-admin user run the batch file? I can't say for sure, but I believe the answer would be yes. The Serviio service can be run as a regular user. It doesn't have to be a system account. The attached log file does show a normal startup. If there's no log file at all with a failed startup, then there's something other than a Serviio problem stopping the startup. Perhaps an anti-virus application, thinking (incorrectly) that it's not an authorized application.

I just checked my main media server, and there are two Serviio services shown in Task Manager, so that appears to be normal.

Well, I don't know how to explain it but now it works. Serviio server is launched at windows startup.

All I did was:

Through 'services.msc', I changed serviio "delayed automatic" startup to "automatic".

I had changed automatic to delayed automatic in the first place when serviio startup wasn't working.

It seems, just flipping to delayed auto, then to auto (and rebooting each time) did the trick although I suspect a timing issue frequent with system startup.

That's great news. Sometimes Windows just needs a nudge...