64-bit detection is missing the mark

[Sahasrahla]

Good day!

Plex server OS: Windows Server 2019 Core
Plex service wrapper: PmsService
Install directory: C:\Plex\Plex Media Server\

I found that my older version of psupdate.exe was no longer functioning and the log reported "Plex is not installed!". I updated to the latest version of psupdate, put my irregular install path in the .config file (and worked out some .NET Framework issues) and now psupdate.exe will run but reports "64-bit: False" which is not true. I couldn't find the logic in the code that helps psupdate determine which architecture of Plex is running, so I am seeking advice here.

Some of the folders in my Plex Media Server directory have a date-modified of 2016, so this is quite an old installation of Plex that's been carried through the years. It's quite possible this installation started as 32-bit (and still contains some remnants), but I have confirmed the 64-bit edition of Plex is what's now installed and running.

Thanks in advance for any assistance

[Sahasrahla]

I found some discussion in issue #55 that may help with my issue, but I have a prior engagement and will investigate further when I get back home.

[Sahasrahla]

Alright, I had a chance to digest the info in #55 and I still don't understand how psupdate determines the install architecture if it's not in the default %programfiles% folders. Here's some additional information that may be relevant:

The account running my plex service is a Windows Domain account, and is also a local administrator on the Plex machine. When testing, I am also logging in as this plex service account when I manually run psupdate, so it should be reading the correct registry hive. When I first updated to the 2.1.1 it could not find my Plex Media Server.exe at all. I added <add key="PlexInstallLocation" value="C:\Plex\Plex Media Server"/> to my .config file and then it was able to find it, but then (and still now) determine's it to be 64-bit: False.

I did have an old directory at C:\Program Files (x86)\Plex, but it only contained the \Resources subdirectory leading down to some old plug-in folders. I shift+del the directory from my machine and tried again, but psupdate still reports that I'm using the 32-bit Plex.

Here's the full log output in case there's a nugget of wisdom I'm not seeing tucked away:

Plex install folder: C:\Plex\Plex Media Server.
Plex local data folder: C:\Plex.
Updates folder: C:\Plex\Plex Media Server\Updates.
Update channel: Plex Pass.
64-bit: False.
Verify the updates folder is specified.
Verify the updates folder, C:\Plex\Plex Media Server\Updates exists.
Getting ready to download the latest package.
Checking for the latest version from Plex.
The update channel is set for Plex Pass.
Sending request to Plex: https://plex.tv/api/downloads/5.json?channel=plexpass
Parsing the information from Plex.
The file, C:\Plex\Plex Media Server\Updates\1.41.4.9399-96e35ac06\packages\PlexMediaServer-1.41.4.9399-96e35ac06-x86.exe, exists. Checking to see if the package is valid.
Checking if the installation package is valid.
The package is valid. The checksums match.
Since the package is valid - not downloading again.
Latest packages file: C:\Plex\Plex Media Server\Updates\1.41.4.9399-96e35ac06\packages\PlexMediaServer-1.41.4.9399-96e35ac06-x86.exe
The latest file version available for download is 1.41.4.9399.
Current version: 1.41.4.9399.
Latest version: 1.41.4.9399.

[Sahasrahla]

Alright, if anybody else stumbles into this thread, I was able to figure out a workaround. I found that somewhere in my previous testing, PlexServerAutoUpdater had placed an install in my default x86 folder. I deleted C:\Program Files (x86)\Plex, and then created a new folder at C:\Program Files\Plex\Plex Media Server; I then copied my existing C:\Plex\Plex Media Server\Plex Media Server.exe into that default Program Files folder I created, and TADA, PlexServerAutoUpdater sees that lonely .exe file in the default x64 install folder, recognizes I have 64-bit plex installs, and updates my custom location with the 64-bit updater. Kinda hacky solution, but it works for now!