Nucleus rolled back to 1.8 automatically after running with zero issues since release 2.0

[Rugby (aka Daniel or Big Dan)]

As Geoff said, being investigated, official notice linked

Why did Roon spontaneously revert itself from Roon 2.0 to 1.8? [Fixed: Update Server Error, Update To v2.0 Using Migration FAQ]

Hello All, 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.…