Sophos EC - Web protection unloaded on multiple endpoints

[DavR]

Have any Sophos users out there found that they are getting multiple errors in the Enterprise Console about Web Protection being unloaded?

 

I have this error "Web protection is no longer functional. The filtering driver has been bypassed or unloaded [0xa058000c]" on whole bunches of PCs, as described here.

 

As far as I can see web protection is totally knackered, and I'm going to need to reinstall half of our endpoints, unless anyone out there has seen this and can offer some advice?

 

We're freshly built Windows 10 over the holidays, so I'm surprised we're getting endpoint failures so soon. Perhaps September Cumulative Update has knackered part of Sophos.

[jojida]

We are seeing this same issue on machines that were recently upgraded to 1703 within the past 3 weeks. Tried KB114350 with no luck what so ever. Submitted a ticket with Sophos but have not received any help with this issue as of yet. Tried to Re-Protect, along with moving machines to and from groups where the items stated in the KB to turn off with Zero luck. Next day the same machines pop back up.

[DavR]

Same here, did a bunch of reinstalls from the console last week and the errors just keep coming back. Also 1703, clean installs all of them.

 

I'll log it with our support (LGfL) and see if they've got any ideas. I needed to speak to them anyway about upgrading to the cloud based console.

[DarrenShan]

Same issue here, only on 1703 machines.

[DavR]

It's not a resolution as such, but I've upgraded to Sophos Central, the web-based EC, as this is included in my broadband services contract (LGfL).

 

This has a different client (although a lot of the same underlying technologies) so hopefully won't have the issue.

[jojida]

A week has gone by along with a few phone calls into Sophos about this issue with no follow up what so ever. Not sure what is going on but hopefully it isn't something that is widespread beyond a few rogue incidents.

[jimatjude]

HI,

 

We have the same issue on multiple Window 10 systems. As it appears from above thread, the issue shows up after upgrade to v1703 -- or an update to 1703. Has anyone found a viable solution yet?

Thanks

Jim at Jude