Confirm which Windows identity runs Jellyfin
A video that opens in your Windows desktop session may still be inaccessible to a Jellyfin service. The service runs under its configured identity, not automatically under the user who opened File Explorer. Begin by distinguishing a normal interactive installation from a service installation before following permission instructions.
Jellyfin’s current Windows service guide describes a Network Service configuration. Open Windows Services, locate the Jellyfin service and inspect its Log On As identity. Record the actual identity and installation paths privately. Do not change ownership or permissions based solely on a tutorial for a different account or an older installation arrangement.
Separate application data from the media originals
The service needs to maintain its own configuration and data, while media originals can often remain read-only. These are different directories with different purposes. Identify the configured data path and the folder used by the affected library before making a change.
Jellyfin’s guide recommends read-and-execute access for media playback. It describes Modify access for operations such as deletion or saving subtitles and NFO files into the media folder. Choose the access that matches your intended operations. Giving full control over a film collection is broader than establishing that the server can see and play a file.
Inspect the path from its parent directories
For an empty library or a path-not-found symptom, confirm that the service identity can traverse the parent folders as well as read the final media directory. The developer specifically notes parent-directory listing access in its troubleshooting guidance. A permission on the final file alone may not explain the whole path.
Use one known media folder as the case and record the before-and-after access choice. If the source is on a network share, follow the relevant Windows and server documentation for that account and share; a local drive example does not prove network authentication works. Do not solve a missing path by making an entire drive broadly writable.
Verify scanning and playback separately
After applying an appropriate authorized permission correction, start the service normally and inspect the same library. Confirm the known file is discovered, then open it through the intended client. Discovery, metadata matching and playback are separate milestones, so record where the result changes.
If saving an NFO or subtitle still fails while playback works, review the intentional write policy rather than treating successful reading as proof of write access. Keep the final service identity and folder policy in server notes. This procedure is based on the published Windows service route and does not claim hands-on validation of your Windows host.
Questions answered
Why can I open a file in Windows while Jellyfin cannot see it?
Your desktop session and the Jellyfin service can use different identities. Check the service’s Log On As account and access along the complete media path.
Must the service have full control of my movies to play them?
No. Jellyfin’s Windows guidance recommends read-and-execute access for playback. Write operations such as deletion or sidecar saving require a separate deliberate decision.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.