2 Replies Latest reply on Aug 31, 2017 9:05 PM by dbareis

    Can't find script engine vbscript error at login

    boopathis84

      Hi,

      few users reported that "Can't find script engine vbscript" error when they login in each time. Verified in blogs and found the below solution.

       

      1. Open regedit as administrator
      2. Browse to the following key:

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

      1. Right-click this key and select "Permissions..."
      2. Select the "Administrators" group and click the check-box for Allow "Full Control"
      3. Edit the "(Default)" key's value and change it:

      FROM: C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.20140819031109.dll

      TO: C:\Windows\system32\vbscript.dll

       

       

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

      1. Right-click this key and select "Permissions..."
      2. Select the "Administrators" group and click the check-box for Allow "Full Control"
      3. Edit the "(Default)" key's value and change it:

      FROM: C:\Program Files (x86)\Common Files\McAfee\SystemCore\ScriptSn.20140819031109.dll

      TO: C:\Windows\system32\vbscript.dll

       

      Why Mcafee Causes the issue, can anyone explain and why this error occurs

        • 1. Re: Can't find script engine vbscript error at login
          frank_enser

          Hi,

           

          according to McAfee, this is due to an uninstall/upgrade bug, see KB86138.

           

          Regards,

          Frank

          1 of 1 people found this helpful
          • 2. Re: Can't find script engine vbscript error at login
            dbareis

            The KB is wrong, this is my list (regjump.exe is a SysInternals tool):

             

            :: ### The following fixes are for 32 or 64 bit OS ###

            :: [step 2]  RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32

                                ::(DEFAULT) C:\Windows\system32\vbscript.dll

            :: [missing] RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32

                                ::(DEFAULT) C:\Windows\system32\vbscript.dll

            :: [step 6]  RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}\InprocServer32

                                ::(DEFAULT) C:\Windows\system32\jscript.dll  (KB VALUE WRONG!!!!!!!)

             

             

                               

            :: ### The following fixes 32 bit scripting on 64 bit OS (so for 64 bit OS only) ###                   

            :: [step 8]  RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32

                                ::(DEFAULT) C:\Windows\syswow64\vbscript.dll  (KB VALUE WRONG!!!!!!!)

            :: [missing] RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32

                                ::(DEFAULT) C:\Windows\syswow64\vbscript.dll

            :: [step 10] RegJump HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}\InprocServer32

                                ::(DEFAULT) C:\Windows\syswow64\jscript.dll  (KB VALUE WRONG!!!!!!!)