Error 2738 could not access VBScript run time for custom action.

Anonymous
2010-01-02T20:10:28+00:00

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 Error 2738 -- could not access VBScript run time for custom action.  I was able to successfully install on my wife's HP with the same OS, so the problem is not with the Broadband2Go device.  Command "regsvr32 vbscript.dll" did not fix the problem.

Windows for home | Previous Windows versions | Apps

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-04-20T18:29:01+00:00

Microsoft has created a Fix-It for this!  

What this Fix it does is to remove incorrect or corrupt registry entries that interfere with VB support in windows and then re-registers the DLL ensuring that the correct registry setting are there. After running the Fix it solution you may be able to immediately  try the operation that previously gave you the error, but to be sure, a reboot is suggested. This will address similar issues with other programs as well and not just the applications that are specifically mentioned in this thread.

The link to the Fix it is: http://go.microsoft.com/?linkid=9804433

Thanks!

Was this answer helpful?

70+ people found this answer helpful.
0 comments

51 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2011-03-09T15:43:50+00:00

    Just to validate an earlier post.  We're using McAfee here and this problem with our logon scripts has really surfaced with the release of SP1 for Windows 7. 

    The key HKEY_CLASSES_ROOT\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 is changed to mcafee's script scanner dll, but isn't registered for whatever reason during install.  Therefore, logon/startup scripts fail to run.  When you try to change the value to c:\windows\system32\vbscript.dll you get an error that you can't make changes to that key. 

    To work around this, (logged in as a local admin) you can modify the permissions of the {B54F3741-5B07-11cf-A4B0-00AA004A55E8} key.  First take ownership of the key.  Right-click the key and select permissions..then advanced..then go to the owner tab, and change the owner to <machinename>/administrators.  once ownership is transferred, go back to the main permissions dialog box and give administrators full control.  Now you can change the default value in InprocServer32 to the correct dll.  Hope this helps!

    Note: even on x64 pc's use the vbscript.dll in system32 not syswow64

    Tim

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-02-24T08:20:25+00:00

    Hi All,

    I have the same issue (2738) with this key {B54F3741 ... in the HKCU on Windows 7 64 Bits but it's not possible to find what is the product's installation has created this key ?

    All installation log is not define in a windows folder ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-02-17T00:30:04+00:00

    Same exact experience trying to get Mcafee out of new computer and used  http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

    to solve error problem.

    Thanks Snowcat

    Was this answer helpful?

    0 comments