I, a fellow Roon user understand the frustration you may have. Roon have quickly discovered a workaround for those happy to give it a try. They have acknowledged the issue and will no doubt be working frantically on a reissue to the 1167 or newer update to correct the error.
The clear instructions @ivan has given has helped a lot so far. A link to an instructions page is also included.
I think Roon are doing a great job at tackling probably their worst nightmare, a software update failure. This will however work towards finding said issue, putting control measures in place to prevent reoccurrence. Whilst this all worked fine in their testing, a simple error pushing the update out to us has probably been the issue.
@danny is probably leading his team accordingly and may issue an explanation.
Let’s face it folks, things can break.
My car has and it’s in the garage. Did I want it to break, heck no. It’s life.
Edit/update: