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

Multiple computers getting netio.sys BSOD after 2022.2.1.9 update

We're having an outbreak of DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD's in driver NETIO.SYS. Netio.sys caused BSOD's are usually tied to network drivers but that doesn't make sense because this started happening all of a sudden on multiple computers. These are fully patched/updated Windows 10 Pro computers. The common thing we're seeing is Sophos was updated to version 2022.2.1.9 around 7/20/22 on all of them. Any insight from Sophos on if the blue screen of death crashes are being caused by the latest version of Sophos?

This thread was automatically locked due to age.

Top Replies

BBallLAL over 2 years ago in reply to Matthew Marsh +5

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…

Parents

0 soph-f over 2 years ago

Sophos, we really need a final fix for this! Any official announcements on Update release date? If yes, please update KB accordingly! We‘re talking about nearly three month without official fix available (except beta patch on manual request).

or do general rollback to 2022.2.1.9?

Degrading security by disabling webcontrol and real-time scanning is no real acceptable workaround for multiple weeks/month! Aren‘t we talking about security?!
Cancel
Vote Up 0 Vote Down

Cancel
0 BBallLAL over 2 years ago in reply to soph-f

The next release on 11/10 contains a fix for this. If you open a ticket they'll give you a version you can install as a workaround.
Cancel
Vote Up 0 Vote Down

Cancel
0 Eric Connelly over 2 years ago in reply to BBallLAL

I received the fix from support (a specific driver file to replace) but it seems like it gets reverted back every day, I'm assuming when Sophos updates. Is there a way to get the workaround to stay put?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Eric Connelly over 2 years ago in reply to BBallLAL

I received the fix from support (a specific driver file to replace) but it seems like it gets reverted back every day, I'm assuming when Sophos updates. Is there a way to get the workaround to stay put?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 BBallLAL over 2 years ago in reply to Eric Connelly

AutoUpdate may replace the sntp.sys driver with the expected version so stopping and disabling the Sophos AutoUpdate service may also be required
Cancel
Vote Up 0 Vote Down

Cancel
0 soph-f over 2 years ago in reply to BBallLAL

…so having next problem: missing updates by disabling autoupdate?
Cancel
Vote Up +1 Vote Down

Cancel