Comments on: Restoring .vbs (VBScript Script File) File Associations

By: Jim

Jim — Tue, 08 Nov 2011 20:36:04 +0000

@Asa,

Hey, you may found my problem as well! My .vbs association keeps getting “lost” even after I fix it, and I use (and love) Notepad++ as well, and used the interface setup options to set .vbs to be edited w/ Notepad++ instead of the default of Notepad. I won’t know for sure for a few days, but thanks for the heads-up!

Thanks for the help Nilpo, the good posters here, and the folks over @ http://kiranpatils.wordpress.com/2009/08/13/there-is-no-script-engine-for-file-extension-vbs/ ! (look there for an easy way to reset the defaults using the %windir%\inf\wsh.inf file! - thanks to kiranpatils)

By: Nilpo

Nilpo — Sat, 05 Nov 2011 21:58:28 +0000

@Nathan,

Of course I remember you. Thanks for stopping by. I’m glad you found it useful.

Nilpo

By: Nathan Kulas

Nathan Kulas — Thu, 03 Nov 2011 22:35:05 +0000

Hey Nilpo,
You may remember me (omrsafetyo) as the BATCH guru from devhardware
I happened across this article trying to fix a wsf file association issue for a client - I was trying to determine where “windows script host” was kept - wasn’t sure if it was vbscript.exe or wscript.exe, or something else entirely. I did my google search “how to associate a file type with windows script host” and this was the first page that caught my eye as relevant. Just wanted to say hi, and thanks for the assist!

By: Bart

Bart — Tue, 27 Sep 2011 20:26:22 +0000

[HKEY_CLASSES_ROOT\.vbs]
@=”VBSFile”

Already solved it for me.

By: Kevin

Kevin — Tue, 19 Jul 2011 22:34:17 +0000

I received this error when trying to run this script on a Windows 7 machine that won’t let me associate .vbs with either cscript or wscript. The default box is greyed out

Cannot import FixVBSFileAssociationsVista.reg: Not all data was successfully written to the registry. Some keys are open by the system or other processes.

By: Lord Nutsack

Lord Nutsack — Wed, 22 Jun 2011 09:55:18 +0000

Your vista reg key works in Windows 7, thanks.

By: Asa

Asa — Sun, 29 May 2011 06:26:20 +0000

Thanks!
I got the ‘There is no script engine for file extension “.VBS”‘ error, and spent about 30 minutes searching online for a solution. No one else seemed to have the right solution for anyone (that I found), going back 10 years of advice!

Your registry entries solved it for me on Windows 7. MSDN describes the issue (”This file extension is not mapped to a script engine.”) and how to solve it: “Check your file extension and also the spelling of your scripting language designation.” or “Use //E to designate a script engine.” At last the last item is a workaround, from the command prompt, to get a script to run.

Pretty sure setting Notepad++ to associate with VBS files caused the problem for me (from the NP++ interface). I should probably let them know…

Your real solution is much appreciated

By: James

James — Sat, 06 Nov 2010 02:38:49 +0000

Thanks so much! This finally fixed my 4-month broken cscript .vbs issue on Windows 7!

By: Scott

Scott — Mon, 01 Nov 2010 15:51:00 +0000

THANK YOU!

By: Tom Souza

Tom Souza — Wed, 06 Oct 2010 00:25:17 +0000

You saved me a lot of headache…

Keep up the good work.

By: Ravi

Ravi — Wed, 26 May 2010 17:32:00 +0000

Thank you. It was really helpful

By: Structed

Structed — Wed, 22 Jul 2009 07:34:38 +0000

Worked like a charms! Thank you very much!

By: Nilpo

Nilpo — Fri, 10 Jul 2009 01:12:28 +0000

Hello Peter.

It sounds as though your .reg file type has been changed as well. This is somewhat common since some administrators will disable the ability to import registry changes.

You can try importing the registry file from the command line and see if that works. Open a Command Prompt window and navigate to the folder where you saved the .reg file that you downloaded. It can be imported using REGEDIT from the command line.

regedit FixVBSFileAssociationsXP.reg

You can repair your .reg file associations with one of the files below. You’ll likely need to import it as I’ve shown you above.

FixREGFileAssociationsXP.reg
FixREGFileAssociationsVista.reg

As for your error message, see my post “There is no script engine for file extension” error when opening .vbs files.

By: Peter A

Peter A — Thu, 09 Jul 2009 23:36:58 +0000

Followed instructions. Tried to run a VBS Script and got the following error message:

Windows Script Host

There is no script engine for file extension “.vbs”"

The clicked to download the fix for XP that you provided but when I ran it, I just got a few lines of code in Notepad and the reg file didn’t run.

Help