Installer failure issue - silent installation

[Paul T.]

Good morning,

I am trying to perform a silent installation with OBS-Studio-26.1.1-Full-Installer-x64.exe. The software will execute using /S. However, it will not install the required C++ runtime (2015). This has to be performed prior to running the silent installer. Otherwise the program crashes on loading, as it's looking for VCRUNTIME140_1.DLL and can't locate it.

The issue with that is if a newer version of the C++ runtime exists on the target system already (2017 or higher), that installer fails to execute as it detects the newer version.

Can the runtime included in your installer be updated to 2017 or newer? I can't run the software otherwise, and removing the other runtime , only to install re-install it again can break already installed programs.

Any assistance, or updating the runtime in OBS, would be appreciated.

Thank you.

 

[FerretBomb]

Multiple runtime packages can coexist on a system. The newer does not need to be uninstalled, to install the 2015 runtime.

 

[koala]

Usually, you can install as many c runtime packages as you like. Once you installed an additional one, you should run Windows Update and search for updates to let Windows pull any updates to it. Then install OBS Studio. And keep in mind every runtime package comes as 32 as well as 64 bit version. If some app requires the 64 bit version, and you have only the 32 bit version installed, the app will complain.

On an older system with many apps, the runtime packages will accumulate, like this:

 

[Paul T.]

Hi all,

Thank you for the replies.

Although normally I agree with you both about having multiple runtimes, this installer is being quite specific.

I have to install this in a silent method, as I deal with many systems and the most efficient way to deal with them is through deployment scripts. I receive the error messages in the log files.

The installer will not install the runtime package from a script for whatever reason, and it requires the 2015 runtime it includes. Thus, OBS will not install via a CLI if the target system already has newer versions installed. The time to test scripts to remove and re-install the offending runtimes takes too long when deadlines loom. OBS could take the time to diagnose and updates their runtime package and alleviate the bug.

I have logs attached, if you are curious.

Paul T.

 

[koala]

According to your log, you seem to not install the most current runtimes - may be you're installing a runtime not recent enough for OBS.

You can find all the most current runtime packages at Microsoft:

Latest supported Visual C++ Redistributable downloads

This article lists the download links for the latest versions of Visual C++ Redistributable packages.

support.microsoft.com

 

[FerretBomb]

The time to test scripts to remove and re-install the offending runtimes takes too long when deadlines loom. OBS could take the time to diagnose and updates their runtime package and alleviate the bug.

Unfortunately deadlines and workload are a universal thing, and also impact the OBS team, who already have an over-full plate. Updating from a working redist to a newer revision is... a very low priority. OBS is an open-source project though, so if you have time to update it, by all means! The source is on GitHub.

Actual recommendation would be to create a silent deployment script for both of the required older redists and run it before deploying OBS, as they do not need newer versions to be removed before installing and can coexist on systems with newer versions. This should solve your issue too, and require far less work.

 

[Paul T.]

I am working with the version contained in the installer. I run it separately and it fails, with the same error the log I attached earlier did. The 2015-2019 runtime causes this issue. It's a known issue. I had hoped the version used in OBs could be replaced to a newer version.

I understand that it's not a top priority, so I will no longer pursue this.