#1 MU1 display keeps showing “Starting Roon…”
Make sure to have the latest MU1 firmware installed. If you do run the latest firmware, use the main knob to enter the menu and scroll to menu 2. Check in the bottom right corner if the MU1 has an IP address. If the MU1 does not have an IP address: check the network cable connection. Unplug it from the MU1 and plug it back in. Check the other end of the cable as well. Reboot your router.
If the MU1 does have an IP address, wait for a few minutes. Roon may need up to 2 minutes to boot. If Roon still does not start, restart the MU1. If that does not lead to success, please open the GRUI web interface. Go to the MU1 settings, open the tab Advanced and then first click the Stop Roon Server button, wait for 30 seconds and then the Start Roon Server button. Wait for a few minutes to let Roon startup. If this does not solve the problem, try stopping and starting the Roon Server a second time.
If these measures do not solve the problem, you may try to reset the Roon database. Please note you will then loose all your playlists, local favorite data, and manually edited metadata.
We recommend to make a backup of your Roon database before you do the reset so you can restore all that information. Of course there is a chance that you then restore the problem too. Restoring an older backup might help in that case.
To proceed, follow these steps:
1. Make a Roon backup using the Roon backup tool, see the Roon backup manual and our backup manual for information how to do this.
2. Reset the Roon database through the GRUI, the web interface of the MU1. You can find this web interface using the hostname, IP or QR code as described in the MU1 software manual. On the GRUI page, press the “MU1” cogwheel button. Go to “advanced” and click, “Reset Roon database”. Confirm in the popup.
3. Restart the Roon remote app of your mobile device or tablet.
4. Login with your Roon credentials and run through the setup as if it’s the first time. Do not forget to activate the extension via Roon -> Settings -> Extensions -> Enable.
If Roon still does not power up, please contact us via the support form of our website.
#2 Cannot login to Roon after database reset.
After you performed a database reset you cannot login to Roon. Instead you are forwarded to the Roon login page. After returning to the Roon remote there is no response.
To resolve this issue, please update your MU1 to firmware version V1.5.8 or higher.
#3 MU1 stuck during update.
In case your MU1 display blanks, freezes or shows a white screen for more than 30 minutes during the update process, please unplug the power cable and plug it back in. The software is built in such a way that if the process did not finish correctly, it will restart the update procedure after a power cycle.
Please make sure to not unplug a seemingly frozen unit within a period of 30 minutes after starting the update. It may still be busy with programming. So, note the time when you start the update process.
#4 MU1 internal drive not visible under Windows.
In some cases the MU1 internal SSD drive is not visible under Windows 10. The reason is that the ‘Bonjour’ service is not installed by default under Windows. Bonjour is used for so called zero-configuration networking, and it enables automatic discovery of devices such as the MU1. It will then show up in the Network File Explorer section of Windows 10 as a named network entity like ‘MU1-00xxxx’.
Solution: First you need to install the ‘Bonjour Print Services’. A download can be found by following this link from Apple.
Next you need to enable ‘SMBv1’. Unfortunately in Windows 10 the SMBv1 protocol is disabled by default as Microsoft sees it as a security risk. Mark that this risk does not apply for the MU1 due to the way it is set up.
If you are running Windows 10 Pro, Education or Enterprise you may need to adjust your Windows security settings. More information can be found here.
Please follow the steps in the work instruction pdf below to install Bonjour and to enable SMBv1. Note that with every Windows 10 update the SMBv1 protocol may be disabled again. In that case please follow the work instruction again.
