Initially I did think it was an Avast issue and I had accepted the download, but it kept coming back. That is when I asked the question.
Still if the developers at Plex left this tidbit out there, I have to question their abilties. And to not hear from one of them on this forum I find grossly unacceptable.
I appreciate your help and comments, but the real test of service is when something goes wrong. So far they are failing.
Some further thoughts ....
May be there is an incomplete download. we have had numerous cases of incomplete downloads when downloading the Plex Media Server install file and one check it out by looking at the file properties and seeing that there is a Digital Signatures tab with an entry for Plex Inc
eg checking file properties for Plex-Media-Server-0.9.914.531-7eef8c6-en-US.exe
The Digital Signature is in the last block of the file and only if it is showing that one can take it that the download file is most likely a complete file
I am mentioning this because the error that Avast reported for file libeay32.dll also says: Digital Signature not present
So C:\Program Files (x86)\Plex\Plex Media Server\PlexScriptHost.exe has downloaded a libeay32.dll file that has no Digital Signature.
Without checking all the server debug logs and system / framework log file I do not know why PlexScriptost.exe is downloading this dll which is a dll within the standard software installed at the time of installing Plex Media Server. In fact, the standard libeay32.dll does have a Digital Signature and you can check that by looking at file
c:\program files (x86)\plex\plex media server\resources\plug-ins\framework.bundle\libeay32.dll and checking its file properties to see that a Digital Signature tab and entry for Plex Inc do exist
Edit: It is actually updating the framework.bundle and libeay32.dll is part of that bundle. So it is probably an incomplete/corrupt download - like what we often see from users with a slow connection to the Plex download servers.
PlexScriptHost.exe runs python scripts which is what the Plex Channels is written in - as well as the internal system/framework bundles python code
So things to look into -
Are there are channels you installed that may be need libeay32.dll and downloading the wrong dll file - one without a Plex Digital Signature?
Is the download being done by plex media server system code as part of update and it is corrupt? I do not use the software update facility as it is not reliable so I do not know how it updates the Plex Media Server installed software
Is Avast telling the truth when it is saying Digital Signature Not Present?
Edit: The bundles update download goes into a staging area - one can check the file there for a digital signature. The path can be determined from looking at the log file
.....\Logs\PMS Plugin Logs\com.plexapp.system.log
To dig deeper into this, you could set verbose and debug logging, restart Plex Media Server and when the Avast warning is displayed, capture the log files:
Plex Media Server.log and zip of the whole Logs\PMS Plugin Logs folder
Get a screenshot again of the error and the whole screen to show the time as well and upload all the files. You could zip the whole set into one file