Thanks for checking in on those steps. I’d be happy to clarify a few things to help make the process smoother.
Regarding step 3: You’ll need to navigate to Roon’s server location not the backup. On Windows 11, this is typically found at C:\Users[Your Windows username]\AppData\Local\RoonServer.
This is the folder you’ll want to rename to RoonServer_old. Once that’s done, reinstalling Roon will generate a fresh RoonServer folder.
For step 6: After reinstalling Roon on your PC, a new database will be created automatically. You’ll then need to connect your Roon remotes to this new database. That is where you will click “Use another Roon Server”.
For step 7: To re-add the HDDs that contain your music go to Roon Settings → Storage.
Step 8 looks good as written.
If Roon Radio doesn’t respond to play or pause commands even after setting up the new database, that may indicate a deeper issue. In that case, restoring your backup likely won’t resolve the problem. You’re welcome to try it, but let us know what you experience and we’ll be here to help troubleshoot further if needed.
@daniel Thanks for the above. I have a family emergency and need to travel out of town. I won’t be able to address for 2-3 weeks. Can you keep the thread open or advise how to revisit upon my return?
No problem at all. This thread will stay open for 10 days, and each new comment will reset that timer. If it does happen to close in the meantime, feel free to reference this thread in a new one, and we’ll be happy to merge them for you.
Enjoy your travels, and we’ll be here when you’re ready to continue!
Just wanted to provide a short update and let you know we’ve put in a ticket for the devs to review and when there’s an update, we’ll let you know. Feel free to reset the thread timer before it closes if you don’t hear back in time, thanks!
In the absence of other reports, we’re going to close this thread temporarily for housekeeping while the ticket progresses through the pipeline.
We’ll comment here again as soon as we have an estimated timeline to the release of the fix. It’s likely we can resolve this issue on the backend without a Roon update or any action on your part, but we’ll let you know if any workarounds are available in the meantime.