Fix Error 2738, Could Not Access VBScript Runtime for Custom Action

If when trying to install the program on a PC with Windows 10/8/7 you get an error message that says: “Error 2738 – VBScript execution environment is not available for customizable actions”, this article should help you. In this article we will identify the possible cause and suggest the most suitable solution with which you can try to solve the problem.

This error occurs due to incorrect or damaged registry entries affecting VB support in Windows. This error also means that VBScript is not properly configured to work on your computer.

If you encounter this error, you can try our recommended solution below and see if it will solve the problem.

Re-register the DLL files

This error is usually caused by corrupted registry entries in the operating system.

  • Run a command line as administrator
  • Type regsvr32 vbscript.dll and press enter.
  • Type regsvr32 jscript.dll and press enter.
  • If possible, restart and try to install the software again with full administrator rights.

Run a system file check

SFC / scannow is a very useful command that can be used in any version of Windows. When the System File Check (SFC) command is used with the / scannow option, the tool scans all important Windows files on your computer and replaces them if necessary.

Missing and damaged operating system files (like many DLL files) may be the main cause of serious Windows problems. With this in mind, and the fact that SFC / Scannnow is fully automated and very easy to use, this tool should usually be one of your first troubleshooting steps.

  • Click Start, click All Programs, click Standard, click Command Line, and then click Run as administrator. If you are prompted for an administrator password or confirmation, enter the password or click Allow.
  • Enter the following command and press ENTER: sfc / scannow
  • [The sfc / scannow command scans all protected system files and replaces the wrong versions with the correct Microsoft versions].
  • You will see a message saying that the system scan will start. Be patient, the scan may take some time.
  • When files need to be replaced, SFC replaces them. You may be asked to insert your
  • Win7 DVD so that this process can continue
  • If everything is okay, you should see the following message after scanning: “Windows Resource Protection did not detect any integrity breach”.
  • After the scan is complete, close the command line window, reboot your computer and check.

Edit registry entries

Replace the following McAfee ScriptScan registry key values with the default values for Windows. This change allows you to install ShoreTel Communicator correctly.

1. Press Windows + R, type regedit, and press OK.

2. Change the following registry key values for McAfee ScriptScan to Windows defaults:

  • Access the registry: HKEY_CLASSES_ROOT \ CLSID \ {B54F3741-5B07-11cf-A4B0-00AA004A55E8}.
  • Change the key value (default) from McAfee ScriptScan to the VB scripting language.
  • Enter the registry: HKEY_CLASSES_ROOT \ CLSID \ {B54F3741-5B07-11cf-A4B0-00AA004A55E8}. \ InprocServer32
  • Change the key value (default) from C: \ Program Files \ Common Files \ McAfee \ SystemCore \ Scriptxxxxxxxx.dll to C: \ Windows \ system32 \ vbscript.dll.
  • Enter the registry: HKEY_CLASSES_ROOT \ Wow6432Node \ CLSID \ {B54F3741-5B07-11cf-A4B0-00AA004A55E8}.
  • Change the key value (default) from McAfee ScriptScan to the VB scripting language.
  • Enter the registry: HKEY_CLASSES_ROOT \ Wow6432Node \ CLSID \ {B54F3741-5B07-11cf-A4B0-00AA004A55E8}. \ InprocServer32
  • Change the key value (default) from C: \ Program Files \ Common Files \ McAfee \ SystemCore \ Scriptxxxxxxxx.dll to C: \ Windows \ SysWOW64 \ vbscript.dll.