Error 2738 could not access vbscript runtime for custom action что делать

	Номер ошибки:	Ошибка 2738
Название ошибки:	Could not access VBScript run time for custom action
Описание ошибки:	Could not access VBScript run time for custom action. When you attempted to install or uninstall your product on Windows Vista or Windows 7, the error appeared and the installation or deinstallation did not continue.
Разработчик:	Autodesk Inc.
Программное обеспечение:	AutoCAD
Относится к:	Windows XP, Vista, 7, 8, 10, 11

Оценка «Could not access VBScript run time for custom action»

«Could not access VBScript run time for custom action» часто называется ошибкой во время выполнения (ошибка). Программисты, такие как Autodesk Inc., стремятся создавать программное обеспечение, свободное от этих сбоев, пока оно не будет публично выпущено. Поскольку разработчики программного обеспечения пытаются предотвратить это, некоторые незначительные ошибки, такие как ошибка 2738, возможно, не были найдены на этом этапе.

В выпуске последней версии AutoCAD может возникнуть ошибка, которая гласит: «Could not access VBScript run time for custom action. When you attempted to install or uninstall your product on Windows Vista or Windows 7, the error appeared and the installation or deinstallation did not continue.». Когда появится ошибка, пользователи компьютеров смогут уведомить разработчика о наличии ошибки 2738 через отчеты об ошибках. Затем Autodesk Inc. нужно будет исправить эти ошибки в главном исходном коде и предоставить модифицированную версию для загрузки. Следовательно, разработчик будет использовать пакет обновления AutoCAD для устранения ошибки 2738 и любых других сообщений об ошибках.

Что запускает ошибку времени выполнения 2738?

Наиболее распространенные вхождения «Could not access VBScript run time for custom action» проблемы при загрузке AutoCAD. Следующие три наиболее значимые причины ошибок выполнения ошибки 2738 включают в себя:

Ошибка 2738 Crash — это распространенная ошибка 2738 во время выполнения ошибки, которая приводит к полному завершению работы программы. Если данный ввод недействителен или не соответствует ожидаемому формату, AutoCAD (или OS) завершается неудачей.

Утечка памяти «Could not access VBScript run time for custom action» — последствия утечки памяти AutoCAD связаны с неисправной операционной системой. Критическими проблемами, связанными с этим, могут быть отсутствие девыделения памяти или подключение к плохому коду, такому как бесконечные циклы.

Ошибка 2738 Logic Error — Логическая ошибка возникает, когда ПК производит неправильный вывод, даже когда пользователь вводит правильный вход. Он материализуется, когда исходный код Autodesk Inc. ошибочен из-за неисправного дизайна.

В большинстве случаев проблемы с файлами Could not access VBScript run time for custom action связаны с отсутствием или повреждением файла связанного AutoCAD вредоносным ПО или вирусом. В большинстве случаев скачивание и замена файла Autodesk Inc. позволяет решить проблему. В качестве последней меры мы рекомендуем использовать очиститель реестра для исправления всех недопустимых Could not access VBScript run time for custom action, расширений файлов Autodesk Inc. и других ссылок на пути к файлам, по причине которых может возникать сообщение об ошибке.

Типичные ошибки Could not access VBScript run time for custom action

Наиболее распространенные ошибки Could not access VBScript run time for custom action, которые могут возникнуть на компьютере под управлением Windows, перечислены ниже:

• «Ошибка программного обеспечения Could not access VBScript run time for custom action. «
• «Could not access VBScript run time for custom action не является программой Win32. «
• «Возникла ошибка в приложении Could not access VBScript run time for custom action. Приложение будет закрыто. Приносим извинения за неудобства.»
• «Не удается найти Could not access VBScript run time for custom action»
• «Could not access VBScript run time for custom action не может быть найден. «
• «Ошибка запуска программы: Could not access VBScript run time for custom action.»
• «Could not access VBScript run time for custom action не выполняется. «
• «Ошибка Could not access VBScript run time for custom action. «
• «Could not access VBScript run time for custom action: путь приложения является ошибкой. «

Проблемы AutoCAD Could not access VBScript run time for custom action возникают при установке, во время работы программного обеспечения, связанного с Could not access VBScript run time for custom action, во время завершения работы или запуска или менее вероятно во время обновления операционной системы. Важно отметить, когда возникают проблемы Could not access VBScript run time for custom action, так как это помогает устранять проблемы AutoCAD (и сообщать в Autodesk Inc.).

Корень проблем Could not access VBScript run time for custom action

Проблемы Could not access VBScript run time for custom action вызваны поврежденным или отсутствующим Could not access VBScript run time for custom action, недопустимыми ключами реестра, связанными с AutoCAD, или вредоносным ПО.

