We'd love to hear about it! Click here to go to the product suggestion community
I have an open ticket with Sophos about this issue popping up on about 17 machines that were just recently updated to Windows 10 1703 from Windows 10 1607. Tried the following KB 114350 with Zero luck in getting this resolved. I have tried Uninstalling and Reinstalling both manually on the console, and through the "Protect Computers" option within the Enterprise Console. Even created a Group with the recommended policies as suggested within the KB article with no luck on that either. going to http://sophostest.com/malware/index.html to test and verify the machines are protected results in the website not being blocked. Looking for any ideas that might help resolve this issue once in for all.
In reply to Jamie Ojida:
Jamie / JAK
Thank you for sharing the details. I am setting it up now and will apply it to a subset of test systems. I will update later with results.
Thank you for sharing the details. I set this up and applied it to a subset of test systems. Results are mixed. The issue with Web Protection appears to be resolved. No additional errors reported. However, Edge still does not correctly block SophoTest pages, yet Chrome and Firefox on the same system will block correctly
In reply to John Comes:
If you look at the list of processes on the computer in Process Explorer, you should see the browser processes talking to swi_fc.exe.Looking at the TCP/IP tab of swi_fc.exe you should see the port swi_fc.exe is listening on, e.g. 12080In the case of Edge, the process talking to swi_fc.exe over loopback should be MicrosoftEdgeCP.exe.
To identify the process making the connection, if you open Edge, drag the cross-hair icon of Process Explorer onto the Edge Window it should focus in on one of the MicrosoftEdgeCP.exe processes in question.
If you look at the TCP/IP tab of that process, do you see it connecting to swi_fc.exe or straight out of the computer? If it's not pointing to the port swi_fc.exe is listening on then the redirection is not working.
In reply to jak:
We have been getting these two from the first day we deployed SEC.
I now have a Preview group setup but the issue for us is the W10 deployment not being done by department. so applying the preview is going to be kinda difficult.
Has there been any know issues with 10.7.6?
I have been also doing some testing with Windows 10 and Preview subscriptions.
It works but there is a flaw with subscription. You can't have an OU that has both Preview (newest version) and recommended (current version) AV software installed.
This can be a real big problem if you have other application that use the OU structure.
If you create an OU just for Preview the PCs in that OU can never move to an OU that has Recommended applied because preview will uninstall and recommended will install.
This not good and what I would call a major flaw.
So to add to this flaw, any time preview goes recommended any endpoints that have an issue with newest version will require you adjust your AD OU structure to apply the older version.
Correct me if I am wrong. And if I remember right you don't get to decide if you want preview to go recommended on your SEC, it will just happen as this is what happen to us when 10.7 replaced 10.6.
In reply to Navar Holmes:
The new update did not thing to fix this issue.
10.7.6.128 is deployed to 99.9% of all of our endpoints.
Why this even generates an error is confusing as we are not using the Web Controls. The default policy for it is not enabled.
Can anyone validate that this web protection error is tied to the Web controls and doesn't put the endpoints a risk?
I have just decided to check the SEC regularly select all of the errors and Acknowledge.
The functionality the check is testing implements the following features:
Not the exact names of the features but these are the 3 features (F1, F2, F3) that utilise the functionality being checked.Note: by default content scanning is set to mirror on-access, i.e. if on-access scanning is enabled so is Content scanning but you can turn it off.
It's only when the last one of the 3 features above are disabled does the component not check. On Windows 7 and 2008R2, you will need to reboot once disabled all features for the features to be totally disabled.The Web Protection features are key security features, Web control on the other hand is just that, more to control users browsing.
So that means with the on going Web protection is no longer functional errors the end-points are being put at risk.
Has any one had any success at getting this error resolved or are you having the same random end pint affected like I am.
Well on the Windows 10 platform, I believe the check runs 5 mins after startup and then every hour. The executables that perform the check (swi_lspdiag_64.exe and swi_lspdiag.exe) are launched from the swi_service. This is detailed in the first activity of the thread.I think it's a case of the checks can work, work, work, fail, work but I don't think the final work clears the previous fail message.You can test if web protection/control is working at any time by going to:http://www.sophostest.com/
For example: http://www.sophostest.com/malware will test malicious website lookups.
http://www.sophostest.com/eicar will test content downloads.
http://www.sophostest.com/adult will test web control if you're blocking/warning on the Adult category.