[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.

[Fix] Can’t find Script Engine Vbscript

Step 1: Fix .VBS file association settings

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

Step 2: Register Vbscript.dll from admin Command Prompt

For Windows 8 and earlier only:

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


See also

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

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

6 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

    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.