When you try to install a program using Windows Installer (.msi) Setup package, you may encounter error 2738 or 2739 and the setup fails.
Errors 2738, 2739 occur if the Windows Installer Setup uses Windows Script (.vbs or .js) custom actions, and the VBScript or JScript runtimes are not registered in the computer.
From Windows Installer Error Messages page at MSDN:
| Code | Description |
| 2738 | Could not access VBScript run time for custom action |
| 2739 | Could not access JScript run time for custom action |
Resolution
Open an elevated Command Prompt. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Run the following commands one by one and press ENTER after each line:
You should see the output DllRegisterServer in filename.dll succeeded for each command. In case you get the error 0×80004005, it’s probably because you’re trying to register the DLLs from a normal (non-elevated) Command Prompt window.
Type Exit to close the Command Prompt window.
Note: If you’re using Windows XP, you can simply run the above commands from the Start, Run dialog after logging in to an account with Administrative privileges.
SEE ALSO
Register DLLs elevated using the context menu
Related Posts
- Can I Install Windows Script 5.6 in Windows Vista
- How to Install and Run the Windows Installer Cleanup Utility if Windows Installer Fails to Work
- Error “the Windows Installer Service Could Not Be Accessed” In Windows Vista
- Determine the Target Path of Windows Installer Shortcuts
- Fix for Error “Windows Resource Protection Could Not Start the Repair Service” When Running SFC in Windows 7 and Vista
If you enjoyed this post, make sure you subscribe to our RSS feed! We feature Tips, Troubleshooting information, Scripts and Utilities for Microsoft Windows Operating Systems!
Prefer an E-mail subscription?
I carefully tried everything in this post x2 and I cannot get past the 2738 error. I run Win 7 32bit with PowerPoint 2007. For the first time ever, there was no administrative install in the context menu and “Run as administrator” under Properties was grayed out. So I chose your suggestion to run an elevated C prompt window, but that didn’t work either. Initially, I ran both regsvr cmd’s in an elevated C prompt with success, but they were “successful” just run from the “Run” line. I also rebooted along the line to clear any memory problems that might have been there.
I am so disappointed because I will miss out on a free copy of iSpring Presenter from giveawayoftheday.com. I’ve been working for 5 hours on this problem and your solution held out the most hope. I don’t know why it didn’t work.