Multiple computers getting netio.sys BSOD after 2022.2.1.9 update

We are starting to see more user reports about this in our environment. Mostly Lenovo machines, and we're also using Cisco AnyConnect.

Over two weeks since I reported it and still no resolution.

I apologize for the frustrations. Looking into the development ticket open for this issue, there’s work being done each day. Our team is actively working towards finding a resolution. 

If you need an immediate work-around to be implemented, you can use the following steps published in the KBA, though I understand that this is not ideal for all organizations. 

Turn off the following within Sophos Central:

• Web Control - Disable the policy that applies to the user for that system
• Threat Protection - Turn off all settings under "Real-time scanning - Internet"

Now at 3 weeks since first reported, still no updates except work arounds. Makes me wonder what their QA process is for new releases...

Yes, it's mindblowing that it would take a multi billion $ company this long to fix it. At least have an option for those affected by bad sofwtare updates to rollback to the previous version instead of making us disable protection making us more vulnerable. 

Yeah we are still having this issue. Just happened to our CEO in the middle of a meeting. My IT manager is suggesting that if they don't get this fixed soon that we will be researching a new AV solution for next year.

It seems like the workaround has helped, but it's hard to verify at this point since it seems like not all of our users are actually reporting their BSODs.

Hello Qoosh, is there any update on the development ticket? We still have daily occurrences of BSODs. So far none after disabling the protection features for affected users as per the KB, but we can't generally disable those for all systems.

Hello Qoosh, is there any update on the development ticket? We still have daily occurrences of BSODs. So far none after disabling the protection features for affected users as per the KB, but we can't generally disable those for all systems.

On 8/22 I was asked to test a build that fixes the issue. I wasn't able to test it since we can't use our call center agents as guinea pigs since every time their computer crashes from a BSOD it causes a negative customer experience. Hopefully there is light at the end of the long drawn out tunnel. 

I can see an update today stating that the latest test build has allowed systems to remain stable for about a week without any crashing symptoms.

If you require the test build sooner, I suggest working with our support team to get access to it. I don't have an ETA yet for when this will be released to all customers.

I have send email to my Sophos contact case# for access to this new build. We had about 20 new incidents with this issue today... The Sophos temporary workaround is NOT the best solution.