Windows Installer Errors 2738 and 2739 with Script Custom Actions

Windows Installer Errors 2738 and 2739 with Script Custom Actions

  • Comments 30

Windows Script custom actions should be avoided. They are difficult to debug, get blocked by virus scanners, and are far more susceptible to machine state than native custom actions. That is indicated by Windows Installer error messages 2738 and 2739, which read:

  • 2738, Could not access VBScript run time for custom action [2].
  • 2739, Could not access JScript run time for custom action [2].

As some people have found, re-registering the runtime libraries vbscript.dll and jscript.dll will fix the errors, but that isn't always the solution.

As a security measure, Windows Installer will not load script engines registered in HKEY_CURRENT_USER. As a user-writable store, a normal user could get an elevated install to run their library masking as a script engine if the custom action was not explicitly attributed with msidbCustomActionTypeNoImpersonate (0x0800). This is an elevation of privileges attack; thus, Windows Installer returns error message 2738 or 2739 for custom actions type 6 and type 5, respectively, and returns Windows error 1603, ERROR_INSTALL_FAILURE.

Check that vbscript.dll and jscript.dll aren't registered in HKEY_CURRENT_USER (HKCU), checking for the registry keys below.

  • VBScript, HKCU\SOFTWARE\Classes\CLSID\{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}
  • JScript, HKCU\SOFTWARE\Classes\CLSID\{ F414C260-6AC0-11CF-B6D1-00AA00BBBB58}

Remove these keys if they exist in HKEY_CURRENT_USER.

Also be sure that if you need to re-register vbscript.dll or jscript.dll, you run regsvr32.exe in an elevated console on Windows Vista and newer with UAC enabled; otherwise, you'll end up registering the runtimes in HKCU.

Leave a Comment
  • Please add 3 and 3 and type the answer here:
  • Post
  • @Darryl, the best advice is to avoid them: You might also try running procmon and see what else it's trying to load. Another DLL might be missing, in which case (re)installing Windows Script 5.7 from the Download Center XP / 2003 may work. If this is Vista/2008 or newer, you should consider opening a case issue with Customer Support Services at

  • hello

    Thanks i also got this error :    could not access vbscript runtime for custom action windows 7

    when i tried to install one software but untill now i dont have solution i tried all steps but still getting same error please help me to get solved out by any other new metods

    Thanks a lot again

    Ganesh and

  • @JustEricsson, you'll need to open a case issue with Customer Support Services @ Workarounds for previous platforms will not work. I recommend you also contact the publisher and ask them to fix their deployment package to avoid using script custom actions citing this and other blog entries (like those I've linked to Rob's blog).

  • On Windows 7 SP1 x64, the described fix works just fine when installing the WIF SDK. Only modification is the one mentioned above - go to HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID to find the keys that need to be deleted.

  • Im running W7 64 bit and when using the suggested solution running cmd.exe as administrator I get the following response: ERROR: The system was unable to find the specified registry or value.  Any suggestion?

  • @dondie, on a 64-bit platform you need to delete the registry keys under the Wow6432Node: HKCU\Software\Classes\Wow6432Node\CLSID\...

  • I tried everything in this thread and still unable to install weatherbug on Windows 7 64 bit  

  • @Mike, did you register both the 32- and 64-bit locations? See the comments on this post for more information.

  • If would be nice if you would include instructions to complete the above tasks for those (me) that are not computer savvy.

  • @Bina,

    1. Click on Start, then Run.

    2. Type cmd.exe and click OK.

    3. Run the following commands:

    reg delete HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8} /f

    reg delete HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58} /f

  • Hey I had the same issue with my computer. I wasted my time on it for

    many days but finally I got a solution from this link

  • Used regsvr32 vbscript.dll command


  • I accidentally deleted the entries under HKLM (all subfolders in {B54...}) manually, and tried to reregister the engine, but the folder in the registry is still empty.. Can anyone give me some advise to undo this?

  • Hi i have faced the same error code working with office 365 after lots of try lastly got the solution from this link

  • You will also get this error if you are running the WiX build on a TFS Build Server and the Service Account under which the build process is running is not in the Local Administrators group on the machine.  After adding the Build Service Account to the Local Administrators group on the build server, make sure to restart the Build Service.

    I can only assume that the Windows Installer service somehow limits access to accounts which are Local Administrators.

Page 2 of 2 (30 items) 12