I’m getting the same issues constantly for the last 2-3 days, regardless of media file.
I’ll be able to play the media for about 2-3min then it throws this error, restart, rinse & repeat.
Just happened 10min ago (10:13pm 7/14)
Plex Media Server Logs_2018-07-14_22-11-25.zip (2.3 MB)
Just updated to beta 1.13.4.5251 and I’m still getting this error "Playback was terminated by the server - Conversion Failed. The transcoder excited due to an error. The issue occurred at 12:06 AM and 12:08 AM on 7-15-18. I’m using an Apple TV 4K with App version 1.29(9554). Plex Media Server Logs_2018-07-15_00-09-42.zip (2.1 MB)
Solved my problem. I have used the following PMS versions on Windows 10:
1.12.3.4973-215c28d86
1.13.2.5154-fd05be322
1.13.4.5251-2e6e8f841
They all present the same error. Since this is very widespread after a recent Windows patch, it’s partly to blame. The issue starts with updating your Windows 10 to OS Build 17134.165. This is patch KB4338819 released on June 10th, and targeted systems on June 11th. If you are unlucky and unable to use Plex with any of the versions (some users down/upgraded versions and have no issues), there is a solution. Unfortunately Windows no longer offers the ability to rollback these types of updates through the Settings UI. You instead have to use command prompt or Windows Restore.
WARNING! Proceed at your own risk. You must have administrator rights on the target machine. These instructions are provided as a suggestion only. You do not have to follow them. In the event your system becomes unstable or has data loss, only you are responsible. If you can wait for a fix from Plex, do so. If you must have access to Plex now, continue.
Command Prompt WUSA (Recommended)
winver and press enter to ensure you are on Build 17134.165wusa /uninstall /kb:4338819
Windows Restore Method (Alternative):
!!Any changes you have made to Windows or programs you have installed will reverted or removed!!
winver and press enter to ensure you are on Build 17134.165rstrui and press enter.When Plex has released an update, turn off defer/pause updates and install any updates pending. This is only a temporary fix for myself because I have family who lives hundreds of miles away that uses my server. It’s been annoying to myself and them for the last few days. Finally we are able to watch again.
Edit: Wanted to clarify this only applies if you are Windows 10 using the most recent version of PMS. I see multiple replies from people saying it started happening only the past few days. This was my solution as that’s all that has changed on my system.
Edit 2: Updates to this post here -> [Windows 10 Update KB4338819 issue] Conversion Failed. The transcoder exited due to an error
Rolling back Windows is NOT a solution. It is just a temporary fix that may cause security risks or other issues. However, it did confirm my suspicions that this error was instigated by the most recent Windows 10 update.
@sa2000 Has the dev team started exploring this connection to the update? Its been 5 days for me where plex is completely unusable. Seems like as more and more people update windows, the larger this problem will grow
I explicitly stated that in my post. Did you read it all or just glance over it?
There is always a security risks for pausing updates. This is common knowledge for any software. So it goes without saying.
I did not mean any offense. I know you stated that, but I was just trying to highlight that it should be unreasonable for plex to expect people to roll back Windows, i.e. they have to diagnose the conflict and fix it ASAP.
Sorry, I could have been more tactful in the phrasing.
Thanks for posting this. Although a temporary solution, it’s up to the user to decide if they want to take the risk and you made that clear. I wish people wouldn’t discourage these kinds of posts because they are helpful for those of us that are comfortable with taking the risk. I don’t run much on my server other than media, so I don’t really care. I’ve removed the update and so far so good. I’ll report back after a little more time has passed to see if the error resurfaces it not. Hopefully Plex can figure out the cause of this soon because it’s basically broken their software for Windows users.
Here are the logs
Plex Media Server Logs_2018-07-15_15-47-51.zip (2.5 MB)
Server Version: 1.13.2.5154
Totally understandable. It’s always better to solve the problem correctly than it is to just MacGyver your way through it.
Same. It’s back to normal since removing the update. I can wait it out like this until an official fix.
I’m not advocating, but I will say that cbabb’s solution of removing KB4338819 did SEEM fix the issue. Still testing but going on a day of no more problems, when before I could get it to happen on three or four files within minutes.
If anyone is curious what this KB does information can be found here: https://support.microsoft.com/en-ca/help/4338819/windows-10-update-kb4338819
Remember, this is removing a SECURITY patch. Own risk, blagh blah.
Hopefully the plex team sees this and it helps them resolve the issue for people similarly affected.
Yep, seems to have fixed the problem for me too. I’ve tested Live TV, recordings and media from my library and have had no issues after a few hours of use.
Plex Media Server Logs_2018-07-16_00-40-51.zip (1.6 MB)
My logs are attached above, along with my separate post here.
Worth noting that I haven’t yet done the Windows Update uninstall as per the above-suggested fix from cbabb, but if the Plex team finds no other cause in my logs, I intend to do so as my use-case for Plex is daily.
Any response from Plex support would be greatly appreciated!
@sa2000 Any update on this? As many people mentioned, Plex is basically useless if you are using Windows for the PMS. I personally am hesitant to roll back the Windows update due to it being a security update, but we are approaching 1 week since the issue started, and there is still no indication from Plex if they are aware of this sudden incompatibility with Windows and if they are close to fixing it.
This cant be a sudden incompatibility with windows
I am using the latest update (and i am sure many others will be) and have no issues
Hope you guys get the issue fixed, but this is not a general issue of it being broken for all windows users with the latest update
Do you have KB4338819 installed on the machine running PMS? Just curious since it seems to be the culprit based on this thread, but it would be useful to know if that in itself is not the case.
I do yes, no issues that i have noticed
As most users are using PS4 we are trying to reproduce the error using this platform. Unfortunately, it does need some complex diagnostics - like pcap capture of loopback - whilst the windows 10 update seems to be a factor, we have one user with Windows 7 SP1 with same errors
Of the 18 users reporting transcoder errors, i have gone through the logs from 8 users and appear to be all the same - with 4 using PS4, 2 Apple TV and one Google Pixel and one XBox One. Will see if we can get it reproduced with a PS4
