

but I did wonder if any Java packages would be affected. didn't pay too much attention) but then got a warning that I should PURGE older Java versions, which I declined, since I think they can usually run side by side. I let it happen overnight, like a good Windows user! A few days earlier (I recall) giving permission for JAVA to update in the Java 8 family (my fault. Windows 10 announces that it needs to UPDATE my installation to version 1903 since 'support is ending' for my version. Serving from a Windows 10 system to a Samsung 46C670 TV. Scenario: Happy UMS user for a few years. So, the 10.20.0 log represents the situation when UMS failed and when the 10.19.0 log was created everything worked fine again.ĭropdown_10.20.0.JPG (16.1 KiB) Viewed 5510 times ums_dbg_-08-34_version 10.19.0.zip (58.57 KiB) Downloaded 120 times ums_dbg_-08-29_version 10.20.0.zip (61.Greetings! I am so relieved to get this problem FIXED that I want to post it for any other unfortunates who may be impacted. I created Trace Logs, both for version 10.20.0 and (after overwriting the 10.20.0 installation with 10.19.0) also for version 10.19.0. Renderers can be selected again, and BubbleUPnP (and the direct connection with my Sangean) can connect to UMS. I eventually reinstalled 10.19.0 (without uninstalling 10.20.0, so overwriting the 10.20.0 installation) and everything worked fine again. Then I did a clean install of 10.20.0, but same problem: again the "Unknown renderer" in the pulldown menu (which is the sole entry), the same error message in BubbleUPnP above and the Sangean can still not connect. Next thing I did was completely remove UMS, I also deleted the folders \Universal Media Server and \UMS. The UMS server is visible, but selecting it result in an error.

The Sangean WFT-3 also couldn't connect anymore to UMS (which always worked with 10.19.0). Unexpected token (position: TEXT Failure: 500 :35 in ). Can't transform message payload: 1.XmlPullParserException:

Reason: Current state of service prevents invoking that action.
