Ignite Installation Errors due to Missing VBScript
Ignite's installation includes running VBScript (.vbs) files on Windows machines. In some environments, VBScript has been disabled, causing the Ignite installation to not complete successfully.
For example, you might encounter an error like "Error: 2738.Could not access VBScript run time for Custom action" during installation of Ignite.
To enable VBScript, run the following by opening a Command Window and typing the following commands:
cscript.exe //H:WScript
regsvr32 %systemroot%\system32\vbscript.dll
After the vbscript.dll is successfully registered, rerun Ignite's Installation again.
If you now get an error like "there is no script engine for file extension .vbs", then you will also need to restore the .vbs file associations. You can do this by downloading the appropriate Registry file and double-clicking it: