Success! The trick indeed was the folder name related to the root file having a UUID. Finally im getting to experience Roon through the Nucleus One. Have also managed to do a manual backup from there and will run a scheduled one starting this weekend.
Thanks so much to you Benjamin and Alex for all your patient advice through the last couple of months. It’s been very much appreciated and I’m so glad a solution was finally reached.
Just as a quick thought: in the general Roon Manual instructions, might be useful to add in there something about the importance of the UUID / not changing the backup folder names, and the need for parallel hierarchy level presence within the Backups storage folder of the root file. Could save both you and also other users some unnecessary (di)stress.
My one last issue is the apparent inability of Windows 11 to show the Nucleus One device being present on the network. It’s obviously there because otherwise nothing would work, and I can also ping it.
I’ve read some material on the Net suggested W11 and W10 can be a bit flaky in “recognising” devices. Have tried all sorts of solutions including sharing permissions, Group Editor permissions and similar, and have enabled many options suggested. Still N One apparently “invisible”. Any further possible things you can suggest that I could try?
Just once again, thanks for all your help. I feel more in touch with some of the inner tech quirks of Roon after all this. Though I’m sure at times you guys were bemused by my tech “saviness”.
Thanks for the update @David_Carter, I’m so happy to hear you’ve been able to get your Nucleus up and running normally! I want to thank you equally for your time and patience while working through these issues, you’re absolutely right in that this process should be so difficult when attempting to set up a Nucleus for the first time.
We’ll absolutely share your feedback with our Nucleus team to ensure more clarity is added to the Nucleus manual.
For your Windows 11 connection issues, looking at Nucleus logs, it’s clear your Windows 11 machine and the Roon Nucleus are having a bit of a communication breakdown. Specifically, the phrases ConnectionReset and Connection refused are the smoking guns here.
Essentially, the Nucleus is trying to “talk” to your laptop (LAPTOP-58VBM2AM), but the laptop is either hanging up the phone immediately or refusing to take the call.
As a first step, let’s review your windows firewall settings. Windows 11 often treats Roon’s RAAT (Roon Advanced Audio Transport) as a threat.
The Fix: Go to Windows Settings > Privacy & Security > Windows Security > Firewall & network protection.
Select "Allow an app through firewall."
Ensure both Roon.exe and RAATServer.exe are checked for both Private and Public networks. If you don't see RAATServer, you'll need to add it manually (usually found in \AppData\Local\Roon\Application).
Let me know if this helps - if not, we may want to clear any stale cache from Roon on your windows and perform a completely fresh install.
Hello Benjamin. First more good news: the scheduled backup worked ok, so hopefully things will proceed in the same way going forward.
I looked into your suggestions about this “Network Discovery” issue with W11/Roon Nucleus One. I double-checked what I thought was the case: Roon and RAAT both allowed through the Norton Antivirus (and I “added” the single .exe files to the allowed list as well); A/V set to Public Firewall; no obvious blocking or exceptions at play; nothing in the Quarantined list; SMB1 enabled in the W11 Group Policy Editor rules.
In essence, whenever I call up the Roon Nucleus One interface in Chrome (or Mozillla, or Bing, or whatever browser) I see the same thing: a warning triangle and the message “Not Secure”. I can’t see how I can force Chrome to “accept” that this is a safe site. Perhaps that’s at the bottom of why the laptop keeps “hanging up the telephone” when Roon calls out to the Network?
Have had a look around at Roon chats and elsewhere, and two things keep coming back: 1) W11 has become more sniffy in past few months about security protocols; 2) Roon may be operating with http rather than https, and so there’s possibly an issue with SSL and other Certification being recognized by W11. No idea if there’s any substane to that: you tech chaps would know better.
I’ll soon be removing Norton A/V from the laptop when current licence expires, and so at that point can try to see if the behaviour changes when a) I just use Windows Defender; b) I install the new Bitdefender A/V. But as I said above, Roon and RAAT definitely showing “in the green” as something Norton A/V is happy to allow through.
Any further ideas appreciated: it’s not a showstopper this issue, more of an irritant and unusual behaviour. W11 has always been quite OK with making visible the Innuos Zen Mini / Roon combination on the laptop’s Network. Also looked at Network on a different laptop (also W11): same problem with no Nucleus One machine visibility.
Thank you for your patience throughout that process!
Regarding your ongoing Network Discovery issue on Windows 11, I can definitely help clarify a few things and suggest the next best steps.
The “Not Secure” Browser Warning Please don’t worry about this at all. This warning is completely normal behavior for all modern browsers (Chrome, Edge, Firefox, etc.) when you access a local IP address (like 192.168.x.x). Browsers expect websites to use HTTPS with an official SSL certificate. However, SSL certificates are issued for public domain names, not for private, local home network IP addresses. Because the web interface connects via standard HTTP, the browser flags it as “Not Secure.” This is perfectly safe since it’s entirely contained within your own home network, and it has no impact on Windows Network Discovery or RAAT communication.
Network Profile: Public vs. Private I noticed a crucial detail in your message: you mentioned “A/V set to Public Firewall”. This is very likely the root of the issue. In Windows, if your network connection is classified as a “Public” network, the operating system strictly disables Network Discovery and file sharing to protect your PC.
Action: Please check your Windows settings and ensure your home Wi-Fi or Ethernet connection is set to "Private network". (Settings > Network & internet > Wi-Fi or Ethernet > Network profile type > Select "Private").
3. Norton Antivirus / Firewall Third-party security suites like Norton are notorious for overriding Windows settings and blocking discovery protocols (like SMB or mDNS), even when specific .exe files are allowed.
Action: Before your license expires, as a quick diagnostic test, please try temporarily disabling Norton completely (both the Auto-Protect antivirus feature and the Smart Firewall). Once it is fully disabled, check if the Nucleus One suddenly appears in your Windows Network Explorer. If it does, we will know for sure that Norton's strict packet filtering was the culprit.
Let us know how the "Private" network switch and the temporary Norton disable go.
Thanks for those suggestions Alex, some of which I’d tried already myself, others of which I’d brushed across when searching on the Net for advice. As requested, I temporarily disabled those sections of the Norton A/V: made no difference to visibility on the Network of the Nucleus One. Likewise the switch of both Router and A/V from Public to Private network setting: I’d tried that before I’m fairly certain.
Let’s see if there’s any difference when I install Bit Defender A/V in a week or so instead of Norton. But I’ll make sure I try things also using the just in-built Windows Defender first, instead of a bought-in product. Will report back on how that goes.
Let us know how it goes after your additional changes. If you manage to connect to the WebUI for the Nucleus, we would suggest trying an OS Reinstall, as that might help.
Thanks Noris. Just FYI: after switch from Norton; then to Windows Defender; now to Bitdefender A/V… No change in explicit visibility of the Nucleus One on the list of Networked devices. However, I’ve now managed to pin the \\nucleus one\data folder to my quick accessibility links on the laptop.
So, I guess let’s stop this thread there: that’s “good enough” for me and ease of access to storage folders.
