Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 17839 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot disable Sophos 10 LSP

ThisGuy

We're having issues disabling the Sophos 10 64-bit LSP using the following command:

C:\ProgramData\Sophos\Web Intelligence\swi_lsp32_util.exe -u -d swi_ifslsp_64.dll 

This works on he 32-bit version, but not the 64. After running the above command we get the following error:

retrieveLSPGUID: LoadLibraryA(swi_ifslsp_64.dll) failed: 193

Has anyone run into this before? Google didn't have much to say about that error. 

Thanks in advance. 

EDIT:

I forgot to add that I also tried using Windows 7 regsvr32 /u, but it did not work. I got the following error:

The module "C:\Program Data\Sophos\Web Intelligence\swi_ifslsp_64.dll" failed to load.

Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.

The specified module could not be found.

:55021


This thread was automatically locked due to age.
Parents
  • 0

    The LSP is disabled as a result of the following features being disabled:

    • Web Control
    • Download scanning
    • Malicious website blocking

    All 3 use the LSP but if all are disabled there is no need for the LSP.

    If the computer enters this state then a registry key value called swiupdateaction (off the top of my head) is created under the webintelligence registry key: hklm`software`sophos`webintelligence. It is given the value of 3 (if I recall correctly).

    When the Sophos Web Intelligence Update service next starts (typically at the next startup), if it reads a value of 3 it knows to remove the LSP from winsock.  You could just start the service when in this state to remove it, the idea behind it being deferred to start is to minimise issues with running applications.

    Regards,

    Jak

    :55030
Reply
  • 0

    The LSP is disabled as a result of the following features being disabled:

    • Web Control
    • Download scanning
    • Malicious website blocking

    All 3 use the LSP but if all are disabled there is no need for the LSP.

    If the computer enters this state then a registry key value called swiupdateaction (off the top of my head) is created under the webintelligence registry key: hklm`software`sophos`webintelligence. It is given the value of 3 (if I recall correctly).

    When the Sophos Web Intelligence Update service next starts (typically at the next startup), if it reads a value of 3 it knows to remove the LSP from winsock.  You could just start the service when in this state to remove it, the idea behind it being deferred to start is to minimise issues with running applications.

    Regards,

    Jak

    :55030
Children
No Data
Unfiltered HTML