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

April 27th, 2008 • Filed Under • by Ramesh Srinivasan

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:

Can’t find script engine "VBScript" for script "filename.vbs".
There is no script engine for file extension ".vbs".

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

regsvr32 %systemroot%\system32\vbscript.dll

You should see the following message:

DllRegisterServer in vbscript.dll succeeded.

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


BOOKMARK THIS PAGE

BlinkList | del.icio.us | Digg it | Furl | ma.gnolia | Newsvine | reddit | Spurl | Wink |


Add to Technorati Favorites Add to Google
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?

Enter your email address:

Delivered by FeedBurner

There Is 1 Response So Far. »

  1. Comment by Kapil on 22 May 2008:

    Thanks a lot…
    That was helpful indeed!

Post a Response