Knowledgebase: Faronics Core
Installing or uninstalled Faronics Products fails with message Error 2738: Could not access VBS Script runtime for custom action.
Posted by Adam Zilliax, Last modified by Adam Zilliax on 05 November 2013 07:59 AM

Cause

There are few reasons why this message could appear: 
  1. Workstation had an antivirus program installed on machine and after uninstalling it, components are left behind preventing VBScripts from running. 
  2. Vbscript.dll is not registered properly.
  3. Vbscript.dll is corrupted

Resolution / Workaround

Solution #1: For workstations with a 3rd party antivirus installed :

  1. Check to see if there are any extra DLL's registered for the VBSCRIPT runtime.
    1. Run search in registry for “{B54F3741-5B07-11CF-A4B0-00AA004A55E8}” 
    2. Check if vbscript.dll path is "c:\windows\system32\vbscript.dll" 
    3. If somehow path is not correct it should be changed to proper one. 
    4. To change it to the proper one you will need to get ownership over the registry, otherwise it will show "access denied" message.
    5. To take ownership:
      • Click on key and select Permission. 
      • Click on Advance. 
      • Switch to the Owner tab.
      • Under Owner select Administrators or the admin user you currently login. 
      • Check the checkbox "Replace owner on subcontainers and objects" and click Apply. Now you should be able to modify registry itself.

Solution for #2: Vbscript.dll is not registered in the proper way
The VBScript engine can be registered by following these steps:

  • Run Command Prompt as administrator:
            Start Menu -> All Programs -> Accessories
  • Right click on Command Prompt and select Run as administrator
  • Navigate to the folder that contains the DLL:
    • If you are using 32-bit version of Windows:
Type cd %windir%\system32 into the Command Prompt and press ENTER
  • If you are using 64-bit version of Windows:
Type cd %windir%\syswow64 into the Command Prompt and press ENTER
  • Run the command that registers the DLL:
Type regsvr32 vbscript.dll into the Command Prompt and press ENTER

Solution for #3: Vbscript.dll is corrupted
Run the sfc /scannow System File Checker command to replace a missing or corrupt copy of the vbscript.dll file. If this DLL file is provided my Microsoft, the System File Checker tool should restore it.

(7 vote(s))
Helpful
Not helpful

Comments (0)