SpywareBlaster blocking Microsoft File Transfer Manager

Discussion in 'SpywareBlaster & Other Forum' started by odditude, May 16, 2010.

Thread Status:
Not open for further replies.
  1. odditude

    odditude Registered Member

    Joined:
    May 16, 2010
    Posts:
    3
    SpywareBlaster is blocking the Microsoft File Transfer Manager, used on microsoft.com for MSDN and TechNet downloads.

    CLSID: {82774781-8F4E-11D1-AB1C-0000F8773BF0}

    Please remove this from the block list.
     
  2. javacool

    javacool BrightFort Moderator

    Joined:
    Feb 10, 2002
    Posts:
    3,997
    Hi,

    SpywareBlaster does not block that CLSID.

    What other software do you have installed? Are you using a "Custom Block List" in SpywareBlaster?

    (For future reference: You can search the built-in block lists for CLSIDs by simply right-clicking on any Block List, and selecting the "Find..." option.)

    Best regards,

    -Javacool
     
  3. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
  4. odditude

    odditude Registered Member

    Joined:
    May 16, 2010
    Posts:
    3
    There are no custom blocklists in use; any/all SpywareBlaster settings should be at their defaults.

    Thanks for the tip for right-click/Find; I wasn't aware of that.

    FTM was failing to run (it was prompting for reinstallation of the ActiveX control each time, ad infinitum). I disabled all protection in SpywareBlaster, restarted IE, and FTM worked afterward. I then re-enabled all protection, restarted IE, and FTM was broken again.

    OS is Win7 x64, browser is IE8 (32-bit).
     
  5. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    did you look for that clsid in your SB install?
     
  6. odditude

    odditude Registered Member

    Joined:
    May 16, 2010
    Posts:
    3
    Sorry for the delay in responding. The CLSID wasn't on the list; I'm at a loss for what the problem was.

    That being said, the problem has resolved itself sometime over the past three weeks. Unfortunately, I don't know if that was due to a SpywareBlaster list update or the last batch of Windows Updates.

    Thanks for the assistance - I know it was my own slow response time that kept you from being more helpful!
     
Loading...
Thread Status:
Not open for further replies.