Error 2738 windows vista

I' m trying to install. I read through the forum/ thread that you mentioned but everyone there is referencing Vista and I' m on Windows 7. does that make a difference? Ran in to this tonight trying to un- install a couple RIM OSs: Error 2738. Could not access VBScript run time for custom action. Couldn' t uninstall, install, or repair, no matter. When you attempted to install or uninstall your product on Windows Vista or Windows 7, the following error appeared and the installation or deinstallation did not continue: Error 2738. Could not access VBScript run time for. Error 2738 is a runtime error and it normally appears during the installation or when we launch a program. Here is an error message: Error 2738 Could not access VBScript run time for custom action. This error appears when the. That is indicated by Windows Installer error messages 27, which read: 2738. in an elevated console on Windows Vista and newer with UAC enabled; otherwise, you' ll end up registering the runtimes in HKCU. I' m running windows vista home premium on my pc but I' ve had too many problems getting spss work run smoothly. I' ve tried to uninstall but each time the error message " internal error 2738" pops up, and the operation.

  • Portable virtualbox kernel error
  • Fortnite sign in error as 0
  • Ошибка xr 3da exe windows 7
  • Fehlercode bmw f10


  • Video:Error windows vista

    Vista error windows

    The error code 2738 typically occurs either when you attempt to install a program or uninstall it on Windows Vista and 7. The error message is displayed in the following format: “ Error 2738. 問題: Windows Vista または Windows 7 で製品のインストールまたはアンインストール を行おうとしたときに、 次のエラーが発生し、 インストールまたはアンインストールを続行 できません。 エラー 2738。 カスタム アクションの VBScript. I' m attempting to activate my Virgin Mobile Broadband2Go device on my Acer Aspire 1410 running 64- bit Windows 7 Home Premium. The installation aborts mid- way through with Errorcould not access VBScript run time for custom. I wanted to see the full text of this error message, so I temporarily changed the product language setting in my WXS file from 1041 ( the LCID for Japanese) to 1033 ( the LCID for English) and re- ran the build. When I did that, the.