jellyfin / jellyfin-server-windows

The Windows tray app and installer for Jellyfin Server on Windows.
https://jellyfin.org
MIT License
79 stars 26 forks source link

[Issue]: Windows server / .Net-Framework 4.8.1 #119

Closed Tfreak586 closed 2 months ago

Tfreak586 commented 3 months ago

Please describe your bug

Windows server 2019 and older cant use the new Jellyfin server. Because .Net-Framework 4.8.1 is required and windows does not allow to install this version.

Reproduction Steps

Install newest server version. Try to start its not working because of .Net is not version 4.8.1

Jellyfin Version

10.9.0

if other:

No response

Environment

- OS: Windows Server 2019
- Linux Kernel: -
- Virtualization: -
- Clients: -
- Browser: -
- FFmpeg Version: -
- Playback Method: -
- Hardware Acceleration: -
- GPU Model: -
- Plugins: -
- Reverse Proxy: -
- Base URL: -
- Networking: -
- Storage:-

Jellyfin logs

No Logs because cant start.
Only window that open´s is "you need .NET 4.8.1"

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

nielsvanvelzen commented 3 months ago

What is the highest .NET framework version available for you?

Tfreak586 commented 3 months ago

The highest version for windows server 2012, 2016, 2019 is 4.8.0 You can find this information here too: https://learn.microsoft.com/en-en/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-481

nirwanah commented 3 months ago

I'm also experiencing this issue. This is also affecting the Media Player users who will not be able to connect to Jellyfin Server as Jellyfin Media Player v1.10.0 and newer requires Jellyfin Server 10.9.1 or later to work.

So the last compatible option for Windows Server 2019 users seems to be: Player: 1.9.1 Server: 10.8.13

DrDagless commented 3 months ago

Same problem with my server. Looks like it's been fixed by #121 so hopefully gets pushed to an update soon.

anthonylavado commented 2 months ago

There are issues with the way we currently handle the build when it comes to either of those fixes, so the next update from today is going out "as-is" until we can fix it properly.