‘Can’t find script engine …’ / ‘A script for the specified language can not be created’ error messages

MediaMonkey Addons (scripts) depend upon the Windows Scripting framework to run. If it isn’t installed or configured correctly, then Addons may fail or show errors.

‘Can’t find script engine …’

Some antivirus applications may prevent scripts from being registered; this error can occur if the antivirus application tries to scan an Addon before allowing it to be run by Windows’ scripting engine, and fails to find the vbscript.dll file after scanning is complete.

The problem is sometimes introduced after Microsoft patch MS10-020 has been installed and Kaspersky Internet Security is running.

To resolve the ‘Can’t find script engine …’ error, you may edit the registry using REGEDIT:

[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

And write “C:\Windows\system32\vbscript.dll” as key values


[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

And write “C:\Windows\SysWOW64\vbscript.dll” as key values

‘A script for the specified language can not be created’

On some systems (particularly x64 systems), User Access Controls (UAC) may interfere with proper registration of scripting components, resulting in the above error.

To resolve the ‘A script for the specified language can not be created’:

  1. Run CMD in administrator mode (click the Windows Start button -> type CMD in the search bar and right click, then choose execute as administrator).
  2. Type/execute “cd \windows\syswow64” (“cd \windows\system32” for 32 Bit windows)
  3. Type/execute “regsvr32 /U vbscript.dll” to unregister Visual Basic Script (vbscript) and Windows Scripting Host (WSH) library if it is registered
    Type/execute “regsvr32 vbscript.dll” to register Visual Basic Script (vbscript) and Windows Scripting Host (WSH) library
  4. Type/execute “regsvr32 /U jscript.dll” to unregister Java Script (jscript) library if it is registered
    Type/execute “regsvr32 jscript.dll” to register Java Script (jscript) library
  5. Type/execute “regsvr32 /U scrrun.dll” to unregister Microsoft Script Runtime library if it is registered
    Type/execute “regsvr32 scrrun.dll” to register Microsoft Script Runtime library
  6. Type/execute “regsvr32 /U msscript.ocx” to register Microsoft Script Control library if it is registered
    Type/execute “regsvr32 msscript.ocx” to register Microsoft Script Control library

    After registering these libraries MediaMonkey and any third party addons / scripts should work without issues.

    Note: To test VBScript, you can use the following test show the VBScript Version on your system:
    http://www.happymonkeying.com/eSupport/Test_VBscript.exe should show VBScript Version.
    If it fails to display the version, there may still be a problem with scripting on your system.

NOTES

  • Editing the Windows Registry is not without risk. Make sure you familiarize yourself with the Windows Registry through online searches prior to modifying it.

Applies to:

Was this article helpful?