Thank you so much for this!!! This totally resolved the problem for me. I uninstalled the last Windows update and turned off the Windows Update option on my WIN 10 PC and now Plex works again. I’ll be sure to recheck periodically to see when Plex fixes everything and then change everything back, but for now everything is peachy!!
Hi sa2000,
Just touching base to make sure you saw my log files and details above. My source is, likewise, PMS running on Win10 64-bit, but my destination devices are an Nvidia Shield and a Chromecast Ultra.
If you get a chance to review them, please do let me know what you think. Thank you!
1 Like
For now, the solution I have found is to use Emby until they solve the problem, I hope they solve it soon. Sorry for my english I’m using a translator.
Yes Thanks. I have looked at the logs and i can see same errors when streaming to Nvidia Shield TV
It’s partly to blame for some of us. I can definitely tell you a Windows 10 update in the past year has caused seemingly unrelated programs to just stop. Of course, I do believe it is related to hardware of some sort. It’s interesting. World of Warcraft stopped working once and spit out a 3D error. I went to the Nvidia support forums and found out the driver was broken as a result of a Windows Update. Nvidia released a fix a few days later.
Other users have tried that and it worked for them. But like I said in the temp fix, it didn’t work for others. Your setup is a factor.
If anyone is comfortable with running SysInternals Process Monitor and capture all events leading up to the failure, i would like to see what is recorded in procmon for requests like this which are failing
http://127.0.0.1:32400/video/:/transcode/session/dd835b07f4b4f2f0-com-plexapp-android/84b8945e-91d4-4ccc-8f96-07ab989071e0/seglist
An unfiltered procmon capture saved as PML together with debug and verbose Plex Media Server logging enabled - could shed some light - whilst we are waiting for the development team to reproduce the error
If happy to do that and can reproduce the error soon after streaming starts (procmon gobbles a lot of resources - do not want to leave it running for more than 5 or 10 minutes max) - then please download it from
Enable both verbose and debug logging on Plex Media Server (settings / server / general /show advanced)
Restart Plex Media Server
Launch procmon.exe with Run As Administrator
Start a transcode that you know would fail in this way
and when the error arises, stop procmon capture
make sure there is no filter of events
Save all events as PML
zip and upload to dropbox or similar service.
Send me a link by private message
download the server logs and post here or send to me with the link to the zipped PML file
Thanks
I agree it is partly to blame, something in the update had caused issues somewhere, which hopefully now the plex guys are digging into it they can find the cause
My comment was more aimed at the messages that the Windows Update makes PMS incompatible with Windows
Is the team unable to reproduce this problem on their end?
Hi
I’ll provide you my log once I get back to home.
Plex server on windows 10 + Chromecast
Crash every 5min no matter what is the file.
For now I use VLC to stream to Chromecast, and it’s perfect.
I have had this error happen on webos, Android, PS4, Xbox One, and the Windows PMP on same machine as PMS as well.
correct. So far not been reproducible running on same OS build
Related? or no? I don’t want to hijack this thread with my own issue:
@Bsmcclure @martintzonev @Devlinpc @aadnieuw @rg9400
any chance of a video clip that gives this error on the PS4 / XBox One?
Plus playback settings / wan or lan / and also server transcoder settings (you could export registry to text file and send me text file by PM)
Exporting to text file
HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server
No. It is not
Good to know. I feel as though running the Windows Security Update rollback may be my only way to troubleshoot in a time-efficient manner, no? Can you advise if the team has any ETA on an update that circumvents the issue?
Consider using other versions of PMS first. If you have tried using other versions of PMS, you can try it. It’s worked for a few people.
@sa2000 I’m going to apply the update again and run through some other options to see what I get. I have hardware acceleration turned on. I can turn that off and try streaming. All the drivers on my system are up-to-date.
Add me to the list of people suddenly getting this error. Been using Plex daily for years and not had this issue until now, shortly after I updated my Windows. Confirmed I am on the current Windows build. All attempted remote playback results in this error–tried via a Samsung TV app, and iOS app w/wifi turned off.
Since we’re not sure yet (from my scan of the post, anyway) what part of the system the Windows update has broken (specific hardware, etc), here’s my set-up that IS having the problem.
The drives I use for Plex are all mirrored with Windows Storage Space, split up and combined into 4 different virtual drives (12 total physical drives).
Some drives are connected within the PC via SATA, some are connected via USB to a MediaSonic Probox server. The issue happens both with internal PC drives and the server box.
"Repair"ing the install appears to have fixed the problem for me. Couldn’t get more than a minute or two into a video before without the error popping before, now I just watched about 10 mins with no problem. Will update if the error comes back.
Just shot you a PM w/ the zip of my logs as well as the text of that registry key.
I’ve had multiple users experiencing this issue on my server but have not yet experienced it myself (I use PS4 locally), so far all issues have been remote users.
I have not yet uninstalled the Windows 10 update that some claim impacted this. I’d be happy to do more testing, get more info from users, and give you any details/logs info from ProcMon.
if i restart de plex server, all my clients works well again for a few hours.
How i can captura then?
