SHARE
TWEET

Untitled

a guest Dec 20th, 2012 3,312 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Alright, this issue seems to be occuring on 64bit systems that have previously had an antivirus installed that included a script scanner but have since uninstalled it
  2.  
  3. Software such as Avast, Mcafee, and several others are known to include these
  4.  
  5. A possible fix would be to use their specific removal tool for that product, but in case it doesn't work, the situation is as follows below.
  6.  
  7.  
  8. The problem occurs because the uninstall for the aforementioned software does not replace the invalid references to the no longer present script scanner with the original path in (Default) Reg_SZ at
  9.  
  10. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
  11.  
  12.  
  13. To correct this issue, you will be required to Take ownership of the {B54F3741-5B07-11cf-A4B0-00AA004A55E8} key and set the Administrator account to have full access permissions to it.
  14.  
  15. After this navigate to the InproServer32 subkey and revert the (Default) reg_sz to C:\Windows\SysWOW64\vbscript.dll
  16.  
  17. After doing this, you can remove the full control check from the administrator account, then Re-Set the Owner to NT Service\TrustedInstaller by copying or typing it into the Types Box and clicking Locate, then OK.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top