As was noted in one of the earlier posts, “The issue starts with updating your Windows 10 to OS Build 17134.165.” It was a Windows update after that OS build that has fixed the problem for many users (myself included). For me, it wasn’t a matter of updating Plex that solved the problem.
can you please read some of the recent posts in this forum topic, The build of windows you mention is the one that introduced the bug
You are expected to read posts in forum threads and you are also expected to read the title of the forum thread you decide to post in
Apologies, I typically jump to the end of forum threads and read backwards; but found the endless scroll, rather than paged, nature of this forum does not make that easy to do. That there are seemingly dozens of similarly titled threads in the forum does not help. Perhaps you could consider some kind of pinned thread, or hot search result, showing latest status of an obviously hot issue like. It might prove helpful in guiding users.
Now that I know this thread holds the answer, if not the real fix, I will read back through it.
This is not related to a code change in PMS. It started occurring on my system, where I have PMS set to ask before updating, without my having approved a PMS update for some time. The only thing that could have changed then is Windows, which auto updated.
So given that I have 17134.165 there are at least two later Windows builds that might correct the problem? Somewhat unhelpful that Windows Update tells me that I am up to date then. Guess it’s time to Google for how to get later Windows updates when it thinks it’s already up to date.
It seems that Windows must not check for updates too regularly. Despite it saying I was up to date, clicking on the Check For Updates button resulted in it finding and installing some including KB4340917. It’s busy downloading and I must head off to work. Guess I will find out this evening whether the problem is resolved by these updates.
That is correct. If you want to force an update you can browse the update catalog.
In this case if you ever want to manually apply an update, you can use Windows Update Catalog.
Here is 4345421 Microsoft Update Catalog
Here is 4340917 Microsoft Update Catalog
Make sure you download the appropriate one and install them in order. These are standalone packages that are click-to-tun.
Windows checks every day. For reasons unknown (even back to XP days) an update that has been published won’t be downloaded unless the user clicks the button or updates manually.
Good thought. But, the viewing Windows 10 system in running build 1803
you responded to the wrong thread…but no matter
This issue is affecting version 1803…so this may be your issue
Your build should be 17134.167 or higher to get rid of this issue
The viewing system is at version 17134.165. That is as far as System Update has taken me in the x64 world.
As a side not: the streams play just fine at full bandwidth when played through the Plex.tv interface. It fails when using the Plex windows player at any bandwidth.
We aren’t concerned here with the viewing system - the system serving your content (that has plex media server installed) would be the issue
OK. Thx. I will apply these updates and give 'er another try
Since forcing the latest Windows updates the problem seems to be resolved. Have watched 6-7 hours without the problem recurring.
Since installing the 4340917 the plex media server no longer starts, hard to debug as while the EXE is running there are no logs being written. this is rather odd
check the registry area HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server and see if you have an entry for LocalAppDataPath and see if it is valid. It needs to be absolute directory path if set
If this is not the issue, you can try
- Repair installation of Plex Media Server
if this does not resolve it, one can you the Windows SysInternals Process Monitor to see what happens when Plex Media Server.exe is launched
Hi
Thanks for reply
Already confirmed in the registry the local appprata path is there.
Have tried a repair install and completely removed and reinstalled with defaults.
Will take a look at procmon later and will post any results if I find the issue.
Is there any use getting dumps of the process? Do we have access to symbols?
If there are any other suggestions I’d be open to them.
HI folks
found the error, the path for the localappdata had a space in the end of it
C:\Users~username\AppData\Local was in the registry key but there was a space at the end.
As this was a fresh install it must have come from the installer itself. Might be worth checking on the plex build side as i certainly didnt edit any options.
Will look into it but as far as I know the field is not created by default and only when the path is set by the user. The default is no LocalAppDataPath registry entry. But I will check it out.
I can confirm that this is the case. If the location is not changed, there will be no LocalAppDataPath in the registry branch.
So if it was there, then you (or some browser extension of yours?) must have put the space into it under
Settings - Server - General - ‘Show Advanced’ - “The path where local application data is stored”
Im on Server 2012 R2, with latest updates, and plex pass version Version 1.13.5.5291.
i7-2600k with hardware transcoding enabled for Quick Sync
16GB Ram
windows installed on SSD with plenty of space
I have never had issued for years, and all of a sudden i am having same issue with this release, i have tried repair through installer, as well as system restarts. This windows update you are referring to does not apply to server 2012 r2, and there have not been any windows updates affecting those parts of windows 2012 r2 in last 3 months, its only been .net updates.
I am having an issue of pausing with chromecast and samsung tv app after 15-20 minutes, i have not installed anything on my server other than plex updates.
