



This issue is typically occurred right after the user upgrades to Windows 10 from an older version or after they install a big cumulative update such as Creators Update or Anniversary update. PS3 Media Server not finding any renderers

The Ps3 media server media renderer was not recognized error is reported to re-occur even if the user restarts the server or reboots the machine. Affected users report that the PS3 Media Server program is searching for renderers on a loop without identifying the PS3 console. This may have been due to exiting while the program was still scanning folders when the media library was still enabled, but it's stupid Java, so who knows.Some Windows users have reported that their streaming (done through PS3 Media Server) has suddenly stopped working. One time so far the javaw.exe process stayed stuck in memory on exit, consuming over a GB of RAM. And it doesn't mention that the server has to be restarted to recognize this change. I had to disable transcoding of mp4 and others, because it was transcoding most files even though my WDTVLive device supports them directly just fine. I disabled and forego the media library to avoid this. Only caveats I've found: - The database size it creates for a modest media library it rather large, and takes forever to scan. But the program is nicely configurable, and does work rather well. Well, it's still a thing made with yucky Java, but at least now it includes its own runtime of it, so there's no ancient security risk, system polluting, full Java install required anymore! Of course, being Java, it's a RAM, CPU, and disk space hog.
