Universal Media Server | Forum

@dm34989 It would help to see logs. see the red section above.

Like I mentioned it may be due to changes in the binaries and a clean install might fix it. Backup your configuration files first.

I have not heard back yet if this works so I cannot be sure if this is the cause. If it does work then I can feed this back to the Devs as the update installer script may need changing.

After starting and when it's scanning media files, it oonly gets so far and then just exist.
Does that 2 or 3 times and then finally seems to finish
Restarted Win 10 PC and no difference

Attached debug file is after it seems to complete

I merged this topic as it is probably the same thing.

There was an issue on Github that was smilier and I think we found the problem

It appears my suspicion about the change to Java 25 is part of the reason.
The lucene search engine was added and that uses something in JDK25 but will work in JDK17 if those modules are enabled as part of the launch command line.

--add-modules=jdk.incubator.vector activates an optimized lucene search engine indexing. Without it won't use it.
--enable-native-access=ALL-UNNAMED is required for native system access. Especially Lucenes native memory optimization classes need this parameter. If not set, it those classes will not be used.

so it should look something like With the devs working on V16 using JDK25 they must have missed that these options need adding. I know a PR was made to fix this.

I don't know exactly how to add those options to UMS when auto-starting in Windows but you should be able to edit UMS.bat (or other startup script in Linux) to add them there and start UMS by running that.

Another option is to download JRE25 and extract it to the UMS folder then edit your script to set the path for JAVA_HOME to that folder.
This is part of my build script that I had to change to use java 25, I assume it will be the same if running UMS from a script. You could also get the updated startup script from the PR here