I’m trying to understand this issue, but my experience is a bit different than anon848905’s description. I recently installed Paratext 9.2 in a Win10 VM and successfully pointed it to my Linux Paratext8Projects directory via the “old” instructions: Rename or delete the default My Paratext 9 Projects folder, and then start PT9 as Admin user, and browse to the folder I wanted to use, permanently mounted in a VM shared folder.
To cover all bases I then checked the (Windows) registry to be sure my custom Projects folder location was recorded there, per How to change PT8 data storage location AFTER installing. Indeed, PT9.2 did automatically update the registry entry (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Paratext\8\Settings_Directory) correctly.
But each time I apply an update patch to PT 9.2 the registry entry reverts to C:\My Paratext Projects. My reading of anon291708’s and anon848905’s comments sounds like if I edit the registry to set the custom path it will stick, but this is not what I’m seeing.
anon291708 mentioned that the point-to-custom-location trick has been removed, but I’m still seeing it with the PT 9.2.20 patch. Perhaps it has been removed in PT 9.3 (which won’t be sent automatically to “all users” until January, as I understand).
At that point will tweaks to the registry remain permanent, or will a custom Paratext Projects folder path still revert automatically? I don’t think it’s a good idea to expect people to edit the registry if they need to locate their Projects folder on a second drive. But many users have good reasons for doing this.
Related question: Is there a way to specify a custom location for the Paratext Projects folder on first install of Paratext on a new computer… and would it stick?