Overview

This article provides the steps to re-register Windows' VBScript (Visual Basic Script) engine when the installation of Archiver fails with an error message:

Error 2738: "Could not access VBScript run time for custom action."

Information

The installer fails to run VBScripts because the VBScript engine is not working correctly. The most likely cause is an anti-virus software hooking into the VBScript engine, or the script engine is corrupted.

Process

Part 1 - Check the Registry

Open the Registry Editor and check the following keys:

• 32-bit OS:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
    The ImprocServer32 subkey should point to C:\Windows\system32\vbscript.dll.
    
    
• 64-bit OS:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
    The ImprocServer32 subkey should point to C:\Windows\system32\vbscript.dll.
    
    
  • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
    The ImprocServer32 subkey should point to C:\Windows\SysWOW64\vbscript.dll.

If these subkeys point to other files (e.g., DLL-files from anti-virus software), it indicates that the software is hooked into the VBScript engine.

 

Part 2 - Possible Solutions

There are two possible solutions to this issue:

1. Uninstall the anti-virus software.
   OR
2. Re-register Windows' VBScript engine.

To re-register Windows' VBScript engine, follow the steps below:

1. Open the Registry Editor.
2. Export the registry keys listed above into a .reg file.
3. Delete the registry keys listed above
4. Open the Run dialog box (press Windows key + "R") and run the following commands depending on the bit version of the OS:
   • 32-bit OS:
     • %WINDIR%\system32\cmd.exe
     • regsvr32.exe vbscript.dll
   • 64-bit OS:
     • %WINDIR%\SysWOW64\cmd.exe
     • regsvr32.exe vbscript.dll
5. Rerun the GFI Archiver installer.

 

Confirmation

The installation of the GFI Archiver will be successful.