There was setting in PLEX 18.x.x (Settings>General) that was doing exactly the same. Why the hell did you removed it from version 19, i don’t understand !
Because of Security: Regarding CVE-2020-5741
Thanks, that was quick and helpfull.
This solution isn’t working for me. The registry file doesn’t seem to be pointing the server to the new folder. Per your instructions I copied the folder from C: to an internal drive labeled M: and put it in a Plex folder, so the path is M:\Plex\ (with Plex Media Server inside). I pointed the string value (REG_SZ) to M:\Plex\ and rebooted my system. When I tried to delete my old folder it wouldn’t let me saying it was in use. I exited from the server and stopped the service and I edited the folder by adding _old to the end and when I restarted the service it immediately created a new Plex Media Server folder on the C: drive. Per your addendum I went back into RegEdit and could not find any references to any drives it was pointed at. I should note this is a fresh-ish install of the software (less than a week old).
Any help?
You probably missed that the addendum points to a different part of the registry than the main part of the How-to.
And you need to stop the service prior to changing the registry key.
5 posts were split to a new topic: No libraries after moving the Plex data folder
Ah, you’re right! I did miss the HKEY_USERS part - my mistake. Definitely works, just deleted the old resource!
Thanks OttoKerner
Out of curiosity, why can it not be a networked drive?
Because this is a recipe for database corruption.
Plus, many network file sharing protocols don’t support symbolic links.
Hi OttoKerner!
I respect your wealth of knowledge and your passion for helping others here. I’m curious about clarification of symlinks - has anyone tried using junctions which are for entire directories and not individual files as for symlinks.
Junctions are wormholes in the tree structure of a directed graph. By browsing a Junction a maybe far distant location in the file system is made available. Modifying, Creating, Renaming and Deleting files within a junction tree structure operates at the junction target, i.e. if you delete a file in a Junction it is deleted at the original location.
I’m happy I’ve regained use of my C drive by moving 30 gigs of metadata, but I’ve confirmed that adding new titles to the library… won’t update any metadata on my core server (only when the files replicate to my 2 backup ReadyNAS devices will the metadata update but that’s because they are on different machines of course). I’d really like to try making the old C references into JUNCTIONS to the pooled drive where the files and metadata are stored.
Thanks for your input, it is appreciated.
1 Like
Pooled drives don’t support symlinks/hardlinks. No way.
Replying to my own post… One of the key Drive Bender features is its non-destructive file system technology. In short, this means that all drives within a Drive Bender pool utilize NTFS (or ReFS format if desired), and can be added to the pool without formatting.
So I’m not sure why the solution here does not work (the whole “how-to” of moving the plex data files to another location off the C drive). I think I’m going to try Junctions and see what happens… I’ve basically lost the use of plex on the main server and might as well delete it if metadata won’t work off a pooled drive 
What solution here does not work?
Clarified above in my post 
I’m hopeful the tech info I found on DriveBender’s site is truthful and since it uses NTFS then symlinks (and junctions) would work according to the info I read here.
AFAIR, Drive Bender has been tested by users before and has been found not optimal.
I cannot remember whether it didn’t work at all or whether it only suffered from the “no pictures” issue of other pooling solutions. Or if there were other wrinkles.
My recommendation: don’t use it. There is no need to put the Plex data folder onto a pooled drive.
Thank you sir, now I’m curious why DB is “not optimal” lol. I’ve used it for 15 years and not one issue so far except just now with Plex’s metadata and data files I must use the DB pool since my C drive is only 60GB and replacing it with a larger drive I’m not sure how to do that without major headache and possible loss of the server. It only runs on the weekends and I have 120TB of pooled drives (and associated data) linked up to that tiny 60GB drive 
I will let you know if junctions work - it’s worth a try since I’m probably going to un-install Plex on the server at this point and try something else on it. (Yes, will keep my plexpass and might even go lifetime as Plex works perfectly on my ReadyNAS movie servers)
You can use it for other things, however for the Plex data folder, use a single internal drive, formatted with NTFS.
How to tell Plex to use that, is explained in detail in the first post of this thread.
Can’t… the plex data and metadata consumes all the space on my 60GB system drive. Hey… (brainstorming here)… can I try adding in another drive internally and point PLEX to that other drive using the method above? I’ll splice data cables and make it so (it’s a shame that’s actually easier than replacing the main system drive lol).
BTW you should be PAID by plex. Your responses and help are better than what I get from other companies for paid support
Sorry, I think you don’t understand what the procedure does.
The whole point is to move this data off the C: drive. Thus it will no longer occupy space on C:, but on a different drive.
I got ya - my only option for “other” drive was my 120TB Drive-Bender Pooled Drive though which isn’t working for Plex’s data files. So I’ll try either the junction method (since DB is NTFS) or adding another internal drive.
I should have wrote down where the original plex datastores were lol… need that info to try the junction method. I suppose I can put them anywhere (as a junction) on the C drive though.