Более конкретно, данные ошибки Could not access VBScript run time for custom action могут быть вызваны следующими причинами:

• Недопустимая (поврежденная) запись реестра Could not access VBScript run time for custom action.
• Файл Could not access VBScript run time for custom action поврежден от вирусной инфекции.
• Could not access VBScript run time for custom action ошибочно удален или злонамеренно программным обеспечением, не связанным с приложением AutoCAD.
• Другая программа, конфликтующая с Could not access VBScript run time for custom action или другой общей ссылкой AutoCAD.
• AutoCAD (Could not access VBScript run time for custom action) поврежден во время загрузки или установки.

Продукт Solvusoft

Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление

Some Windows users are encountering the “Error 2738. Could not access VBScript run time for custom action” or “Error 2738. Could not access Javascript run time for custom action” error message when trying to install one or several different applications on their Windows computer. This problem is confirmed to occur on Windows 7, Windows 8.1, and Windows 10.

As it turns out, there are several different causes that might contribute to the apparition of this particular error code when installing an app. Here’s a shortlist of potential culprits that might trigger a 2738 error:

Method 1: Conflict with Endpoint Security (if applicable)

If you end up seeing the ‘Could not access VBScript run time for custom action’ error when attempting to install ShoreTel Communication, it’s very likely that the installer ends up conflicting with the Endpoint Security solution developed by McAfee.

If this scenario is applicable in your case, you have 2 different ways of fixing the problem:

• Uninstalling the conflicting Endpoint Security software
• Reverting some registry values belonging to McAfee ScriptScan to their default values in order to eliminate the conflict.

If you’re looking for the easiest solution, you should go for the uninstallation of your Endpoint Security tool. This is not ideal, but it will allow you to install ShoreTel Communication without having to modify your Registry. In this case, follow subguide A.

If you’re comfortable with Registry Editor, you should follow subguide B to modify some key registry values belonging to McAffee ScriptScan which will end up resolving the conflict.

A. Uninstalling Endpoint Security

1. Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu.
2. Once you’re inside the Programs and Features menu, scroll down through the list of installed applications and right-click on Endpoint Security. Next, choose Uninstall from the newly appeared context menu.
3. Next, follow the uninstallation instructions to complete the uninstallation process, then reboot your computer.
4. After the next startup is complete, attempt to reinstall the ShoreTel Communication app and see if the issue is now fixed.

In case the same error code is still occurring, move down to Method 2.

B. Adjusting the Registry values of McAffee Scripts Scan

1. Press Windows key + R to open up a Run dialog box. Next, type ‘regedit’ inside the text box and press Enter to open up the Registry Editor. When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Once you’re inside Registry Editor, use the menu on the left-hand side to navigate to the following location:

   HKEY_CLASSES_ROOTCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}

3. Once you’re inside the correct location, change the value of (Default) from McAfee ScriptScan to VB Script Language.
4. Next, navigate to the following location:

   HKEY_CLASSES_ROOTCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32

5. Once you arrive in the correct location, change the value of the (Default) key from C:Program FilesCommon FilesMcAfeeSystemCoreScriptxxxxxxxxx.dll to C:Windowssystem32vbscript.dll.
6. After you’ve enforced the change above, navigate to the following location:

   HKEY_CLASSES_ROOTWow6432NodeCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}

7. Next, change the value of the (Default) key from McAfee ScriptScan to VB Script Language.
8. Finally, navigate to the following registry location:

   HKEY_CLASSES_ROOTWow6432NodeCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32

9. Change the value of the (Default) key from C:Program FilesCommon FilesMcAfeeSystemCoreScriptxxxxxxxxx.dll to C:WindowsSysWOW64vbscript.dll.
10. Once every change listed above has been enforced, restart your computer and see if the problem is now fixed.

In case this method was not applicable or you’re still encountering the same Error 2738 even after following the instructions above, move down to the next method below.

Method 2: Registering the vbscript.dll file

If you’re encountering the “Error 2738. Could not access VBScript run time for custom action” after an agent installation fails, it’s likely that you’re seeing this error because the VB Script Engine is not correctly registered. In most cases, this issue will occur after the vbscript.dll is modified by a third party software (most likely an AV tool).

If this scenario is applicable, you should be able to fix the problem by re-registering the problematic DDL file from an elevated CMD prompt.

Here’s a short guide that will walk you through the process of registering the vbscript.dll file that’s most likely causing the 2738 installer error:

Note: The instructions below should work regardless of your Windows version (Windows 7, Windows 8.1, and Windows 10)

