There is no script engine for file extension “.vbs”
Posted by kiranpatils on August 13, 2009
Challenge:
If you received an error saying There is no script engine for file extension “.vbs” then you are on right post 
Solution:
I tried doing this : regsvr32 %systemroot%\system32\vbscript.dll
But like you — for me too no luck 
But finally following trick worked for me
1. Locate the file %windir%\inf\wsh.inf (inf is a hidden
folder)
2.right click and select “Install”.
Happy Coding!!
Advertisement
Max said
Thanks alot, exactly what I was searching for!
bobby said
thanks this is what worked for me . I was working on it for last 12 hrs and finally got it
shuzaku said
wonderfull step thanks, keep go a head
kiranpatils said
Thanks!
smartflower2002 said
doesnt work for me, that file does not exist in my win directory ;(
smartflower2002 said
can anyone please upload that file, so i can try it
Hilbert said
After much messing around, kiranpatils’ suggestion [%windir%\inf\wsh.inf] on this site finally finished the problem (it actually worked well).
…However, it was only part of the solution. It included much other info too (and I’ve only included the most relevant references here):
1. “Restoring .vbs (VBScript Script File) File Associations”
Info here: http://www.nilpo.com/2009/07/windows-xp/restoring-vbs-vbscript-script-file-file-associations/
2. “regsvr32 %systemroot%\system32\vbscript.dll”
Info here: http://www.winhelponline.com/blog/error-there-is-no-script-engine-for-file-extension-when-running-vbs-files/
3. “Windows Script 5.7 for Windows XP”
Info here: http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-D896-482E-A0D6-524E7E844D81&displayLang=en
4. Various VBS stuff at http://www.kellys-korner-xp.com/taskbarplus!.htm
5. Doug Knox File assocoation info: http://www.dougknox.com/xp/file_assoc.htm (especially “VBS file association fix”).
This was one big messy problem and I could not have fixed it easily without the help of this site and all these other sites too.
Presumably, the problem was initially caused by some security program nuking all the VBS scripting.
Jim said
Hey Hilbert, one of your links may have had the answer for me! I’ll have to wait a few days to know for sure, but a poster (Asa) @ http://www.nilpo.com/2009/07/windows-xp/restoring-vbs-vbscript-script-file-file-associations/ uses the same program I do, and I think setting the file association in the program may be what is throwing Windows off…
“Asa Says:
May 29th, 2011 at 1:26 am
Pretty sure setting Notepad++ to associate with VBS files caused the problem for me (from the NP++ interface). I should probably let them know…”
But I’m not complaining! Other than this, (if turns out to truly be the problem), Notepad++ is an AWESOME, free, small, portable (no install/admin rights needed), powerful, intuitive script and programming app. Check it out if you haven’t already.
fantubilog said
initially the trick from kiran didn’t work for me… because I couldn’t find the file wsh.inf in my system (windows 7)
so I tried the link given by Hilbert above “Restoring .vbs (VBScript Script File) File Associations” … downloaded the file FixVBSFileAssociationsVista.reg.. applied it.. and its work…
(fyi.. my “.vbs” association is replaced by notepad++)
thanks kiran and hilbert…
good work
Magician said
works very well…Thank You.
John said
Awesome, tried this 100% working. Thank you heaps.
Todd said
Did this happen to anyone after a particular hotfix or service pack? I have the same issue on a Windows Server 2003 SP2 box. The .inf re-install will work but the file association is lost shortly thereafter. I don’t know how long this has been occurring but have an idea that it started after I last rolled updates to this box one month ago.
Jim said
I have the same problem. The .inf fix works, but then a few days later the problem is back. I wonder if the antivirus (McAfee) is killing the scripts or scripting host? I don’t know when the problem started, because we just recently started using a vbscript logon script. (They were mapping drives, printers, etc. manually before… hard to convince them this is “better” when this keeps happening! LOL)
Sushmita said
This really helped.. I was not able to run backup and after running this, it worked.. thanks a lot..
1. Locate the file %windir%\inf\wsh.inf (inf is a hidden
folder)
2.right click and select “Install”.
Hammer said
Worked like a champ.
Varun Shringarpure said
Thanks Kiran..!
The solution rele worked..
After searching a lot on the net finally got the solution..
Thanks to your Blog..
You Rock Man..! Cheers..!
kiranpatils said
Thanks Varun!
Tim said
You, my friend, are a god-send. This is exactly the fix I needed. I’ve spent a couple days trying to get my vbs files to work and was about to give up and rebuild this XP machine.
Thank you.
ane said
Thanks a lot it worked for me…
kiranpatils said
Thanks! – Glad to know that it worked for you!
Happy Reading!
Cheers,
Kiran
BillyBob said
Thank god there are people like you. And of course all you others that came here as me…
Thnaks
/Ralf
kiranpatils said
Thanks!
Happy Reading!
Cheers,
Kiran
Josh Livingston said
THANK YOU THANK YOU! Days of Tracking down solution NONE WORKED!!! EXCEPT
YOURS! This is was a great Help. Thank you Very Much. Even Microsofts sight, did not have this solution for this probolem….like that is a surprise!
kiranpatils said
Thanks Josh!
Happy Reading!
Cheers,
Kiran
pankaj garg said
no such file exist in my win directory suggest me another solution…..
S.E. said
It works. I can only ask: what was the cause? One moment my script ran fine, the other moment I had the error message. The only thing that happened inbetween was launching Notepad++. Is it possible that Notepad++ is the culprit?
Richard said
Thanks.
Rick said
I can’t find %windir%\inf\wsh.inf anywhere in my machine. Win 7 Pro. I am trying to install CorelPDFFusion ang get the There is no script engine for file extension “.vbs” message. Can you help?
Mike said
Have this problem with W2K machine and stumbled across this “fix”.
Noticed in Explorer\Tools\Folder Options\File Types where you can
define your file associations that there was a .vbe extension that
was associated with vbs. I renamed the .vbs script I wanted to run
to .vbe and it worked.
What didn’t work was then duplicating all the .vbe association paths to
the .vbs, so the problem dosn’t appear to be there.