Roon.exe does not start any more after update to build 1272

[jts_muc]

Hello, I am using Windows 10 Home. Today after update to 1272 Roon App does not start any more. When I click roon.exe nothing happens. Tried to uninstall/install, but it does not help. .NET6 is installed/updated as well.

Software is not usable for me now. Any suggestions how to solve this problem? Thanks

[Menzies]

Hi @jts_muc

Welcome to the Roon community

I’m a fellow user here to offer help

From other threads with a similar issue. This might help.

Roon app not working in WIndows 10Pro after update. Core is not on pc

Do you have .NET 6.0 installed? The new Roon update switched to that and IIRC there was at least one similar thread where it was missing on the PC and installing it helped You would just need the .NET Desktop Runtime (not the SDK) from here:

RoonServer failing to start on Windows 10/11 after build 1272 update [Roon Investigating, workaround in thread]

Hi All, Thank you for bringing this issue to our attention, I have notified the team and we are looking into this, we will update everyone once we have more information. In the meantime, it sounds like doing a reinstall of the RoonServer Application Files (while leaving the Settings and Databases unchecked) allows RoonServer to start again. You can give this suggestion a try from your Windows Apps & Features menu: [2023-05-11 13_03_50-Settings]

[jts_muc]

Thank you. Tried both ways but it didn’t help…

[jts_muc]

Is there any solution here how to use the 1272 on Win10? Before the update to 1272 everything was working. I have a lifetime license and would want to continue using Roon software please. It will be fair if Roon Team finally find and post a solution or give a possibility to download previous working version before the update.

Thanks

[Wes]

Hi @jts_muc,

Did you happen to wipe the folders after uninstalling but before reinstalling? Also, did you happen to see if Roon was running in task manager?

If there’s some form of corruption in the SW it might be carried over if not. Here are the instructions for a clean slate install.

• Navigate to your Roon’s Database Location
• Find the folder that says “Roon” and “RAATServer”
• Rename “Roon” to “Roon_old” and “RAATServer” to “RAATServer_old”
• Reinstall Roon from our Downloads Page

Please do try this and let us know. We’d love to get you back to enjoying the music.

Thanks,
Wes

[jts_muc]

Hi @Wes

just tried it, but didn’t help. I don’t believe there is some form of corruption in the SW on my PC as I am not the only one with my problem.

Quite frustrating not being able to use the software you have paid for since many weeks after the update.

Can you provide the older version to download?

[noris]

Hi @jts_muc ,

Apologies for the delayed response here, Wes has been pulled away on another project and we missed your follow-up response here.

Are you still having issues with getting Roon running at the present time? Are you using both Roon + RoonServer on the same PC?

Do you see any Application errors related to Roon in your Windows Event Viewer and if so, can you copy+paste them here?

[jts_muc]

Hi Noris, I just use Roon Client and its not starting after the update. Tried everything possible from this forum, but no success. No errors - its just not starting anymore…

[noris]

Hi @jts_muc ,

Are you able to manually access your Roon logs, are there any log files contained in the directory?

Logs

If so, can you upload the full contents of the Log folder to the following link and let me know once uploaded?

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

[jts_muc]

Thank you Noris, will upload tomorrow

[jts_muc]

@noris just uploaded the log files. Thank you

[jts_muc]

@noris any news?

[noris]

Hi @jts_muc ,

Sincere apologies for the slow response here. I noticed that you now have a ROCK registered to your account, has there been any change in behavior? I have looked over your previous log set, but it is inconclusive as to where the issue lies. If you are still seeing this issue, do you have any clues visible in your Windows Event Viewer logging regarding the issue?