Error “There is no script engine for file extension”

You may receive an error “There is no script engine for file extension” while attempting to run .vbs files in Windows. This error can occur if no default scripting engine is set, the VBScript module is not correctly registered, or the .vbs file class settings are broken.

I’ll address each of the potential problems in order so you should attempt to run your .vbs file in between each step.

Step 1: Set a default script host

Open a Command Prompt window. In Windows XP, click Start, Run…, and type cmd.exe. In Windows Vista and Windows 7, click Start and type cmd. Then select cmd in the Instant Search results.

Type the following command and press Enter.

cscript.exe //H:WScript

Step 2: Registering the vbscript.dll module

Open a Command Prompt window. In Windows XP, click Start, Run…, and type cmd.exe. In Windows Vista and Windows 7, run an elevated Command Prompt.

Type the following command in the command prompt window and press Enter.

regsvr32 %systemroot%\system32\vbscript.dll

You should see the following confirmation message.

DllRegisterServer in vbscript.dll succeeded.

Step 3: Restore the .vbs file associations

If the previous two solutions didn’t work, you should restore the file associations for the .vbs (VBScript) file type by downloading and running one of the registry files below.

FixVBSFileAssociationsXP.reg

FixVBSFileAssociationsVista.reg

Tags

Like the read? Share it!

13 Comments

  • Error “There is no script engine for file extension”…

    You may receive an error “There is no script engine for file extension” while attempting to run .vbs files in Windows. This error can occur if no default scripting engine is set, the VBScript module is not correctly registered, or the .vbs…

  • Rob – Thanks for the “There is no script engine for file extension” article. The .REG file you provided was a huge help in resolving this issue!

  • Dan,

    You are most welcome. Thanks for stopping by!

  • Create posting! This really helped me out, thank you!

  • Sir.

    I have reached the step which says “DllRegisterServer in vbscript.dll succeeded.”
    So i had my PC rebooted to check if it’s already rectified.

    Sad to say, the problem is still there.

    Any other solutions for this please?
    Thanks.

  • Sir…

    Im writing here again in hopes that you could help me with this little problem of mine.
    Please help me.

    Thanks.

  • The following blog + many more comments has additional steps that may help solve reinstalling, registering and associating VBScript .vbs functionality: http://kiranpatils.wordpress.com/2009/08/13/there-is-no-script-engine-for-file-extension-vbs/

  • step 1, step 2 didn’t helped but adding the registry solved my problem… thanks a lot.

  • Thanks .. great article sir, it fix my problem during install postgresql90 on win7.

  • Thanks a lot Nilpo – I went through several pages with my problem, until I found yours which helped!
    M.

  • Ushran – Thank you very much for solution on “There is no script engine for file extension” article. The .REG file given by you was a big help for me

  • So thrilled I had to come back and add my “Thank You” to those who also appreciate the help you provided us. After trying for two days and several other websites, I came across your posting and it is the one that worked for me! Well written and easy to follow! Thank you so much.

  • Thank you very much. I really glad you found it useful.

Leave a Reply

Contact

Wanna say hello?
Drop us a line!

You'll find us here

1 Microsoft Way,
Redmond,
WA 98052, United States