search
top

Can’t find script engine “VBScript” for script error on Windows 7 and Windows 2008

We had recently received an error when upgrading a product and the script used for the upgrades was VBScript. When running the script there was a few systems that displayed the following error.

“Can’t find script engine “VBScript” for script “<path to script>”

vbscripterr

Upon doing a bit of digging I found that most times this error is resolved by re-registering the vbscript.dll. We ran the following commands.

  1. Click on start button, type cmd. In the search result right-click on cmd and selectRun as administrator.
  2. Type cd %windir%\system32 and press enter.
  3. Type regsvr32 vbscript.dll in command prompt and press enter.

If the registration was successful, you should now see the following message:
DllRegisterServer in vbscript.dll succeeded.

On some of the servers this fixed the issue and scripts ran again. On the systems that still didn’t work did a bit more digging and found that a recent McAfee upgrade changed a registry key for vbscript. Here’s how to correct it.

  1. On the problem machine, log in as an administrator.
  2. Open the registry editor (regedit.exe) and navigate to the following registry key.[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
  3. check the path of the Default registry key, it will most likely point to the path of your Anti-Virus Product.
  4. Right click on InprocServer32 and select permissions. Give the Administrators group full access.
  5. Then Modify the Default registry key and change the path to C:\Windows\system32\vbscript.dll
  6. Change the permission back.

vbscripterr3

After making the change vbscript’s started running again!!

 

15 Responses to “Can’t find script engine “VBScript” for script error on Windows 7 and Windows 2008”

  1. David says:

    This worked! Thank you so much.

  2. ron says:

    3rd solution worked for me, thank you very much

  3. Ryland says:

    Beautiful – thank you. Regedit worked!

  4. Jitka says:

    The change of registry key helped me, thank you very much.

  5. bzrg says:

    This worked! Thank you

  6. Chris says:

    I logged in with my local admin rights and was unable to change the administrator permissions for that registry key. :S I get “access denied”. Is there some way to override that?

  7. Win7Works says:

    The change of registry key helped me, thank you very much.

  8. Leonardo says:

    It worked! Thank you!!!!!

  9. DC says:

    It is work!
    Thanks

  10. Gremy says:

    Also check [HKEY_CLASSES_ROOT\VBScript\CLSID]
    @=”{B54F3741-5B07-11cf-A4B0-00AA004A55E8}”

    The Default name with type REG_SZ and data of
    {B54F3741-5B07-11cf-A4B0-00AA004A55E8} was missing in the registry. Adding the string fixed the issue for me.

  11. Roger says:

    It worked by changing the registry, but i had to change the permissions, check this link:

    https://www.howtogeek.com/262464/how-to-gain-full-permissions-to-edit-protected-registry-keys/

Trackbacks/Pingbacks

  1. Unable to Find VBScript Script Engine? - Nicole Welch - Site Home - MSDN Blogs - […] VBScript.dll, but that didn't help.  After some careful searching, we found this article http://lifeofageekadmin.com/cant-find-script-engine-vbscript-for-script-error-on-windows-7-and-windo…  Basically the antivirus software had…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

top