You must have learned your trade at Bletchley Park…
2 Likes
During my absence I absolutely did not cut the electricity meter.
I just shut down my PC.
Everything else works perfectly fine and by the way I am writing to you using this PC which is running Windows 11.
Also, if you read my previous posts carefully you will find that before I encountered the Merging driver problem I I could use the entire chain of my system from Foobar2000 and Tidal (through Google Chrome) on this PC.
I even took the liberty of attaching screenshots showing the proper functioning of the latter.
It’s not about the Roon server but just to start the Roon software on my PC.
My approach here is just to share and try to move things forward.
My little personal case basically interests me very little.
I really like Brittish humor but I’m not sure that in this case it is appropriate. Up to you…
But it is true that often our different cultures can lead to confusion between our different languages.
Besides, we really can’t hide anything from you because I will soon be going on vacation again!
And I’m not even sure I have time to reinstall Windows 10 Pro…
I totally agree with your sentence and that’s why I also contacted two of my very good friends who are computer scientists (two extra pairs of eyes instead of one…, they connected to my PC with TeamViewer) and one of whom was even specialized (he is now a young retiree) in computer networks and has spent a large part of his career in the United States.
These friends certainly do not come from Bletchley Park but only from the Ecole Centrale in Paris and the Ecole Polytechnique (X).
Maybe these profiles are too high but sorry they are my friends.
However, they are not really interested in musical software and installations.
I was also very grateful for the help I received from members of the Roon forum who I asked for help.
Have a good day !
2 Likes
Thank you Geof @Geoff_Coupe for all these explanations and insights. In Windows 11 odyssey
I just got the Merging Technologies hotline this morning and they allowed me to reinstall the Merging Audio Device (Merging RAVENNA/AES67 Vitual Audio Device Installer - 3.2.0 build 50895).
Many thanks to them!
This driver works correctly again on my PC, even if officially this one is not compatible with Windows 11.
On the other hand, software like Pyramix or Pro Tools does not yet work on Windows 11.
So I came back to the same starting point of the beginning of last week.
Roon’s log files reporting the same malfunctions.
You are right, although I find the members of the forum very sympathetic and undoubtedly competent on computer subjects in general, I will wait for Roon Support team to come back to me.
I continued to persevere in my attempts to install Roon.
And after the xth time, after having uninstalled then reinstalled the Windows 11 updates (is it the “Cargo Cult” ???) the installation was finally possible.
For all practical purposes I keep the Roon log files before (certifying that Roon does not work) and after (conclusive installation) in case the Roon Support team is interested in this scenario.
@Geoff_Coupe Tell me, Geoff.
@Roger_Staines I will finally be able to go on vacation again.
Thanks again everyone.
This incident can be closed.
3 Likes
Stephane I’m very happy for you that you will have music again with Roon.
Did you find out what the cause was though, just in case it happens again? 
Unfortunately, the joy was short-lived…
Last night after using Roon all day I restarted my PC (around 10:00 p.m. Paris time) to check that everything was in order and again Roon did not restart anymore.
When I woke up this morning, I still had the Roon splash screen.
Of course, I have all the log files from yesterday and this morning.
@Geoff_Coupe @Rugby @Beka This time I am waiting for help from Roon Support regarding the analysis of these log files and a solution to be able to use Roon again.
@Geoff_Coupe Also please reactivate this thread which should be closed within two days.
1 Like
I tried to install Roon 1.8 (build 933) and then Roon 1.8 (build 935).
No change. The problem remains the same.
@beka @support
I am still waiting for help from Roon Support regarding the analysis of these log files and a solution to be able to use Roon again.
I can of course send you my latest log files.
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!
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:
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:
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.
4 Likes
Thank you very much, Noris.
Now my problem is solved.
Just before you sent this message, there may have been thought transmission 
, I had just found the thread in which the problem of WiFi+ Transfer was mentioned and it was precisely the cause of Roon not working for me.
All this made me have a bad week all the same.
10 Likes
Glad to hear that it helped solve the issue, @Stephane ! I am curious as to why the issue just started following the Windows Update (assuming you had WiFi + Transfer installed before) but I’m hoping the rest of your week will be better with some music 
1 Like
Nothing to do with the Windows updates, it’s just what I thought while fearing the Cargo Cult effect, and it was.
I indeed very recently installed a software called Nero to make a CD copy for one of my friends and this Nero software also installed this WiFi+ Transfer which started when Windows starts.
Maybe when I just uninstalled the Windows updates, this disabled the start of the software WiFi+ Transfer, but as soon as I restart Windows, then WiFi+ Transfert started again.
Sorry for my poor English especially since it’s 2:09 am here in Paris 
5 Likes
It would be great to have a thread or Wiki page or something that listed these kinds of things – the symptoms and their causes – instead of having to re-find them every time.
3 Likes
Agree totally about the Wiki, but documentation efforts are always left to the weak sister.
I imagine there’s a Knowledge Base editor somewhere reading these posts.
The goal here is not to document these kinds of issues, but to fix them outright. As I mentioned earlier in the thread:
But meanwhile… Though, if it’s some other software causing the problem, I don’t really see how you can “fix it outright”.
Here it seems that the other software at Windows startup binds to its preferred port 1900, which is also used by Roon, which then throws an exception and hangs when the user tries to start the application.
As @Stephane was able at one time to start Roon after several reinstallation attempts, it seems as if the other software had some kind of fail-over mechanism and can bind to an alternative port, if at startup it finds it can’t connect to port 1900.
Roon could implement a similar fail-over mechanism and so prevent this thing from happening again. This would also take care of other software products possibly out there which use port 1900.
As for ports, please see this post