Soon as I did, boom, up came all four windows for EncodingServer.įWIW I also think that I had problems with my browser (Brave) at one point, but I changed a lot of flags in there and now there are no issues with EncodingServer, even with Brave running. I messed around in there with settings but absolutely could not fix this without completely stopping and disabling those services. The services above appear to be related to the nVIDIA GeForce experience app that is installed by default with the GeForce drivers. I have a Ryzen 9 3950X (but had an I7 4-core before, same issue) and a GTX1080. NVIDIA Display Container LS (this is the prime culprit).Tried clean boots via msconfig and all of a sudden EncodingServer started working again and that's when I knew it was something I was running that was preventing proper operation.īy a process of elimination I have discovered that two Nvidia services kill the ability for EncodingServer.exe to bring up a window and/or commence work. I read about something like this in previous posts on this thread and have tried reinstalling the VC redistributables, it did not help at all. But it simply wouldn't on my main desktop. I have a few other machines here and on each of those, the EncodingServer app would start fine. It was the absolute most frustrating thing for me and I tried dozens of things to try and fix it. The client window appears, and four (which is what I use) EncodingServer.exe instances appear as tasks, but their WINDOWS do not appear and work does not commence. The problem was simply that starting a Ripbot encode did NOT trigger the startup of any EncodingServers. Wanted to drop this off here just in case someone has ever experienced the same issue I did in recent months.
0 kommentar(er)
