If VBScript module is not registered correctly or .vbs file class settings are broken, you may receive one of the following errors when running a VBScript (.vbs) file in your system:
This error can be fixed using the steps listed below.
Step 1: Registering the vbscript.dll file
Open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. Type the following command in the Command Prompt window, and press {ENTER}:
You should see the following message:
Step 2: Fixing the .VBS file association settings
Then, download and apply the .vbs association fix from our File association Fixes for Windows Vista page.
Editor’s note: If you experience this error in Windows XP system, see this article for instructions.
SEE ALSO
Error "There is no script engine for file extension" when running .js files in Windows XP/Vista
Related Posts
- Can I Install Windows Script 5.6 in Windows Vista
- How to Run .BAT Files Invisibly, Without Displaying the Command Prompt Window
- Clear Recent Documents History in a Single Click in Windows XP, Windows Vista and Windows 7
- Fix for Error “Windows Resource Protection Could Not Start the Repair Service” When Running SFC in Windows 7 and Vista
- Search Results
If you enjoyed this post, make sure you subscribe to our RSS feed! We feature Tips, Troubleshooting information, Scripts and Utilities for Microsoft Windows Operating Systems!
Prefer an E-mail subscription?
@Dan E.
i had same problem, and it occurred due to me having Notepad++ as default association for .vbs files. so maybe you have some program which is taking that association.
you can see by opening
explorer > tools > folder options… > file types
Did everything listed above and I still get the error ” There is no script engine for file extension “.vbs” Now what
Thank you, sometimes Windows messages are too much generic and not at all user friendly.
Thanks a lot…
That was helpful indeed!