Hopefully if you have an error installing patch 2738 on your system, this guide can help you.
PC problems? Solve them in minutes.
This message indicates why the VBScript engine is not currently built on the machine running the technology. Vbscript. dll must be registered to resolve the issue.
When trying to install a program using the Windows Installer package (installer.msi), you may encounter errors 2738 or 2739 and find that the installation fails.
Errors 2738, 2739 appear when Windows uses custom Windows Script Installer actions (.vbs or .js only) and the VBScript runtime or perhaps JScript is not frequently registered on the computer.
|2738||Unable to access VBScript Runtime for Custom Action|
|2739||Unable to access JScript Runtime for Activity and Culture|
As mentioned above, if the installer fails to run JScript / VBScripts as VBScript / JScript, the above errors occur, sites will not work as expected. The most likely cause is antivirus software that is tryingIt will connect to the script engine and block scripts from running. Instance,
For McAfee, the antivirus software replaces the specific vbscript.dll reference in the registry in its DLL version (specific suffix may vary) below:
C: Program Files Common Files McAfee SystemCore ScriptSn.20110222204811.dll
Windows 10 And Windows 8, Windows And 7 Earlier
To improve the next steps to recover from errors 2738 and / or 2739, download Roam and the associated recording contract using – Download vbscript_jscript_2738_2739_fix.zip
To manually fix all Vbscript 2738 and / or JScript 2739 errors:
- (You can create a system restore point or take a full computer backup before proceeding.)
VBScript Error Fix The 2738
- Start Registry Editor (
- Go to the fanbase branch:
HKEY_LOCAL_MACHINE SOFTWARE Classes CLSID B54F3741-5B07-11cf-A4B0-00AA004A55E8 InprocServer32
- Double click in the right pane (default) and configure the data:
C: Windows System32 vbscript.dll
- If you are using 64-bit Windows, you can also access the following key:
HKEY_LOCAL_MACHINE SOFTWARE Classes Wow6432Node CLSID B54F3741-5B07-11cf-A4B0-00AA004A55E8 InprocServer32
- In this special area on the right, double click (default) and set the data to:
C: Windows SysWOW64 vbscript.dll
- Use the following methods (if applicable) in
HKEY_CURRENT_USER SOFTWARE Classes CLSID B54F3741-5B07-11cf-A4B0-00AA004A55E8HKEY_CURRENT_USER SOFTWARE Classes Wow6432Node CLSID B54F3741-5B07-11cf-A4B0-00AA004A55E8
- Remove all people most associated with the above keys.
- Close the registry editor. For
JScript error 2739 fixed
- Start Registry Editor (
- Go to the following branch:
HKEY_LOCAL_MACHINE SOFTWARE Classes CLSID f414c260-6ac0-11cf-b6d1-00aa00bbbb58 InprocServer32
- Double click in the right pane (default) and align the data:
C: Windows System32 jscript.dll
- If you are using 64-bit Windows, also use the following key:
HKEY_LOCAL_MACHINE SOFTWARE Classes Wow6432Node CLSID f414c260-6ac0-11cf-b6d1-00aa00bbbb58 InprocServer32
- Double click in the right pane okto (default) and set history to:
C: Windows SysWOW64 jscript.dll
- Access the following practical knowledge (if any) at
HKEY_CURRENT_USER SOFTWARE Classes CLSID f414c260-6ac0-11cf-b6d1-00aa00bbbb58HKEY_CURRENT_USER SOFTWARE Classes Wow6432Node CLSID f414c260-6ac0-11cf-b6d1-00aa00bbbb58
- Remove all people associated with the above keys if there are many.
- Close the registry editor.
Alternative Method For Windows 7, Vista And Earlier
- An open and great elevated command prompt. To do this, click on "Start", "All Programs", "Accessories", right-click on "Command Prompt" and select "Run as administrator".
- Run the when commands individually and click the
regsvr32 vbscript.dll entry after each line.regsvr32 jscript.dll
For 64-bit editions of Windows, they only run two additional commands:
c: windows syswow64 regsvr32.exe vbscript.dllc: windows syswow64 regsvr32.exe jscript.dll
You should really see the name of the DllRegisterServer output file in .dll for every production command. If you get an error
0-80004005this is probably because you are trying to register DLLs from a normal (non-elevated) command prompt window.
- Enter exit to close the main command prompt window.
The Regsvr32.exe structure does not delete the redundant HKCU registry key. This method doesn't make things easy, just follow the method for editing the registry that we talked about earlier.
Technical explanation of errors 2738 or 2739
For security reasons, Windows Installer does not load the kernel script specified in HKEY_CURRENT_USER. As a writable function, a standard user can get some kind of elevated setup to mask their variant as a scripting engine in case the custom action has not been explicitly assigned using msidbCustomActionTypeNoImpersonate (0x0800). This could be a privilege escalation attack; Hence, Windows will return error 2738 or 2739 for custom actions, enter 6 or 5 respectively, and return Windows error 1603, ERROR_INSTALL_FAILURE.
Make sure vbscript.dll and jscript.dll are not registered in HKEY_CURRENT_USER (HKCU), etc.Check the Windows registry keys of your computer below.
Hint: If You Liked This Post, Please Share It If You Can?
The "small" margin you have as a result will really help those who are very developing this blog.Some good suggestions:
- Share this on your favorite blog + Facebook, It!
About the author
Ramesh Srinivasan is passionate about Microsoft technology and even won the Microsoft Valuable Most People Professional award in the Windows Shell / Desktop Experience category ten times in a row from 2003 to the following year. He loves to fix bugs and write Windows.Ramesh founded Winhelponline.com in 2005.Keep your PC safe and secure with this free
Corrigir Erro Do Instalador 2738
Corregir El Error Del Instalador 2738
ì„¤ì¹˜ í”„ë¡œê·¸ëž¨ ì˜¤ë¥˜ 2738 ìˆ˜ì •
Correggere L Errore Di Installazione 2738
Ispravit Oshibku Ustanovshika 2738
Fixa Installationsfel 2738
Napraw Blad Instalatora 2738
Correction De L Erreur D Installation 2738
Installationsfehler 2738 Behoben
Repareer Installatiefout 2738