[Fix] Can’t find Script Engine Vbscript, and “no script engine for .vbs”

When you run a vbscript or .msi setup file that runs a vbscript, you may receive one of the following errors:

Can’t find script engine “VBScript” for script C:\ProgramData\Microsoft\Windows\OFFICEICON.vbs

There is no script engine for file extension “.vbs”.

This happens if the Vbscript.dll module is not registered correctly or the .VBS file association settings are broken. This error can be fixed using the steps listed below, applies to Windows Vista, 7, 8, 8.1 and 10.

Step 1: Fix .VBS file association settings

Download and apply the .vbs association fix from the following link.

File association fixes for Windows Vista | Windows 7 | Windows 8 | Windows 10

Step 2: Register Vbscript.dll from admin Command Prompt

Open an elevated Command Prompt window.

regsvr32 %systemroot%\system32\vbscript.dll

You should see the DllRegisterServer in vbscript.dll succeeded.

If you’re using Windows 64-bit, run the following command in addition:

%systemroot%\SysWOW64\regsvr32.exe %systemroot%\SysWOW64\vbscript.dll

Step 3: Download the Vbscript.dll Registration Entries

If Steps 1 & 2 don’t resolve the problem, download the Vbscript.dll registration entries.

Unzip and run the enclosed REG file. Note that the paths are hardcoded for C:\. If the system drive letter is different than C:\ in your case, edit the REG file using notepad and update the correct path.

The REG files fix the Vbscript DLL CLSID key in the following registry path:

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}

See also

Error “There is no script engine for file extension” when running .js files

About the author

Ramesh Srinivasan founded Winhelponline.com back in 2005. He is passionate about Microsoft technologies and has a vast experience in the ITeS industry — delivering support for Microsoft's consumer products. He has been a Microsoft MVP [2003 to 2012] who contributes to various Windows support forums.

8 thoughts on “[Fix] Can’t find Script Engine Vbscript, and “no script engine for .vbs””

  1. I tried to uninstall an Opera widget and got the error message “There is no script engine for file extension “.vbs”. Your solution above fixed my problem. Thank you. Really appreciated.

  2. Excellent! I issued the regsvr32 command using the “start —-> run” path.
    And it worked!
    Though it is a mystery how both vbscript and jscript dlls had got de-registered.

  3. That didn’t work for me. I did find another solution:
    1. Locate the file %windir%\inf\wsh.inf (inf is a hidden
    folder)

    2.right click and select “Install”.

  4. for the step 1, I got following msg.
    The filename, directory name, or volume label syntax is incorrect.

  5. Thanks a ton Bill, your below solution worked.
    ***************
    Locate the file %windir%\inf\wsh.inf (inf is a hidden
    folder) Right click and select “Install”.

Comments are closed.