Have to rebuild Visual C++ Runtime with an update to authenticode or they fail
Posted: Fri Nov 04, 2022 5:17 pm
We don't include the Application Runtimes with our Installer as they are provided via the Download URL's in the Web Media Block however they are prerequisites for our product installations thus in our Check Application Pre-Requisites we have the:
"Include Script: checkVC1416_27012_x64"
And in the Install Application Pre-Requisites we have the
"[DEFINE WEB MEDIA Microsoft...., Exclude from build]"
Include Script: setupVC1416_27012_x64
It seems like anytime that I change anything with the way our products are run through the Authenticode Signature or even going from the InstallAware X15 32.10 to 32.23 that we cannot keep using the already built (+signed) microsoft visual c++ runtime for visual studio 2017 v.15.9 (x64).7zip that was signed with 32.10 as during the installation it throws an error:
At another time when the timestamp server I was using stopped working and I switched to another the installation failed also.
I've confirmed the Runtime gets extracted into the C:\ProgramData\{GUID}\Microsoft Visual C++ Runtime for Visual Studio 2017 v.15.9 (x64)\mFileBagIDE.dll\6ABE32B1 fine as "vc_redist.x64.exe" and I can run this file with the same options the "setupVC1416_27012_x64" has without any error. I've tried adding "/log <logfile>" into the "setupVC1416_27012_x64" to see if that shows anything but it is almost like the file never even gets run.
I have to go into web media blocks and build a new version (+include signing it) of the runtime with the updated version of InstallAware or signing process, upload it to a new download location (I have to keep the old runtimes around for our older product releases) and update the Download URL.
Has anyone else had issues with the Visual C++ runtime libraries? It doesn't seem to happen with other runtimes that will install. I have a Windows 10 VM that I can revert back to a fairly old setup that doesn't have many runtimes to test out these changes and we've had customers complain back when we went from InstallAware X6 to InstallAware X12.
Does the InstallAware code for "Run Program $VC1416_27012_FILES_X64$\VC_redist.x64.exe" do some sort of weird check on the file or did the "Define File Bag :" not actually find the VC_redist.x64.exe to run?
As a follow on I changed the setupVC MSI script to show where it expects to find the vc_redist.x64.exe. This is the issue in that the new installer is not pointing at the right location it appears:
"Include Script: checkVC1416_27012_x64"
And in the Install Application Pre-Requisites we have the
"[DEFINE WEB MEDIA Microsoft...., Exclude from build]"
Include Script: setupVC1416_27012_x64
It seems like anytime that I change anything with the way our products are run through the Authenticode Signature or even going from the InstallAware X15 32.10 to 32.23 that we cannot keep using the already built (+signed) microsoft visual c++ runtime for visual studio 2017 v.15.9 (x64).7zip that was signed with 32.10 as during the installation it throws an error:
At another time when the timestamp server I was using stopped working and I switched to another the installation failed also.
I've confirmed the Runtime gets extracted into the C:\ProgramData\{GUID}\Microsoft Visual C++ Runtime for Visual Studio 2017 v.15.9 (x64)\mFileBagIDE.dll\6ABE32B1 fine as "vc_redist.x64.exe" and I can run this file with the same options the "setupVC1416_27012_x64" has without any error. I've tried adding "/log <logfile>" into the "setupVC1416_27012_x64" to see if that shows anything but it is almost like the file never even gets run.
I have to go into web media blocks and build a new version (+include signing it) of the runtime with the updated version of InstallAware or signing process, upload it to a new download location (I have to keep the old runtimes around for our older product releases) and update the Download URL.
Has anyone else had issues with the Visual C++ runtime libraries? It doesn't seem to happen with other runtimes that will install. I have a Windows 10 VM that I can revert back to a fairly old setup that doesn't have many runtimes to test out these changes and we've had customers complain back when we went from InstallAware X6 to InstallAware X12.
Does the InstallAware code for "Run Program $VC1416_27012_FILES_X64$\VC_redist.x64.exe" do some sort of weird check on the file or did the "Define File Bag :" not actually find the VC_redist.x64.exe to run?
As a follow on I changed the setupVC MSI script to show where it expects to find the vc_redist.x64.exe. This is the issue in that the new installer is not pointing at the right location it appears: