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.
Step 2: Register Vbscript.dll from admin Command Prompt
Open an elevated Command Prompt window.
You should see the DllRegisterServer in vbscript.dll succeeded.
If you’re using Windows 64-bit, run the following command in addition:
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:
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.