Consider updating Flash Player custom action - to not require VB Script

I had a client problem on 12 PC's (out of 6200 - so its not that critical) with the error: "Product: Adobe Flash Player 21 ActiveX -- Error 2738.Could not access VBScript run time for custom action ."

I opened the MSI and noticed that the developer uses Installshield - the specific action that seems to be causing the problem is under "CustomActions" Table - "IsIllegalUpgrade"

At some point Microsoft made it so you can't call a custom action is the user sets a vbscript class under hkcu:

Windows Installer Errors 2738 and 2739 with Script Custom Actions | Setup & Install by Heath Stewart

Installshield Corp also doesn't recommend doing this sort of thing anymore:

https://community.flexerasoftware.com/showthread.php?202346-VBScript-Error-2738-with-BasicMSI-and-CA

Comment from a developer:

"InstallShield provides a front-end/designer for a number of Windows Installer features, including things like VBScript custom actions. Unfortunately, though, limitations and issues with the Windows Installer cannot controlled by InstallShield beyond the data that is populated in the tables of a built MSI package. Issues in the Windows Installer such as those with VBScript actions have existed for years (the previously linked MSDN blog article is from 2004). Other issues such as those with nested MSI custom actions have even caused Microsoft to officially deprecate such functionality. However, even in this case, all functionality is still available to ensure old MSI packages continue to function as before.

In general, the simpler an installation is, the more resilient it will be against possible failures. VBScript actions tend to introduce a layer of complexity (as do any custom actions that runs code not part of MSI) that increase the number of possible failure points in the install, and are especially subject to interference by other software (antivirus software in particular) on target machines. With VBScript actions, there is an added downside that results in being unable to apply normal troubleshooting and debugging disciplines to resolve the issue through the script itself.

When custom actions are necessary, we would recommend MSI DLL, EXE, or (if allowable) InstallScript custom actions since they can be more easily debugged and are in your direct control (in the case of DLLs or EXEs). (In the case of InstallScript actions, we have the ability to resolve any issues caused by our code when bugs are reported, unlike issues with Windows Installer engine functionality which we do not own.)"