[Ticket in] B1643 on Windows required manual .NET 10 runtime installation

Early Access
1

After updating to build 1643 on Windows, Roon prompted me to manually install the .NET 10 runtime.

I downloaded the installer and ran it, and after that Roon started successfully. I would like to confirm whether this is expected behavior.

I also checked the installed runtimes by running dotnet --list-runtimes in PowerShell, and found that the .NET 8 runtime was not installed. Because of that, I suspect this may not be the normal expected state for Roon on Windows.

Is manual installation of the .NET 10 runtime required for build 1643, or could this indicate that something is wrong with my environment or with the update process?

2

The very first line of the update details is this..

Migrated Roon Desktop Clients to .NET10

as found here. “EarlyAccess: Roon 2.63 Build 1643 and ARC 1.75 Build 395 are Live!”

So, yes, if .net10 is not already on your system then it will prompt for an install of it, like it did with mine.

1 Like
3

Thanks for the comment.

I understand that Roon has migrated to .NET 10. However, I could not tell from that note that the runtime model had changed from self-contained to framework-dependent, which is why I made this post.

6

Ahh. Yep. Your right, ignore my comment and let’s see what Support has to say.

8

The release notes discuss .NET10 on MacOS but I’m running Windows 11. Why is it trying to install this? Shouldn’t my Win 11 be enough? The problem is that my Windows machine is locked-down by my IT. The Roon Remote normally is able to be installed without much fuss but this is a showstopper.

10

Windows 11 doesn’t come with the .NET 10 runtime by default.

13

After installing B1645, I removed the .NET runtime that I had installed manually and restarted the system. I confirmed that Roon starts successfully. I believe this issue has been resolved.

3 Likes
14

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.