1. Press Windows key + R to open up a Run dialog box. Next, type ‘cmd’ inside the text box and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Once you’re inside the elevated Command Prompt, type one of the following commands depending on if you’re using a 32-bit or 64-bit version of Windows and press Enter:

    cd %windir%system32
    cd %windir%syswow64

3. After you arrive inside the correct location, type the following command, and press Enter to register the problematic vbscript.dll:
   

   regsvr32 vbscript.dll

   Note: If you’re seeing the “Error 2738. Could not access Javascript run time for custom action” error, use the following command instead:

   regsvr32.exe jscript.dll

4. Restart your computer and see if the issue is fixed once the next startup is complete.

In case the same “Could Not Access Javascript / VBScript Run time for Custom Action” error is still occurring, move down to the next potential fix below.

Method 3: Running SFC and DISM scans

As it turns out, you can also expect to encounter this problem due to some type of corruption that ends up affecting your system’s ability to make use of DLL (Dynamic Link Library) files. If you think this scenario might be applicable, you should be able to fix this problem by using a couple of utilities that are known to fix corrupted OS instances – DISM (Deployment Image Servicing and Management) and SFC (System File Checker).

In instances where there’s suspicion of corrupted data, you should start by running a System File Checker Scan. This operation is the ideal way to start since you can deploy this scan even if you don’t have a reliable Internet Connection. This utility works by leveraging a locally stored archive to compare potentially corrupted files against a list of healthy equivalents.

Note: Keep in mind that once you start this type of scan should not be interrupted once started (under no circumstances). If you shut down your computer or close the CMD window prematurely, you run the risk of creating logical errors on your Windows drive.

Once the SFC scan is finished, reboot your computer and initiate a DISM scan once the next startup is complete.

Note: This Deployment Image Servicing and Management service use a sub-component of Windows Update in order to download healthy copies that will be used to replace corrupted instances.

Once the second scan is finished, restart your computer and see if the problem is resolved at the next startup.

In case the same problem is still occurring, move down to the next potential fix below.

Method 4: Using System Restore

If this problem only started to occur recently, it’s possible that a recent software change has ended up causing this problem with programs that want to make use of the installer infrastructure. Since there’s no clear way of pinpointing the culprit (it could be a software update, a driver, a bad Windows update, a software conflict, etc.) the best thing you can do is revert your computer to a state in which this problem was not occurring.

The best way of doing this is by using System Restore to revert your Windows installation back to a healthy point in which the “Could not access VBScript run time for custom action” or “Could not access Javascript run time for custom action” error was not occurring yet.

Here are some step-by-step instructions on using system restore to fix reset your PC back to a healthy state.

If you already did this and you’re still encountering the same 2738 error code, move down to the next potential fix below.

Method 5: Resetting every Windows Component

If none of the methods above have worked in your particular scenario, you’re probably dealing with an underlying system file corruption that cannot be resolved conventionally.

Several affected users that found themselves in the same situation have reported that they only managed to fix the problem after refreshing every relevant OS component related to their Windows 10 installation. When it comes to doing this, you have 2 ways forward:

• Repair install – This is the more focused approach since it will allow you to refresh all our OS files without losing personal data that’s currently present on your OS drive. You’ll be required to use an installation media that’s compatible with your Windows version, but you’ll be able to save applications, games, media, and even user preferences that you’re currently storing on your OS drive.
• Clean install – If you’re looking for the easiest procedure, this is it. You won’t need compatible installation media to start this operation, but unless you manage to back up your data in advance before starting this operation, you’ll lose all your personal data that’s currently stored on the Windows drive.

Windows Installer Errors 2738 and 2739 with Script Custom Actions

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, HKCUSOFTWAREClassesCLSID
• JScript, HKCUSOFTWAREClassesCLSID

Remove these keys if they exist in HKEY_CURRENT_USER.

Источник

2738 vbscript runtime error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have two servers. One runs 2008 64 bit and on runs 2008 32 bit. When I tried to install HP Web Jetadmin on the 64 bit server I received the Error 2738 listed in the title. When I tried to uninstall ActiveClient for the 32 bit server I received the same Error 2738.

I performed the following common resolutions:

Successfully registered the DLL by running regsvr32.exe vbscript.dll on both servers. The programs mentioned still would not installuninstall

Attempted to delete registry key «HKCUSOFTWAREClassesWow6432NodeCLSID» however it does not exist.

Does anyone have any suggestions what I could do next?

Answers

Found the possible problem:

It appears that the McAfee ScriptScan dll was missing (ScriptSn.dll) from both machines which would prevent application scripts form running.

Reinstalling McAfee did not resolve the issue. However reimaging the server did.

Start by that: http://blogs.msdn.com/b/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Источник

