Error Code 2738 Could Not Access Vbscript Runtime
Contents |
CompatibilityCustomer ServiceInstallation, Activation & LicensingNetwork License AdministrationAccount ManagementContact UsCommunityForumsBlogsIdeasContributionArticle ContributionsScreencastFree Learning Resources You are hereHomeSupport & LearningAutoCADTroubleshooting OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting could not access vbscript runtime for custom action windows 7 OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting To translate this article, select
Error 2738 Microsoft Fix It
a language. Bahasa Indonesia (Indonesian) Bahasa Melayu (Malay) Català (Catalan) Čeština (Czech) Dansk error 2738 vbscript windows vista (Danish) Deutsch (German) English Español (Spanish) Français (French) Italiano (Italian) Latviešu valoda (Latvian) Lietuvių kalba (Lithuanian) Magyar (Hungarian) Nederlands (Dutch) Norsk (Norwegian)
Internal Error 2738 Windows 7
Polski (Polish) Português (Brasil) (Brazilian Portuguese) Română (Romanian) Slovenčina (Slovak) Slovenščina (Slovenian) Suomi (Finnish) Svenska (Swedish) Tiếng Việt (Vietnamese) Türkçe (Turkish) Ελληνικά (Greek) Български (Bulgarian) Русский (Russian) Українська (Ukranian) हिन्दी (Hindi) ภาษาไทย (Thai) 한국어 (Korean) 日本語 (Japanese) 简体 (Chinese Simplified) 繁體 (Chinese Traditional) View could not access vbscript runtime for custom action windows 10 Original Translate English Original X View Original X Installation fails with message Error 2738. Could not access VBScript run time for custom action. Sep 24 2015SupportApplies to AutoCAD 2010, AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD 2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD LT 2013, AutoCAD LT 2014, AutoCAD LT 2015, DWG TrueView 2010, DWG TrueView 2011, DWG TrueView 2012, ... Applies to AutoCAD 2010, AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD 2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD LT 2013, AutoCAD LT 2014, AutoCAD LT 2015, DWG TrueView 2010, DWG TrueView 2011, DWG TrueView 2012, DWG TrueView 2013, Design Review 2010, Design Review 2011, Design Review 2012, Design Review 2013, and Design Review 2014See More Share Add To
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# JavaScript TypeScript Python .NET
Error 2738 Autocad
.NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform
Error 2738 Could Not Access Vbscript Runtime For Custom Action Windows 10
Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL Server Data Tools DocumentDB internal error 2738 windows 7 64 bit Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and Visual Studio. Windows Installer Errors 2738 and 2739 with Script Custom Actions ★★★★★★★★★★★★★★★ May 31, 2007 by Heath Stewart (MSFT) // https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Installation-fails-with-message-Error-2738-Could-not-access-VBScript-run-time-for-custom-action-s.html 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 custom action [2]. 2739, Could not access JScript run time for custom action https://blogs.msdn.microsoft.com/heaths/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions/ [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 PostShareShareShareShareShare Recent Posts Changes to Visual Studio "15" Setup September 15, 2016 Insert GUIDs directly into Visual Studio Code January 30, 2016 Get the Windows Instayour next steps? .Net Framework Errors and Windows 7 Autodesk 2011 products. Error 2738 Installation, could not access VBScript run http://upandready.typepad.com/up_and_ready/2011/07/error-2738-installation-could-not-access-vbscript-run-time-for-custom-action.html time for custom action 07/19/2011 If the Technical Solution below didn't fix the issue, you can delete the relevant registry entries and re-register the dll. http://usa.autodesk.com/getdoc/id=TS15102758 Please make sure you backup the registry/system before you make any changes to the registry. To delete the registry keys, please error 2738 run following commands in a command prompt with elevated privileges. Please check out this reference post as well: http://upandready.typepad.com/up_and_ready/2012/03/general-systems-windows-7-administrator-tips-tricks.html On Windows 7 64 bit System reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f On Windows 7 32 bit reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f To re-register the DLL, please run could not access following commands with elevated privileges: On Windows 7 ~ 64 bit system c:\windows\syswow64\regsvr32 vbscript.dll c:\windows\system32\regsvr32 vbscript.dll On Windows 7 ~32 bit system c:\windows\system32\regsvr32 vbscript.dll Certain Anti-Virus programs have been known to affect the registration of the dll. Please check out the the notes below: If you had McAfee Anti-Virus in the past (even if you have unistalled it will leave some trace components on the computer), please use this tool to remove it completely: http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe If you had Avast Anti-Vvirus program in the past (and you have installed it), please read the instructions to completely uninstall it here. ______________________________________________________ Epilogue 1. Search in the registry for the following value: {B54F3741-5B07-11cf-A4B0-00AA004A55E8} 2. Back up any key with that value then delete it. i.e. Backup: File > Export. When deleting the key, there maybe an error and the key will not delete. You will