Hi @Michael_Putz,
Thanks for the update! Odd that increasing the RAM hasn’t helped. I don’t think we’ve come across a Nucleus report in which upping the RAM didn’t help.
Could you share some specific timestamps around the issues you’re having? If you haven’t yet, I’d also reinstall RoonOS via the webUI, as well as reboot your server and router as well.
Thank you!
Hi @benjamin ,
Thanks for your replay.
Odd, that you say that it is odd… Given that @vadim mentioned before I’ve bought and added additional RAM …
This reads to me that this procedure helped some, but didn’t in other cases.
Here a protocol of another typical weekend with roon so far (it - still and again - shows decreasing performance speed the longer I do use roon):
2026-Feb-21
16:20 CET – roon software shut itself down out of the blue (however, the playback of the currently running song continued whatsoever)
Same happened at 17:22 CET
16:32 CET – Skipping to next track during an album listening lasted more than 4-5 seconds until playback of next song started (system freeze)
Same happened at 16:41 CET, 16:51 CET, 16:55 CET, 16:56 CET and 16:59 CET.
2026-Feb-22
08:45 CET – Displaying albums in “My Album” section freezes and do not show albums for several seconds:
10:18 CET – “Managing tags” section shows “You have no tags” for several seconds
12:50 CET – It takes several seconds before the “Album editor” properly opens:
13:41 CET – Displaying the queue takes more than 10 sec.:
14:03 CET – Displaying filtered tracks takes 10 or more seconds:
14:09 CET – Applying track editor takes more than 7 sec to open
14:10 CET - Name edit saving procedure lasted for more than 30 sec.
14:51 CET – Location edit saving procedure takes more than 30 sec.:
15:10 CET – Skipping to the next track takes almost 30 seconds:
Thanks for speeding up other possible solutions on your end
Michael
P.S.: Rebooting helps for a while, but the issues keep on returning the longer a roon session takes…
Hi @Michael_Putz ,
We released a new version of Roon today, can you please update and let us know if the same behavior still occurs? The new version includes scheduled metadata updates (these can be configured in Roon Settings → Library), and I am wondering if the background metadata updates were related to the previous issue. Let us know!
Thanks for the heads-up @noris . The roon software was updated yesterday. Settings are like this:
Unfortunatley, the performance still ist crazy slow, like described earlier 
Thanks for giving that a try @Michael_Putz, we’ll be in touch as soon as our development team has more information to share. 
@vadim @benjamin @noris - I’d also like to add, that manual roon backup processes failed twice in the meantime: on Feb 27 (18:49 CET) and March 6 (9:51 CET) the system crashed and shut itself down a few seconds or minutes after I’ve started the backup procedure manually. Thanks again for any quick help
Thanks for the heads up @Michael_Putz, please bring your Nucleus back online, and we’ll enable diagnostic mode for further inspection around the failure times you’ve shared above.
Thank you! 
@benjamin - will go online on Monday afternoon (I am enjoying a little break)
@benjamin back online
@vadim @benjamin @noris - Just now, at 5:58 PM CET on March 11th, the manual backup process was abruptly interrupted again, and the Roon system crashed. However, the backup restarted automatically afterwards. I urgently request assistance. All other procedures and playbacks still are as described before…
Thanks for your continued patience. We’re sorry for how long this has been dragging on. At this stage, we’ve confirmed that the issue is not resolved by the previously suggested steps, including the RAM upgrade and software update. Based on the behavior we’ve observed and the diagnostics gathered so far, this appears to be tied to an issue that is currently under active investigation with our R&D team.
We understand the impact this is having on your day to day use especially with search and metadata edits and queue loading and manual backups also triggering instability. The additional timestamps and examples you shared are helpful, and we are keeping them tied to the ongoing investigation.
At the moment, we do not have a reliable workaround or confirmed fix to offer yet, but the case remains active with development. As soon as we have either a targeted workaround or a fix path to share, we’ll follow up here. Thank you again for sticking with us on this.
@alex_h, @vadim , @benjamin , @noris , @connor
Another week of disastrously slow Roon performance came and went. At this point, it’s increasingly ruining my enjoyment of music through Roon altogether. The only good thing is that I’m playing more vinyl again… But seriously, guys: when can I expect a substantial, viable solution from you? A solution to a problem I first posted about two and a half months ago?
[edit] PS: manually started Roon backup failed twice today (Sat., Mar 28, 8:52 CET and 9:19 CET). Extremely worried, that changes might not be able to be saved anymore (!!??)
Hi @Michael_Putz,
We understand this is a frustrating issue. As mentioned above, our team is still working on releasing some memory optimizations that should help your case. We don’t have any new information to report - when we do, you’ll be notified.
There is nothing to worry about here, I can see from a fresh diagnostic report that your backup was successful on the 29th:
[Local 03/29 11:48:53] Debug: [broker/backups] successful sync on FileBrowser.Entry: Intenso, Intenso Portable SSD : /RoonBackupsWe didn’t observe any failures around the timestamps you’ve shared above. That said, we did see two USB drives show dirty unmount warnings at boot:
exFAT-fs: Volume was not properly unmounted. Some data may be corrupt.
exFAT-fs: bogus allocation bitmap size (need: 118267, cur: 118402) — this indicates possible filesystem corruption on that drive.
fsck on those drives would be advisable.
I think you have misunderstood. Isn’t the OP talking about a manual backup? Not a scheduled backup. Roon actually said they could reproduce this problem on Jan 2024. That’s more than 2 years ago now but I don’t recall seeing any followup.
https://community.roonlabs.com/t/cannot-backup-since-build-1353/256894/16
Can you specify the timings for this? How long does the roon team expect me to wait for substantial improvements?
There are (scheduled) backups which seem to work (can you confirm?), but manual backups that frequently fail (the time stamps provided should be proofs).
Today at 13:30 CEST (local time) the manual backup again failed and roon crashed… What a pain…
I have been plagued by this for years. Quite by accident, I discovered that if instead of restarting roon, I just ignore the “uh uh something has gone wrong” message, then the error message eventually goes away and roon backs up normally. Worth a shot.
@alex_h, @vadim , @benjamin , @noris , @connor
Almost three weeks after my last post to you on this, nothing’s changed. I am highly disappointed, I’d like to receive some substantial support…
re. the disastrously slow Roon performance
re. backup security
Can I do something? Have you done something? I am running out of patience.