Hey David!

After copying that DLL to the proper directory and re-running the installation from the user's desktop, the installation worked as intended.

Thank you for your help!

I am wondering if this is common with script-based deployments?

I had several other clients that I got set up using the GUI on their desktop and was able to install without any issues when script-based deployments had failed immediately prior. Granted, I did not get any error about missing C++ libraries and instead ran into errors indicating that the installation path could not be found.

Again, thank you for your help! :)

Gotcha! Is there a good way to submit logs from the command line interface so as not to disturb the client's workday?

Is there anything else that can be done at this point besides sending the logs?

Hi David!

I have installed the 32-bit version as well and rebooted. Behavior is persisting.

It bears mentioning that version 7.2.1.49 was installed previously, but there was an issue with one of the VSS DLLs which prompted the initial uninstall/reinstall attempt when I ran into this problem while trying to re-install.

I can provide some logs if that would be useful.

Looks like it was already installed on the machine in question. I ran a repair of that library and the same behavior continued.

Thanks David! I will give that a try and report back shortly.

The installer is version 7.2.1.58

Hi David!

I run into the attached popup after running the installer on a Windows 10 21H2 workstation.