Lỗi there is no script engine for file extension exe năm 2024

When you run a VBScript or .msi setup file that runs a VBScript, you may receive one of the following errors:

Can't find script engine "VBScript" for script C:\ProgramData\Microsoft\Windows\OFFICEICON.vbs There is no script engine for file extension ".vbs".

This happens if the vbscript.dll module is not registered correctly or the .VBS file association settings are broken. This error can be fixed using the steps listed below, applies to Windows Vista, 7, 8, 8.1, and 10.

Step 1: Fix .VBS file association settings

Download and apply the .vbs association fix from the following link.

• Windows Vista | Windows 7 | Windows 8 | Windows 10

Step 2: Register Vbscript.dll from admin Command Prompt

For Windows 8 and earlier only:

Open an elevated Command Prompt window.

regsvr32 %systemroot%\system32\vbscript.dll

You should see the DllRegisterServer in vbscript.dll succeeded.

If you’re using Windows 64-bit, run the following command in addition:

%systemroot%\SysWOW64\regsvr32.exe %systemroot%\SysWOW64\vbscript.dll

Step 3: Download the Vbscript.dll Registration Entries

If Steps 1 & 2 don’t resolve the problem, download the VBScript.dll registration entries.

• vbscript.reg for 32-bit (download)
• vbscript.reg for 64-bit (download)

Unzip and run the enclosed REG file.

Note that the paths are coded for `C:`. If the system drive letter is different than `C:` in your case, edit the REG file using notepad, and update the correct path.

The REG files fix the VBScript DLL CLSID key in the following registry path:

HKEY_CLASSES_ROOT\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}

See also

Error “There is no script engine for file extension” when running .js files

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:

• Pin it!
• Share it to your favorite blog + Facebook, Reddit
• Tweet it! So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

Earlier this week, I experienced the error message “There is no script engine for file extension “.vbs”“ on computers running both Windows 10 and Windows 11. In this article I will talk about what I tried unsuccessfully and then successfully to fix it.

You will most likely experience this error message when launching a program or installer that tries to run a .vbs script. For me it was shown just a few seconds after launching the PostgreSQL 14 installer and was blocking me from completing the installation.

What are VBS files?

The error message will either describe a problem with VBS or VBX files. These files are Visual Basic scripts that should normally be run by the Windows Script Host (wscript.exe).

Root cause

There seems to be a few different root causes for this problem. Either a program like Notepad++ has become associated with these files instead of wscript.exe, or alternatively the problem might be caused by a Windows Group Policy (GPO).

Luckily, it’s quite easy to fix the issue, no matter the root cause.

The fix that didn’t work for me

Several posts on Stack Overflow talk about running Notepad++ as an administrator, opening the Settings > Preferences > File Associations menu and removing the association to VBS files.

This did not fix my issues, since Notepad++ wasn’t associated with VBS files to begin with.

The fix that worked for me

And finally, this is how I managed to resolve the issue. Note: for some reason I had to run through these steps twice on Windows 10 but not Windows 11.

1. Open Command prompt as an administrator and then run the below commands. These will force Windows to re-associate the Visual Basic files with Windows Script Host.

assoc .vbs vbs=VBSFile assoc .vbx vbs=VBSFile

2. Re-register the DLL file used to run these scripts. Type the following into the open admin command prompt window.

The “script engine” error occurs if the .js file association data is missing or incorrect. Follow these steps to resolve the problem:

1. Open an elevated Command Prompt window.
2. Type the following command and press Enter: regsvr32 %systemroot%\system32\jscript.dll
3. Type exit to close the Command Prompt window.
4. Right-click jscript_fix.reg (zipped), click “Save Target as” or the equivalent option in your browser, and save the file to the desktop.
5. Unzip the archive, and double-click on the .reg file to apply the settings. The fix applies to all versions of Windows, including Windows 10.
6. Click Yes when asked for confirmation.

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:

• Pin it!
• Share it to your favorite blog + Facebook, Reddit
• Tweet it! So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.