If you look at the GitHub you’ll see all the reported bugs.
All 14 of them? That’s a good tuesday where I work lol. Half of those “issues” aren’t real issues because people are doing weird / unsupported stuff and the developer has explained that in a lot of his comments and responses.
What specific issue isn’t working? I’ve been running the service wrapper untouched for nearly 3 years and had no issues - what specific issue are you having and maybe someone here can help you?
i didn’t ask if it’s still in development because I have an issue. I ask if it’s still in development because the signs point to it not being in development.
14 issues is small but they were opened a significant time ago if some are non issues, close them out. It would show it’s still an active code base.
Plus it can always be improved upon.
One way would be to implement a way to update Plex without having to kill tue service. Have the service itself pull the update, and handle the update process vio a user definable schedule.
Since it is in Github, if there are changes that need to be made, then the repo can be forked, changed and then a pull request submitted to update the service. If someone would like changes, and isn’t a developer, then perhaps others can make the change on their behalf.
While it probably can be implemented, this would be an issue if the service isn’t run under an administrator account. I run the service under a standard user account, so the service wouldn’t be able to run the Plex update because the service user doesn’t have enough permissions.
I’ve taken the liberty of doing a major overhaul on PMSService, including fixing the majority of the reported bugs from the main project’s git.
Hopefully, @cjmurph is still around and this can make it to the main project, but until then, you can find it here:
I’ve added a new 1.1.8 release, with a big list of fixes/additions/etc.
And there’s also a thread here:
1 Like
@digitalhigh I don’t see the latest release of your 1.1.8 fork/update on GitHub.
Could you upload it?
Looks like this was deleted 
All I get is a 404 big sad
It’s back on Release 1.1.8 - Add auto-remount feature, themes, aux app logging, update packages · d8ahazard/PmsService · GitHub
@mike80808 @Arthur_Dallas
Does anyone have experience with @digitalhigh /d8ahazard’s latest release from last month?
Also, I am running Server 2022 VMs. I have read about the lack of GPU access when running Plex as a service which impacts transcoding, but does this even apply when I’m running VMs on ESXi with server grade hardware (e.g., crappy GPU)?
It has nothing to do with the type of hardware or hypervisor.
It is a restriction of the Windows OS.
I understand that. I’m asking if you’re running VMs on server-grade hardware with no access to a decent GPU anyway, would you even want to use GPU-based transcoding? Why not let the processor handle it since it’s much more capable?
The digitalhigh branch does not work properly on Windows Server 2022, although the cjmurph branch works fine though.
Hi there. I’m really hoping someone can help me on this, as I am vexed at this point. So I installed the Plex as a service 1.1.9, ran it as the account I log in as (also local admin account) and all the Plex data is under. When it runs as a service PMS loads, everything appears as normal, however, it says the files are “Unavailable”. When running under non-service mode the files are available. So I am confused as to how regular mode it see’s the path where the files are (on a NAS), but under service mode everything works fine except the file location. I have disabled UAC via registry, changed from mapped drive to full UNC path, nothing works. What’s odd is under the Mapped Drive section of the new 1.1.9, nothing happens. I can’t add anything the UI just seems unresponsive, and I have installed .NET 6 as well. Any thoughts as to how to can get the service to run AND allow it to see the storage location without issues?
I’ve just released version 1.2.0 with all of d8ahazards changes. Thanks heaps for the time and effort you put in to overhaul the application.
I finally managed to pour over the changes and do some more tidy up and a few bug fixes. I’ve also tested this version against the upcoming 64 bit release of plex and it’s working as expected.
I also updated the list of supporting proceses to kill off.
Let me know if you find anything, it has changed substantially from my last release (0.1.7).
Release 1.2.0 · cjmurph/PmsService (github.com)
enjoy.
1 Like
Works great on Windows Server 2022. You can add that one to the list.
Working fine on Server 2016 Essentials.
Though crash detection doesn’t detect the Plex “soft crash” showing up for people in the last month where the exe is still running but web or clients can’t connect.
I forget, can I use PMS as a service to remotely stop/start Plex ?
I recently upgraded to the preview release of Plex Media Server 64bit, PlexMediaServer-1.28.1.5985-56c96115f-x86_64. I also upgraded PMS as a service to 1.2.0. Since the upgrade, I cannot use PMS as a service, it seems to think that plex isn’t installed, though it is. It correctly locates my PMS data location. Any thoughts on how to resolve this? I’m running Windows Server 2019.
[10:51:10 DBG][TrayCallback][OnSettingChange] Setting change…
[10:51:11 DBG][PmsMonitor][WatchLog] PMS Log Path: c:\Plex\plex_data\Plex Media Server\Logs
[10:51:11 INF][PmsMonitor][Start] Plex Media Server does not appear to be installed!
Edit: Figured it out thanks to https://github.com/cjmurph/PmsService/issues/60
1 Like
Is this because you are not using the default location of
C:\Program Files
for the 64-bit install ?
I think so, or at least that is my assumption at this time.
Thanks for all your work, and loving v 1.2.0
Humble feature request: can we get a link to the PMS server download page in the service tray? Then I could stop the service and go directly to the downloads page without having to open a browser manually 
