Roon no longer starts after 10 days of non-use [Solved - Port issue due to WiFi + Transfer program]

[noris]

Hi @Stephane ,

Thanks for your patience here while @beka flagged me and for the other users chiming in with some very helpful suggestions so far!

@Stephane

04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 169.254.187.211:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée
04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 192.168.1.21:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée
04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 127.0.0.1:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée

I do recall a few similar cases with these error messages. Some of the time this was triggered by Windows updates, but for other users it was due to a program called Wifi + Transfer:

Roon core won't open, logo just does its thing endlessy

HI, no worries… I have now managed to get it working in the meantime! So, i discovered that Nero had installed a nasty program called WiFi + Transfer. Going on Chris’s idea that it was a networking thing, i removed it. And hey presto, it started up immediately. I assume this was the problem. Thanks for the suggestions Rebeka. All good now…

Roon First Sign-in - Sits and spins forever [Solved - WiFi+ Transfer App Conflict]

@dylan - Well, what do you know! I do have Nero installed, and WiFi+ Transfer was running at startup. It’s actually one of the startup things that I sometimes kill after startup, but hadn’t done for a while. I’ve removed it from Windows startup permanently, and Roon ran immediately. So now I’m in business, and able to try the software out. Thanks for your help, and for figuring this one out. (Now crossing my fingers that I can re-enable Hyper-V as long as I make sure I don’t let it configure its…

Do you by any chance have this app? It might be interfering with Roon starting due to this port conflict. If you don’t have this app, then I’d advise running Windows Advanced Port Scanner and see if another program is using port 1900:

Advanced Port Scanner – free and fast port scanner

Also, while this doesn’t help your case at the present moment, I do want to mention that we are investigating this type of hang on the QA side to see what improvements we can make in this area.