2738 vbscript runtime error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have two servers. One runs 2008 64 bit and on runs 2008 32 bit. When I tried to install HP Web Jetadmin on the 64 bit server I received the Error 2738 listed in the title. When I tried to uninstall ActiveClient for the 32 bit server I received the same Error 2738.

I performed the following common resolutions:

Successfully registered the DLL by running regsvr32.exe vbscript.dll on both servers. The programs mentioned still would not installuninstall

Attempted to delete registry key «HKCUSOFTWAREClassesWow6432NodeCLSID» however it does not exist.

Does anyone have any suggestions what I could do next?

Answers

Found the possible problem:

It appears that the McAfee ScriptScan dll was missing (ScriptSn.dll) from both machines which would prevent application scripts form running.

Reinstalling McAfee did not resolve the issue. However reimaging the server did.

Start by that: http://blogs.msdn.com/b/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Источник

Error 2738, Could not access VBScript runtime for custom action

If when you try to install a program on your Windows 10/8/7 PC, you receive the error prompt Error 2738 – Could not access VBScript run time for custom action, then this post is intended to help you. In this post, we will identify the possible cause, as well as provide the most suitable solution you can try to mitigate this issue.

This error occurs due to incorrect or corrupt registry entries that interfere with VB support in Windows. This error also means VBScript is not properly configured to run on your computer.

Error 2738, Could not access VBScript runtime for custom action

If you’re faced with this error, you can try our recommended solution below and see if that helps to resolve the issue.

First, ensure that Windows Script Host is enabled on your machine. You can use our FixWin to fix this issue. It offers a 1-click fix under the Additional fixes section.

Having done that, you need to remove an incorrect VBscript entry from the registry, as follows:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type cmd and then press CTRL+SHIFT+ENTER to open Command Prompt in admin mode.
• In the command prompt window, copy and paste in the command below and hit Enter.

The command removes the incorrect entry for VBScript support on Windows.

• Next, you need to make sure VBScript is properly registered by running the following command in CMD prompt:

After executing these commands the issue should be resolved.

Hope this helps!

Date: August 23, 2020 Tags: Errors

Fix Error 0x8007000D, The data is invalid while renaming a folder on Windows 11/10

Fix Nvldumd.dll Bad Image error in Windows 11/10

Error 10013, An attempt was made to access a socket in a way forbidden by its access permissions

[email protected]

Obinna Onwusobalu has studied Information & Communication Technology and is a keen follower of the Windows ecosystem. He has been a Windows Insider MVP (2020). He runs a computer software clinic.

Источник

Fix for Windows Installer errors 2738 and 2739

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.

As said earlier, the above errors occur if the installer fails to run JScript/VBScripts as the VBScript/JScript engines are not working properly. The most likely cause is anti-virus software hooking into the script engine in order to block the execution of scripts.

For instance, McAfee anti-virus software replaces the vbscript.dll reference in the registry to their DLL (the version number suffix varies) below:

Resolution

Windows 10 & Windows 8, Windows 7, and earlier

To automate the following steps to fix error 2738 and/or 2739, download and run the appropriate registry fix — Download vbscript_jscript_2738_2739_fix.zip

To fix the Vbscript error 2738 and/or JScript error 2739 manually:

• (Before proceeding, you may want to create a System Restore Point or take a complete registry backup.)

Fix for VBScript error 2738

1. Start the Registry Editor ( regedit.exe )
2. Go to the following branch:
3. In the right-pane, double-click (default) and set its data to:
4. If you’re using the 64-bit version of Windows, additionally, go to the following key:
5. In the right-pane, double-click (default) and set its data to:
6. Go to the following keys (if they exist) under HKEY_CURRENT_USER
7. Delete each of the above keys.
8. Exit the Registry Editor.

Fix for JScript error 2739

1. Start the Registry Editor ( regedit.exe )
2. Go to the following branch:
3. In the right-pane, double-click (default) and set its data to:
4. If you’re using the 64-bit version of Windows, additionally, go to the following key:
5. In the right-pane, double-click (default) and set its data to:
6. Go to the following keys (if they exist) under HKEY_CURRENT_USER
7. Delete each of the above keys if they exist.
8. Exit the Registry Editor.

Tech explanation about 2738 and 2739 errors

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
JScript: HKCUSOFTWAREClassesCLSID

Remove these keys if they exist in HKEY_CURRENT_USER (HKCU).

An alternate method for Windows 7, Vista, and earlier

• 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:

For Windows 64-bit editions, run these two commands in addition:

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.

The Regsvr32.exe method doesn’t remove the redundant HKCU registry key. If this method doesn’t help, follow the registry editing method discussed earlier.

Источник