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

• Windows Vista | Windows 7 | Windows 8 | Windows 10

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.

• vbscript.reg for 32-bit (download)
• vbscript.reg for 64-bit (download)

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:

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

See also

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