Hello @Olaf
Two tests, and please do them in this order. The first is quick and may settle it on its own.
1. Properly remove the Roon app on your Windows 11 laptop, including its data.
This is not the same as what you have already done. Uninstalling Roon on Windows leaves its data folder behind, so reinstalling picks the old state straight back up. That folder holds the flags that record whether the app has been through the setup screens, which is very likely why your reinstalls changed nothing.
Please do this:
- Uninstall Roon through Settings, then Apps.
- Press Windows and R together, paste
%localappdata% and press Enter.
- Delete the folder named Roon.
- If you see a folder named RoonServer, leave it alone. Your server is the ZEN Mini and that folder is not it, but there is no reason to touch it.
- Reinstall Roon and connect to the ZEN Mini.
Then open and close Roon a few times and tell us whether the setup screens still appear every time.
Your iPhone and iPad do not need this. Deleting an app on iOS removes its data with it, so those were already clean.
2. Only if the setup screens still appear: a genuinely empty server database, with no restore.
Last time you created a new RoonServer folder and then restored your old backup into it. If the problem travels in the backup, restoring it puts the problem straight back. So this time, rename the RoonServer folder aside, let an empty one be created, and connect without restoring anything.
Your library will be empty and you will go through setup once. That is expected and temporary, and your old folder is still there so nothing is lost.
What we want from that is one answer: does it stop asking you to set up on every connection?
If it stops, the problem was in your database. If it still asks every single time on an empty database, then it is not the database at all, and it means the ZEN Mini cannot save the server’s own state to disk. That would fit everything, including why nothing has stuck and why this began with a power outage, and on an Innuos unit that becomes theirs rather than ours. We would tell you that plainly rather than keep you testing.
Please leave the DAC error aside until we have the answer to test one. We will come back to it and we do not want two changes in flight at once.