Error 2738 Vbscript Windows 2008
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 16:10:38 GMT by s_ac4 (squid/3.5.20)
Setup & Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual C++ Visual F# could not access vbscript runtime for custom action windows 10 JavaScript TypeScript Python .NET .NET .NET with Beth Massi ASP.NET by Scott
Error 2738. Could Not Access Vbscript Runtime For Custom Action Windows 10
Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL error 2738 autocad Server SQL Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and Visual Studio. Windows Installer Errors 2738 and 2739 with Script Custom Actions http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-2738-could-not-access-vbscript-run-time-for/1a4499ae-8bc1-4534-9c6f-4d399ac70d9a ★★★★★★★★★★★★★★★ May 31, 2007 by Heath Stewart (MSFT) // 28 Comments 0 0 0 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 https://blogs.msdn.microsoft.com/heaths/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions/ 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, HKCUSOFTWAREClassesCLSID{ B54F3741-5B07-11CF-A4B0-00AA004A55E8} JScript, HKCUSOFTWAREClassesCLSID{ 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.
Back totop Search this blog Search all blogs Share This PostShareShareShareShareSharMichael P.) » Error 2738 - W2K8 R2 x64 « previous next » Print Pages: [1] Go Down Author Topic: Error 2738 - W2K8 R2 x64 (Read 5483 times) 0 https://forum.avast.com/index.php?topic=89354.0 Members and 1 Guest are viewing this topic. rafaelsantiago Newbie Posts: 4 Error 2738 - W2K8 R2 x64 « on: November 29, 2011, 06:30:47 PM » Hello friends,I was using http://yetanothercomputingblog.blogspot.com/2011/12/error-2738-occurs-when-installing-msi.html the Avast Pro 4.8 (Business Protection), and i'm trying to migrate to the new version (Avast Business Protection 6). I removed: Avast Manager & Avast Management Tools from my Control error 2738 Panel.I've received my new license file. And i'm trying to install the new BP.I ran the setup wizard "setup_console_bp.exe", and check that i have all the prerequisites mentioned in the Wizard. Ok, everything's right.Continuing the instalation, the wizard show a error "Error 2738 - Could not access VBScript run time for custom action.". And it ends here. I just cant install vbscript runtime for it!I need to install it very urgent, cuz i removed my Avast Console 4. And now i just can't manage my Avast Clients.I search for some help in Google, but everything that is mentioned in every topic is:QuoteIf you are using 64-bit version of Windows:Run Command Prompt as administrator:Start Menu -> All Programs -> AccessoriesRight click on Command Prompt and select Run as administratorType the following command in the prompt: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f, then hit Enter.Next, you must also type the following command: c:\windows\syswow64\regsvr32 vbscript.dll, then hit Enter.This doesn't work to me. I'm using a Windows Server 2008 R2, 64 bit version.What can i do about this?Thank you so much! « Last Edit: November 29, 2011, 06:34:39 PM by rafaelsantiago » Logged giogio Avast Evangelist Massive Poster Posts: 3996 Re: Error 2738 - W2K8 R2 x64 « Reply #1 on: November 29, 2011, 07:58:32 PM » Try also this Go to the Start Menu and click on Run. Type CMD on Run Search Bar to start Command prompt. Type cd %windir%\system32 and press Enter.
with elevated permissions. To confirm that its the problem run the MSI installer from the command line (with administrator permissions - right click on the command prompt link in the start menu and select run as administrator) like this: MSIEXEC /i