Error “There is no script engine for file extension” when running .vbs files
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
Copyright © 2008 Ramesh Srinivasan. All rights reserved.
RELATED POSTS
- Can I install Windows Script 5.6 in Windows Vista
- How to run .BAT files invisibly, without displaying the Command Prompt window
- Save and Restore Desktop icon layout in Windows NT/2000/XP/Vista
- Fix for RICHTX32.OCX Component Error when running a Program
- Search Results
- VBScript Files Open With Notepad
- Error “The audio service is not running” when opening the Volume mixer in Vista
- Clear Recent Documents history in a single click in Windows XP and Vista
- Analyze and Defragment buttons in Disk Defragmenter do not work
- Quickly clear the Google Chrome Cache using Script
BOOKMARK THIS PAGE
BlinkList | del.icio.us | Digg it | Furl | ma.gnolia | Newsvine | reddit | Spurl | Wink |



If you enjoyed this post, make sure you
Prefer an E-mail subscription?
Comment by Kapil on 22 May 2008:
Thanks a lot…
That was helpful indeed!