Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· App interface looks or behaves oddly
Tell us what's going on
· ROON does't
Tell us about your home network
· ROON doesn;t respond !?
· None of the above quite fits
· App interface looks or behaves oddly
· ROON does't
· ROON doesn;t respond !?
Hello @Vancho_Kolev,
Welcome to the Roon Community
— and thanks for reaching out.
At the moment, there isn’t enough information in the post for us to understand what’s going wrong. When you say “Roon doesn’t respond” or “doesn’t provide expected functionality”, this can mean several very different things.
Could you please clarify the following so we can help effectively:
Once we have a bit more detail, we can point you in the right direction or start proper troubleshooting.
Looking forward to your reply, and happy holidays ![]()
Hello @Vadim,
I am using Roon for Windows PC ( HP Spectre !5 ) as a yearly subscriber.
All three apps ( Robin Server, Roon Roon bridge ) are unresponsive.
Roon stopped after the update.
Hope this information is helpful.
Merry Christmas and Happy New Year.
Hello @Vancho_Kolev,
Thank you for the clarification.
First, just to clear up one point: on Windows there is no longer a separate Roon Server / Roon Bridge installation. Everything is installed and managed as a single Roon package, so that part is expected behavior.
Based on the diagnostic logs we have, RoonServer itself is actually starting and running correctly on your system. For example, we can see the following entries:
12/31 16:23:54 Info: Starting RoonServer v2.57 (build 1598) production on windows
12/31 16:23:54 Info: Local time is 31.12.2025 16:23:54, UTC time is 31.12.2025 15:23:54
12/31 16:23:54 Trace: [roondns] loaded 41 last-known-good entries
12/31 16:23:54 Debug: Init DefaultBackingApi: HttpWebRequest
12/31 16:23:54 Debug: [easyhttp] default backing API HttpClient -> HttpWebRequest. This may cancel all in progress http requests
12/31 16:23:54 Trace: Checking if we are already running
12/31 16:23:54 Trace: Nope, we are the only one running
12/31 16:23:54 Info: Is 64 bit? True
12/31 16:23:56 Info: [stats] 2102006mb Virtual, 43mb Physical, 2mb Managed, 41mb estimated Unmanaged, 367 Handles, 19 Threads, 0% of runtime in GC pauses, 0ms last GC pause duration
12/31 16:23:56 Trace: [orbit] init seq=0, pending=0, spcount=8, uidcount=2
12/31 16:23:56 Trace: [realtime] fetching time from NTP server
12/31 16:23:56 Trace: [realtime] Got time from NTP: 31.12.2025 15:23:56 UTC (3976183436420ms)
12/31 16:23:56 Trace: [realtime] Updated clock skew to 00:00:00.1593201 (159,3201ms)
12/31 16:23:57 Trace: [ipaddresses] enumerating addresses
12/31 16:23:57 Trace: [ipaddresses] SKIPPED Local Area Connection* 1: not up
12/31 16:23:57 Trace: [ipaddresses] FOUND WiFi 192.168.100.112
12/31 16:23:57 Trace: [ipaddresses] SKIPPED Bluetooth Network Connection: not up
12/31 16:23:57 Trace: [ipaddresses] FOUND Loopback Pseudo-Interface 1 127.0.0.1
12/31 16:23:57 Info: [broker] starting 55f64448-276e-4860-950b-43fe5c4b4812
12/31 16:24:01 Trace: [httpcache] loaded 2120 cache entries from C:\Users\Vanco Kolev\AppData\Local\RoonServer\Cache\httpcache_2.db, current: 30mb / 128mb
This indicates that the server process is launching normally after the update.
When Roon appears “unresponsive” after an update on Windows, the most common cause is a stuck or orphaned Roon process left behind during the update, which prevents the UI from attaching correctly.
In most cases, this fully resolves post-update unresponsiveness on Windows.
If the issue persists after a clean reboot, please let us know:
We’ll be happy to continue from there.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.