Server Version#: Installer file version: 1.13.5.5332
Player Version#:
Installation fails immediately with error 0x80070643. I haven’t had a previous version of Plex Media server on this machine, and I have tried the Microsoft Fix It tool (which does not offer specific support for Plex player or media server). I’m attaching the install log and a screen cap of the error message.
Plex Media Server_20180906155145.log (19.7 KB)
Deinstall plex server
Don’t use 3rd party unistaller software like Revo.
Don’t use ‘Registry cleaners’ like CCleaner etc.
Download a fresh copy of the installer.
Use a different web browser this time.
Only download it from the link below.
If that still fails, you need to remove pms-shutdown.msi using the Microsoft Fix-It!
If that fails as well, there is some manual registry work needed:
Fix-It (or Easy Fix) is no longer available. I found this article with suggested fixes: Microsoft Easy Fix solutions have been discontinued - Microsoft Support
This is going to require a manual fix, and I’m very hesitant to alter my registry unless I know exactly what I’m looking for and what specific change I need to make.
It is called ‘Fix It!’ and is still available. Directly from Microsoft.
https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed
I’d previously downloaded that app, but using your link I downloaded and tried it again, though I fear to no effect. It simply opens the appropriate Windows troubleshooter which I’ve also tried opening directly using Settings>Update & Security>Troubleshoot>Program Compatibility Troubleshooter.
I can open regedit, but I’m not sure what I need to look for or remove. I’ve already tried searching “v1.13.5.5332” but found nothing in the extensive results I was comfortable deleting.
@sa2000 do you have any idea about this?
Lets try and see if the other logs add any extra information. Error 0x80070643 is a general generic error
Can you see if you have any of these other logs
C:\Users\keith\AppData\Local\Temp\Plex Media Server_20180906155145_000_pmsshutdown.log
C:\Users\keith\AppData\Local\Temp\Plex Media Server_20180906155145_001_vcredist.log
C:\Users\keith\AppData\Local\Temp\Plex Media Server_20180906155145_002_pms.log
I would not recommend making registry changes manually
Hopefully from the logs we can see if detected a specific version it can no longer find the package cache for and then we can see if the Troubleshooter can be used in a way to uninstall that detected old version
The Fix It / Troubleshooter needs to be used to troubleshoot uninstall of the existing version - this could be by giving it a package or product name and it could be Plex Media Server and pms or a specific package identifier
I apologize for inundating.
Plex Media Server_20180906155145.log (19.7 KB)
Plex Media Server_20180907132231.log (19.3 KB)
Plex Media Server_20180906015238.log (23 KB)
Plex Media Server_20180906015238_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906015336.log (9.89 KB)
Plex Media Server_20180906015355.log (23.1 KB)
Plex Media Server_20180906015355_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906021345.log (23.3 KB)
Plex Media Server_20180906021345_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906021455.log (23.5 KB)
Plex Media Server_20180906021455_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906021532.log (23.3 KB)
Plex Media Server_20180906021532_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906021620.log (23.2 KB)
Plex Media Server_20180906021620_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906021937.log (23.3 KB)
Plex Media Server_20180906021937_000_pmsshutdown.log (4.43 KB)
Plex Media Server_20180906155145.log (23.6 KB)
Plex Media Server_20180906155145_000_pmsshutdown.log (4.44 KB)
Plex Media Server_20180906155220.log (23.5 KB)
Plex Media Server_20180906155220_000_pmsshutdown.log (4.44 KB)
Plex Media Server_20180906161837.log (23.3 KB)
Plex Media Server_20180906161837_000_pmsshutdown.log (4.44 KB)
Plex Media Server_20180906162234.log (23.3 KB)
Plex Media Server_20180906162234_000_pmsshutdown.log (4.44 KB)
Plex Media Server_20180907132231.log (23.1 KB)
Plex Media Server_20180907132231_000_pmsshutdown.log (4.44 KB)
Plex Media Server_20180907134441.log (23.2 KB)
Plex Media Server_20180907134441_000_pmsshutdown.log (4.44 KB)
you could have attached as one zip
will have a look tomorrow - getting late here
My bad. I didn’t even think of zipping them.
Thanks for all the logs
Something does not look right in the windows installation
need clarification
Are you switching windows versions ?
One of your logs shows Windows 8 Pro running whereas the others show Windows 10 - but there is a mixture of settings for both windows 8 and windows 10
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegReleaseID' to value '1803'
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegCurrentBuildNumber' to value '9200'
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegInstallationType' to value 'Client'
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegEditionID' to value 'Enterprise'
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegProductName' to value 'Windows 8 Pro'
[1C41C:1B644][2018-09-07T13:44:41]i000: Setting string variable 'WinRegCurrentBuild' to value '17134'
1803 and 17134 are windows 10 numbers
9200 is windows 8
[1C41C:1B644][2018-09-07T13:44:41]i001: Burn v3.10.3.3007, Windows v6.2 (Build 9200: Service Pack 0)
This is windows 8
This was the last log that you uploaded.
So it shows that vcredist is missing and also pms needs to be installed
[1C41C:1B644][2018-09-07T13:44:43]i201: Planned package: vcredist, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: No, uncache: No, dependency: None
[1C41C:1B644][2018-09-07T13:44:43]i201: Planned package: pms, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
But i cannot find any reference to `vcredist being installed
Were there any log files for vcredist?
Would be with names ending with vcredist,log as in
C:\Users\keith\AppData\Local\Temp\Plex Media Server_20180907134441_001_vcredist.log
May be the failure is before getting to that point
Before making any suggestions on using the troubleshooter, I would like to understand first why the log was referencing windows 8
The log being Plex Media Server_20180907134441.log
May be you need to do a windows repair or run in admin session
sfc /scannow
It must have been trying to install in compatibility mode. This machine has
always run Windows 10 Pro. I probably do need to run a repair, if not a
reinstall. I tried to install WinZip last night, and it was a bust as well.
Btw, I appreciate all your help.
-Keth
…and no vcredist.log files. I sent all the Plex Media Server files in
that directory.
would suggest undoing everything you did with compatibiilty mode and also complete an integrity check
Start / Run: cmd and right click Run As Administrator and then execute
sfc /scannow
and after reboot try again to install different programs and when you succeed then try Plex Media Server install
Restarting was all it took. (And the integrity check came back clean.)
You’d think that would be the first thing I’d try, but with 10 Pro I
haven’t needed to for any reason in so long.
Thank you so much for all your help. …I’m sending a zipped file of all
the install logs purely for satisfaction. 
-Keith
PMS install logs.zip (584 KB)
Looking back - there was actually a clue that I missed. I should have looked up msi error code 1603
MSI (c) (E4:3C) [13:44:46:497]: MainEngineThread is returning 1603
This was the log line near the end of the _000_pmsshutdown.log log files before verbose logging gets stopped
The msi errors are documented here Windows Installer Error Messages (for Developers) - Win32 apps | Microsoft Learn
and 1603 is defined
1603 The file [2][3] is being held in use by the following process: Name: [4], Id: [5], Window Title: ‘[6]’.
A system restart may be required because the file being updated is also currently in use. Users may be given the opportunity to avoid some system restarts by using the FilesInUse Dialog or the MsiRMFilesInUse Dialog. For more information, see System Reboots and Logging of Reboot Requests.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
