Plex Media Server v1.0.0.2261-a17e99e seems to install without any apparent problems, but won’t run under Windows 10 Pro 64 Individual Preview Build 14383.
It ran fine under Build 14379.
With a fresh, just completed installation of PMS, I’ll click the launch button displayed at the end of the installation. I then see the PMS icon displayed in the Windows 10 taskbar. When I click that icon it disappears. I’ll then check task manager and see that PMS is not running. It’s the same result when I then start PMS from the Windows Start Menu.
There are no PMS log or dump files to be found anywhere on my computer system’s hard drive.
And there are no related events posted to the Windows Event log.
When I rollback my installation of Windows 10 to Build 14379, PMS runs as it should. When I again install the update to Build 14383, it doesn’t.
I don’t know what other information I can provide…
Any ideas as to what the problem is, and how I might overcome it without having to rollback to Windows 10 Build 14379?
This should be reported through the insider preview app in Windows, as it is a Windows issue rather than a plex issue, I can see no reports on technet or connect(partner site for Microsoft) that would cause this behavior.
I reported this as a problem via the Windows Feedback Hubb before posting here, and after I couldn’t find any reports on TechNet or in the Windows 10 Insider forums.
I have my fingers crossed that the problem will be identified and fixed before the scheduled public release of the Anniversary Update to Windows 10 twenty four days from now, so that others won’t encounter this problem with that release.
Ill give it a try on my windows machine running that build
EDIT:
I just set up Plex 1.0.0.2261 on Windows 10 (Enterprise) 14379, Works fine, change log indicates som changes to starats up in Windows 10 on that build, so try reinstalling/“updating” plex, should resolve this issue.
I’m updating to your build now ill keep you updated.
Edit2:
Microsoft update servers are not cooperating with me, might take some time to get that specific build.
The problem continues after the installation of the update of Windows 10 Individual Preview to Build 14385, which was released last night, and a fresh installation of PMS v1.0.0.2261.
@lkmcmillen said:
The problem continues after the installation of the update of Windows 10 Individual Preview to Build 14385, which was released last night, and a fresh installation of PMS v1.0.0.2261.
I have time tonight to update my insider machine and do some testing. I’ll post my results.
I don’t know how I did it, but after restoring my installation of WIndows 10 from backup to what it was when I initially encountered the problem I’ve reported and am working on, and updated that installation to WIndows 10 Build 14385, I finally managed to cause Plex Media Server to generate a .dmp file, and a crash log file, which I’ve placed in the ZIP container file attached to this message.
Hopefully this will help in determining the cause of the problem I’m experiencing with PMS v1.0.0.2261 failing to run under Windows 10 Pro 64-bit Individual Preview Build 14385.
Windows 10 Home, Pro, Enterprise, or Mobile? And 32 bit or 64 bit?
And specifically Plex Media Server v1.0.0.2261?
Thus far, you are the only other person I’ve heard from who says that PMS is running without any issues under Windows 10. So this might actually help narrow down the source of the problem for those of us for whom it isn’t running without any issues.
At the suggest of others, I’ve been running Kodi for the first time. I don’t like it anywhere near as much as I do Plex.
Windows 10 Pro 64 bit, Plex is version 1.0.0.2261.
Few things that I can think of offhand that may be unusual compared to most plex users is that I don’t have “local application data” saved on the same drive that I have Windows/Plex installed. I use the Plex Media Server Service to autostart plex as a service, and I think I installed 1.0.0.2261 2 insider builds ago.
No, I haven’t. I took a hard look at doing so but one of the documented limitations led to my resurrecting an old Windows XP desktop from my garage, which I just finished setting up to Plex Media Server for Linux v1.0.0.2261 under Ubuntu 16.04 (32-bit) desktop. PMS runs a lot slower on that machine, but at least it’s running.
I think we’ll stick with running PMS under Ubuntu until the problem of running PMS under the current build of Windows 10 Pro 64-bit Individual Preview is fixed. Hopefully that will be before the release of the Anniversary Update on August 2nd (20 days from now).
The problem continued after the installation Plex 1.0.1.2396 under Windows Pro 64-bit Individual Preview Build 14388.
And it continues after the installation of this morning’s upgrade to Windows 10 Build 14390. (With perhaps one more build before RTM of Anniversary Update?)
The crash dump and log files generated after the most recent attempt to start Plex is attached for your perusal.
I’m in the midst of building an ISO from the ESD file for Build 14390, which I’ll then use to perform a clean installation of Windows 10 Pro 64-bit IP Build 14390. I’ll then perform a clean installation of Plex Media Server v1.0.1.2396, and post the results of those efforts here.
I’ve updated my feedback to Microsoft regarding this problem, where Microsoft has thus far only acknowledged their awareness of the problem.
Strange, I was away on a gig for the past week this delay in response. I set up 14388 with clean plex install and worked out of box, (been running beta builds for past year or so)
I’m now running with a clean installation of Windows 10 Build 14390 from a self-constructed ISO. The only other program which I’ve installed, and which is not not inherent to the installation of Windows 10, is Plex Media Server, v1.0.1.2396-c094d0d, and the ancillary programs installed by the execution of the PMS installation distribution file.
The install(s) of Plex appear(s) to complete successfully (No errors - Launch button displayed at it’s conclusion). But when I click the displayed “Launch” button; the PMS icon in the Windows Start Menu;,double click it’s executable in File Explorer;, or click “Run as Adminstrator” from the executable’s properties menu; PMS appears to start, as it’s icon appears in the taskbar. But when I hover my mouse above it, the icon disappears. A review of the Windows Task Manager discloses that PMS is in fact not running. A brief amount of information is posted to the PMS log file, and a PMS crash log is generated, but no relevant entries entered into the Windows Events log.
It’s the lack of any relevant entry to the Events log that has me most puzzled.
