PMS creates new "Plug-ins-*********" folder with each update

Otto, this is not about storage. I would simply like to know if those DLLs from 2022, which all have since received updates to newer versions, can be removed or not.

It’s essentially related to the original bug report I posted here, where every PMS update would add another plug-ins folder. I can see this happening with the DLLs as well.

Generally I would say not to remove them. Are sure there are newer duplicates. Can you provide an example of one or more of the DLLs that are duplicated.

The ones from 11/1/2022 are all a “version” lower. There are more further down.

@BigWheel After installing the latest PMS beta yesterday, I noticed that the Plug-ins folder had been moved to the main folder instead of the Resources folder. That’s probably intentional, but I was wondering if you guys also made a change so that the Script executables that normally run along with PMS don’t run anymore. Previously, when you installed a new version of PMS, there would be multiple instances of those in Task Manager, compared to just one or two with an already existing version. Now, with this latest beta, there are no script executables, and I noticed that the only scheduled task that ran overnight was the scan. Metadata did not refresh, for example. Wonder if that might be related or just a coincidence.

This release was already supposed to fix the issue: Plex Media Server - #610 by drzoidberg33
Are you saying that it is not fixed for you?

No current issue with the Plug-ins folder, as far as I can tell. Was just wondering if the move from Resources to the main folder was intentional. But I’m more curious about the script executables. Didn’t want to open another thread for that, though.

The installer moves it to the parent folder and then clears out all resources plugin folders and then moves the new plugins folder to be below the resources folder

We had one reported case where this final move failed. We do not know why - suspect some lock / some other software interacting.

If there is new evidence of this happening again and can be reproduced then would be interested to follow up - but we would only know the reason for the failure in moving the folder if we have a capture of Process Monitor a the time to go with the Installer logs

Thanks. I’ll wait til the next beta release install and report back.

Still curious about the “missing” script executables in Task Manager :wink:

If the Plug-ins-xxxxxxx folder is not moved to the C:\Program Files\Plex\Plex Media Server\Resources folder by the installer then there won’t be any bundles for the PlexScriptHost.exe to run and I would suspect that is why they do not show in Task Manager.

An uninstall and re-install may fix the problem if there is not something that is blocking moving folders - eg some live backup software or some anti-virus software may lockdown a folder whilst it is performing its task making any move action to fail with a windows share violation.

To identify what is causing the move folder to fail, one would need to have ProcMon running capturing events before the install sequence is initiated - if the problem arises then the saved procmon PML file together with the installer logs (which are initially in %TEMP%) would identify the reason.

Note that PML files are very large but they do zip very well. The zip would need tp be uploaded externally and a link provided.

FYI this is the forum topic where we had a failure on the move folder (we use windows rename system call to do that)

Server accesible from https://app.plex.tv, but not from local IP or loop after update to 1.40.0.7998 - Plex Media Server / Desktops & Laptops - Plex Forum

1 Like

Spot-on! Having the Plug-ins folder in the main PMS folder must have been a one-time glitch. After uninstalling and reinstalling, everything is now back to normal. All the scripthost exes are running again.

Regarding this:

28d

“Generally I would say not to remove them. Are sure there are newer duplicates. Can you provide an example of one or more of the DLLs that are duplicated.”

After uninstalling and reinstalling, all the old DLLs are now gone. So, it should be safe to delete them manually as well.

The old DLL’s are similar issue to the old Plug-ins-xxx folders we had - Except they happen much less frequently - only when we update the transcoder with a new ffmpeg version. We have decided that as they are very few files and have no impact, we will not be making changes to remove them automatically.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.