Sorry to jump in again. Are the logs from the machines any help at all? I’ve seen one user post a log which complained about the branches folder and connection to the room server URL. However the pair has since been moved or deleted, so I am unable to link it directly to you.
I had this problem (ROCK downgraded itself to 1.8)
I fixed it by installing the legacy 1.8 remote, connecting to the core, then going to the settings/about screen - thats what prompted it to update again to 2.0.
I have an Intel NUC8i5BEH Core i5 that I bought in September 2019 running Version 1.8 (build 1126). I have carefully followed the instructions located on the “Roon 1.8 <-> 2.0 Migration FAQ” from the Knowledge Base marked as “RoonOS Core 2.0 (Nucleus / ROCK)” from the "How do I move to Roon 2.0 from Roon 1.8? " section and the Roon Core still remains on version 1.8.
I have repeated the process several times and restarted the Roon Server or rebooting the Intel NUC several times too and after all that it still remains on version 1.8.
Screenshots do not say anything new as you can see.
I just attempted the 1.8 Legacy → 2.0 migration process on ROCK (Intel NUC8i5BEH Core i5). Here it is the steps I have done:
I removed from “Data/branches” folder the old version of the downloaded “roon” file, named “roon_2-0” when downloaded.
Before trying to download again the “roon_2-0” file from the server, named it “roon” and copied on “Data/branches” folder so this folder remained empty, I went to the Roon Core Web UI to stop the Roon Server software when I have noticed that “Version 2.0 (build 1128) production” was already running so I did not proceed stopping the Roon Server software and followed as described.
I removed the old version of the Roon App from my MacBook Pro, downloaded again the Roon App from RoonLabs web site and installed.
Started the Roon App on my MacBook Pro, connected to the Roon Core and it is working like a charm! Roon Core running with Version 2.0 (build 1128) and my Mac (remote device) with Version 2.0 (build 1128).
Thanks a lot! Finally this issue have been resolved in my case. What about you guys?
Thank you for the reports here and we apologize for the inconvenience.
We’ve identified an issue with our update server erroneously serving 1.8 Legacy builds when it was not supposed to, and have since corrected this behavior.
For those who have already been downgraded to Legacy 1.8 and wish to re-install Roon 2.0 on their Cores, please follow the 2.0 migration guide on our knowledge base, linked below.
1.8 Legacy is compatible with 2.0, so your Roon database should remain intact. If you encounter any further issues after following the guide, please start a new support topic and let us know, thank you!