I recently update ROON and now Windows Defender (Windows 10) is blocking RAATserver. I have never seen this before. ROON is at Version 2.0 build 1483.
Have you had a recent Windows update, possibly some changes there?
Is the Network set to public or Private?
Just click “Allow Access”?
I am not aware of a recent Windows update, though that sometimes happens automatically in the night while the computer & I are both sleeping.
My Windows 10 is at Build 19045. That has been out for a couple of years now.
I currently only use it on the private network in my house (though it obviously pulls information across the internet about loaded recordings from the ROON databases in the sky.
I am interested in getting ARC to work, but I don’t have enough time right now to devote to that project.
I was concerned that, if there was some identified security exposure, that even though my music streaming is only within my private network, that allowing it would create a security exposure through the router to the broader public network (ROON does grab information through the public Internet).
The question is just whether the Roon application’s RAAT traffic is allowed through the firewall of the Windows machine. This is only the streaming protocol Roon uses between Roon server and endpoints, it has nothing to do with the internet.
It’s not unheard of that Windows sometimes changes/loses settings randomly and you have to redo them.
Given your explanation that this component is a communications component that handles the streaming of music (with one RAATserver instance at each end of the communication) -
I experimented with what would happen if I did not enable the RAATserver on this Window machine which I sometimes use as a control point, but is not a ROON server.
Turns out that the only function it impacted was the ability to use this computer as a System Output (Endpoint) device. I rarely do that, so I can safely not enable it. All other selections for System Output work just fine.
Thanks for all responses.
From the screenshot, it looks like Windows thinks that you are on a public network (it does say that Roon had already been allowed in private networks).
Windows does get confused about this often enough, and if anything had changed with how that particular PC connects to the network, it will default to Public.
Assuming that the computer actually is on your home LAN, just configure the network connection as Private, and everything should be back to normal.
2 Likes
There was one last week , you may have inadvertently accepted it by restarting your PC , the update is applied by rebooting . You get a small icon in the tray RHS bottom and it modifies the restart shutdown options . all quite normal stuff for Windows
The Firewall warning is quite normal and may appear after an update , this one did require permission. just click Allow Access and you are away. I suspect it depend on what the update includes.
2 Likes