Share via

Error: there is no script engine for file extension ".vbs" at Windows XP startup.

Anonymous
2012-09-21T16:39:49+00:00

Original Title: there is no script engine for file extension ".vbs"

When I log on, I get this box titled "Windows Script Host" that includes a red "x" and the statement:  there is no script engine for file extension ".vbs".  I was haveing problems with my .exe extensions changing, but that was fixed, but this remains.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2013-08-12T17:58:13+00:00

Another solution might be to reassociate the vbs files with the following command:

  • assoc .vbs=VBSFile

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

Answer accepted by question author

Anonymous
2012-09-22T08:40:22+00:00

Hi,

Have you made any changes on your computer prior to this issue?

“wscript.exe” is Windows Script Host which is a default program to open “.vbs” file types.

Let’s follow these methods & check if the issue persists:

Method 1

a. Type ‘cmd’ in Start, Run box. Right click on cmd in the Program list and then select the option Run as Administrator.

b. Type the following command, and then press ENTER on the keyboard:

cscript.exe //H:WScript

Method 2

You may re-register the vbscript.dll file:

a. Type ‘cmd’ in the Start, Run box, right-click on Command Prompt, click on Run as Administrator

b. Type ‘Regsvr32 <space> vbscript.dll’.

c. Click the OK button.

Hope the information helps.

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments

12 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-08-28T12:14:57+00:00

    I had the same issue using WEBuilder.

    To solve it, I went in the Options/Preferences/Files/Associations

    and removed the association with .vbs files.

    Cheers!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-01-10T14:59:47+00:00

    THANK YOU VERY VERY MUCH!


    IT WORKS LIKE A HOTROAD!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-09-12T19:44:22+00:00

    It's not a file type association issue, necessarily. I'm experiencing the same issue, and it occurs for me even when I don't leave it to chance; I run the command (in the directory where the script is located) "wscript scriptname.vbs".

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments