How To Fix: Can’t find script engine “VBScript” for script error

Can’t find script engine “VBScript” for script – this error message may occur when you try to run a program that uses VBScript – a Microsoft programming language modeled on Visual Basic and included in Internet Explorer.

I first encountered it while testing a program to quickly create a system restore point but there are thousands of other programs that also use VBScript.

VBScript relies upon a specific file (vbscript.dll) being present and correctly registered in Windows.

If it isn’t (usually caused by a faulty uninstall of an antivirus program) this error message appears – in my own experience, Avast and McAfee are the most likely culprits…

Here are two fixes to resolve such an error – the first is to correctly re-register the vbscript.dll file and the second is to repair a specific registry setting, if required.

Can’t find script engine "VBScript" error message

1. Re-register The Dll File

  • Open an elevated (administrator) Command Prompt window by doing the following:

Windows 10, 8, 7 or Vista only – click Click ‘Start’ and type CMD into the search box. Right click on the ‘CMD’ program in the search results and select ‘Run As administrator

You may now see a User Account Control message asking “Do you want to allow the following program to make changes to this computer?”. Click on ‘Yes’ to confirm.

This will open an elevated (Administrator) level Command Prompt window – notice that the title of this window is ‘Administrator: Command Prompt’ which shows that it is running with elevated system privileges. Skip to ‘All versions of Windows’ below.

XP only – click ‘Start’ and type CMD into the search box. Click on the ‘CMD’ program in the search results to open an elevated (Administrator) level Command Prompt window.

Type the following command then press Enter: cd %windir%\system32

  • All versions of Windows – you should now be in the C:\Windows\system32 directory. Type regsvr32 vbscript.dll then press Enter.

You should see a message that the operation succeeded – press OK then close the Command Prompt window.

Tip: if the operation says that vbscript.dll was not found (and you’re sure you ran the command from the system32 folder as above) then try to replace the missing vbscript.dll file by using System File Checker.

Now run the program that uses VBScript again and see if this fix works – if you still get the same Can’t find script engine “VBScript” error message, proceed to the next fix.

2. Repair VBScript Language Registry Setting

Be careful when editing the registry – create a System Restore point first for safety or take a backup e.g. with the Tweaking.com registry backup utility.

1. Open the Registry Editor:

  • XP – click Start \ Run and type regedit into the Run box then press OK
  • Windows 10, 8, 7, Vista – click Start and type regedit into the Search box then click on the regedit.exe entry in the search results

2. In the Registry Editor, browse to the following key:

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

The entry called (Default) should have a value of C:\Windows\system32\vbscript.dll as shown below (ignore the Default Engine and ThreadingModel entries, you may have different ones):

InprocServer32 Default value

Correct value of (Default)

However, an old antivirus may have set the value of (Default) to something else and, when uninstalled, it has not removed it.

So the incorrect value is still shown as below:

InprocServer32 incorrect default value by Avast

Incorrect value of (Default) – set by Avast (long since uninstalled)

If the value of (Default) is not correct then double click it and change its value to:

C:\Windows\system32\vbscript.dll then press OK.

Note: if you get an ‘Error Editing Value’ error message when you press OK, change the permissions of the InprocServer32 registry key then try again.

3. Close the Registry Editor and restart the computer.

4. Now run the program that uses VBScript again – if the incorrect registry setting was the cause of the error, it should now work ok.

Why Is The Registry Change Required?

The (Default) value defines the .dll file to be used by VBScript – by default this is vbscript.dll

Some antivirus programs change this value to point to their own .dll file so they process the scripts to check them for signs of malicious behavior – a good thing.

However, this becomes a problem if the antivirus is uninstalled (and so deletes its own .dll file) but does not also change the (Default) value back to the original vbscript.dll file location…

In this case, a program may continue to look for the old antivirus .dll file, but that no longer exists – causing the error message that “VBScript” cannot be found.

Conclusion

There are many causes for VBScript error messages but this particular one is most often caused by a poorly coded uninstall of an antivirus program.

I have seen Avast! uninstallation cause this problem many times and McAfee can also be responsible – there may be several other antivirus programs to blame.

Share this:

22 Responses to: "How To Fix: Can’t find script engine “VBScript” for script error"

  1. Everton Godoy says:

    Perfect, it worked properly.

    Thank you very much for the tip .

Leave a reply