PMS Updater using an alternate reg key?

[K12342]

Server Version#: 1.20.1.3252
Player Version#: Web 4.34.4

I initially setup my server and specified the location of the app data using the reg key LocalAppDataPath at Computer\HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server. This worked fine. No issues. It was the only location based setting I changed (other than my library file paths).

I recently moved my PMS’s AppData to another drive (with a different drive letter). I updated the reg key above, and it seemed to work fine. Although my updates didnt seem to be applied correctly (when I applied an update, the version didnt change and it crashed). I didnt think much of it.

But then I noticed some log files being created in a PlexAppData folder at the old location… and the server wasnt even running. The folder was locked, and I couldnt delete it unless I disabled the Plex Update Service - which apparently runs all the time in the background.

So - it seems that the Plex Update Service does NOT use the key referenced above. It uses a key, by the same name, in a different location!

I found that this alternate key, which I did not set manually myself, was pointing to the old drive.

Computer\HKEY_USERS.DEFAULT\Software\Plex, Inc.\Plex Media Server LocalAppDataPath - which I did not manually set.

This issue seems exactly as described in this older thread - but the thread was closed so I could not add to it. This appears to still be a bug/unclear behavior, and I wanted to report it.

Plex Update Service not recognizing change in metadata location

I recently Changed my metadata location from F:\Plex\Metadata to E:\Plex\Metadata. While the Plex Server seems to recognize this change, the Plex Update Service does not. It is still logging to F:\Plex\MetaData. How can I Change this ? I have tried logging out, Restart Plex. Restarting Computer, Restarting service. Thanks!

Why did this happen? Is this process explained somewhere and I missed it? This alternate registry location does not appear referenced here https://support.plex.tv/articles/201370363-move-an-install-to-another-system/ or here https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/ - and I think it probably should be (or addressed somewhere similar).

This is apparently a necessary item for moving a plex install.

[pshanew]

This is described in the addendum in Otto’s first post in his how-to describing the full procedure for moving Plex data on Windows:

[HowTo] An extended guide on how to move the Plex data folder on Windows

By default, Plex server stores all its own data on the system drive, in the AppData path of the Windows user. You might want to change that location, if your system drive is a small SSD or you are simply having capacity issues. Moving Plex data to a dedicated drive also makes it easier to retain your Plex server data when changing machines or re-installing Windows from scratch. For larger servers/collections, I recommend a dedicated, internal SSD drive. Exit/End/Quit/Close plex, using the t…

As far as I know, that thread is the closest thing there is to “official” documentation of how to move the Plex data folder on Windows since the UI setting was removed.

[K12342]

Thanks @pshanew

I did read that - but I don’t see a part referencing two unique keys. All I see is it referencing the standard key used by the server - I don’t see anything referencing the second key used by the update service.

If I’ve missed it - can you quote it / copy paste it?

EDIT: Nope - I see it now. The very last section.

Could this be incorporated into the official plex documentation I referenced in my first post? I’m not sure a forum post is sufficient to fill the gap in official docs.

[K12342]

I’m referencing the Plex doc titled “Move an Install to Another System”. I think the second reg key should be added here. This doc currently only references the first one.

Plex doc “Advanced, Hidden Server Settings” would be another good one - it also only references the first key.

Both are linked in my first post. I feel like those docs give incomplete info without this - if it was specified there it could have saved a lot of time for me (and the others I see posted in some threads).

[pshanew]

@K12342

I feel like those docs give incomplete info without this - if it was specified there it could have saved a lot of time for me (and the others I see posted in some threads).

At the bottom of the articles you linked is a question: “Was this article helpful?”

If you click “No” you can leave feedback describing what you believe would improve its helpfulness.

[K12342]

Thanks @pshanew.
I didn’t feel that was sufficient for an issue that’s been documented in about 3 years of forum posts that I was reading through.

Both the extended guide, and the main thread describing the issue I linked in my first post - are from 2017/2016. With the issue thread having people report this almost yearly, including one user for whom this blocked a system upgrade (due to an unknown file lock on a folder, the same file lock I noticed too).

I thought it was worth raising again to see if it could be actually addressed in a more official form - either with a correction / better workflow by the dev team or an actual integration into the Plex documentation.

I see that may have been too ambitious. I’ll just click the link. Thanks.