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.

Windows XP: http://www.happymonkeying.com/eSupport/FixVBSFileAssociationsXP.reg

Windows Vista and 7: www.happymonkeying.com/eSupport/FixVBSFileAssociationsVista.reg