That's what a lot of people here on the forum thought too.
I was sure it had to be the Windows Defender Firewall settings SOMEHOW. The UMS Service could see the TV, and could even control the TV Volume so I was baffled as to how this could break down so annoyingly. I immediately jumped to the foregone conclusion that either the Windows 10 update, or the Java Update or BOTH had corrupted ONE THING that worked well in this hoaky home network! Then I stayed up late into the early hours trying things to get the UMS server connection working again. I hadn't used it since the Windows 10 Update. I tell you all that to illustrate how convoluted a home Windows System upkeep can seem, and (spoiler alert) to show how easy it is for apparent complexities of the Windows 10 system to cast a dark shadow and confuse what are otherwise not so difficult problems.Īs it happens, last night, I discovered that the TV could NOT find the UMS DLNA service. 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. Greetings! I am so relieved to get this problem FIXED that I want to post it for any other unfortunates who may be impacted.
0 kommentar(er)
