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

Shh/Updater-B - Web protection is no longer functional [0xa058000c]

All my machines now has these error on them after the Shh/Updater-B problem.

Web protection is no longer functional. The filtering driver has been bypassed or unloaded [0xa058000c]

Any idea's on how to fix this?  reprotecting a machine does not fix the error.  Just comes right back.

:31647


This thread was automatically locked due to age.
  • Same here.

    I've searched the link that was listed, and the whole board.
    There are only (3) threads with this "Web protection is no longer functional" keyword!

    Sophos... Stop passing the buck!
    "THIS" thread here is the most appropriate one to deal with it!

    Stop telling us to look at some other link with 116 pages that doesn't even discuss this error.

    -------------------------------------------------------------------------------------------

    I did find one thread...

    (/search?q= 24721)


    talked about ....

    Re: Unable to authorize applicationThu 17-May-2012 12:52
    I've just spoken to support and the issue with my clients reporting issues with web protection is an issue with the Web Protection and what it attempts to insert into winsock. This conflicts with the transparent ISA server I have and therefore produces this error. Sophos are very aware of this issue and it's to be fixed in an upcoming release (He thinks August with v10.6). Temp fix is to disable WP within EC and roll out the policy change (reboot needed on clients). Great to know it's not just me and Sophos are aware of the problem.
    :32961
  • Have you tried to reset the winsocks?  I've had issues with winsock causing the web protection not to work correctly. 

    :32965
  • "Have you tried to reset the winsocks?  I've had issues with winsock causing the web protection not to work correctly."

    You mean like this.....
    http://support.microsoft.com/kb/299357

    :32969
  • you can type the command in.  "netsh winsock reset"

    if that doesnt clear it, try, "netsh winsock reset catalog"

    you'll need to reboot after you do it, but you can use PSEXEC to do it as well

    :32973
  • Resetting the winsock "did" help me.

    Thanks to hitechgreg for offering help.

    I ran this from a remote commandline....

    R:\@Queries\psexec -s \\(remote pc here) netsh int ip reset c:\_Reset_Winsock.txt
    :33209