Problem after Upgrade on 10.11.0

[starbusch]

Hello, I am running my Jellyfin server on a Windows 11 (25H2) PC.
I had solved my media access on the NAS with a local link (D:\Jeliyfin\Media) to \\NAS IP address\Share.
With the upgrade from 10.10.7 to 10.11.0, there are access problems to the media folder, which is why the server startup is aborted.
I have now tried reinstalling the server, but I can't create a library because of the same problem.
What can I do, or how can I integrate a NAS share (SMB or NFS) as a library path?
I have a QNAP TS-453D as network storage.

Translated with DeepL.com (free version)

[schnappi]

Can you try translating your issue again? I think something got lost in translation.

[starbusch]

I am referring to the Windows installation of the Jellyfin server, not a Docker image.
Since no network paths work in the Jellyfin web interface (\\NAS-IP-address\share, smb://NAS-IP-address/share, or nfs://NAS-IP-address/share), I created a symbolic link with mklink in Windows via the command line. The command looked like this:
mklink D:\Jellyfin\Media /d \\NAS-IP-address\share
This allowed me to access the folders on the NAS via D:\Jellyfin\Media in version 10.10.7.
This no longer works with version 10.11.0. The folders on the NAS are not displayed.
Now my question is how to set up access correctly.

Translated with DeepL.com (free version)

[schnappi]

Got it. Are you running the server as a user or as a service? The fix will depend on the answer.

[starbusch]

As a Service

Is my approach to connecting the NAS share as a library correct?

[schnappi]

I won’t say you are wrong. However, I suggest the easy fix of automatically mounting the network drives normally and using the task scheduler to autostart Jellyfin as a user instead of as a service. As you know, the issue you are running into is accessing network drives by the Jellyfin windows service.

[starbusch]

However, I find that starting via the service is more stable.
It worked with 10.10.7 as well.
But I figured out how to make it work.
The service must run with the Windows user's login details.
Thank you.

[schnappi]

I should have recommended that. That is how I did it as well for a while instead of running it as a user.