Please help me find any logic in that message… ![]()
That shows up at every Remote launch on Windows 10.
My guess is that are running production with early access, and these aren’t compatible at present.
Nope:

Then, I don’t know why. Maybe reboot core and remotes?
I tried that, no change.
After a few (5-30) seconds that message disappears and Remote starts.
I had similar experience yesterday connecting an Android tablet
I’ve noticed also that before dismissal of this message there is a check for update of Remote being performed:
And surprisingly the result is the same as before check
Hi, @Piotr_Pekala, thank you for your report! Could you, please, use the directions found here and send over a set of logs from your Windows remote affected by this behaviour to our File Uploader?
Thanks!
–
Ivan
done
/10char
Thanks, @Piotr_Pekala. I’ve examined your logs and it looks a lot of them end with a crash trace. Have you seen your Roon app crashing a lot recently?
–
Ivan
@alec_eiffel, could you, please, launch Roon Remote app on the affected device? I am going to send a request for the remote diagnostics report. By any chance, do you remember an approximate timestamp when this issue occurred on your end?
Thanks!
–
Ivan
Yes - that’s also a new “feature” of this build.
I haven’t reported it yet because I don’t understand when it’s happening. Sometimes 5-10 consecutive attempts to run Remote fail (at different stage) before it actually start and sometimes it starts many times in row successfully.
I had some hypothesis but none of them confirmed.
It’s (re-)started now without crashes.
“Software update needed” appears at every Remote launch. During last 10-15 minutes at least twice.
I don’t remember the exact crash times - but it happened many times yesterday between 19:00-22:00 CET.
Understood, thank you. Another quick question, have you seen this issue on any other of your remotes?
Thanks!
–
Ivan
Nope. The second one I’m frequently using (Android) works without any problems.
The others are used infrequently and may have not been used in that build at all.
Hi, @alec_eiffel, @Piotr_Pekala, we have just released a build with potential fixes for both the crash and the false positive “Software update needed” screen. Could you, please, update to the latest Early Access build and check if you are still experiencing issue described in this thread?
Thanks!
–
Ivan
So far it looks good with the latest build ![]()