A week ago, Microsoft released six patches that brought many machines to their knees. As I <\/span>explained last Friday<\/span><\/a>, when the dust cleared, it was apparent that all six of these April patches:<\/span><\/p>\n\n
![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security12-100734741-large.3x2.jpg\"\/)
<\/p>\n<\/p>\n
Credit to Author: Woody Leonhard| Date: Tue, 16 Apr 2019 08:02:00 -0700<\/strong><\/p>\n A week ago, Microsoft released six patches that brought many machines to their knees. As I <\/span>explained last Friday<\/span><\/a>, when the dust cleared, it was apparent that all six of these April patches:<\/span><\/p>\n would trigger blue screens on reboot on most systems running Sophos antivirus products, and many systems running AV products from Avast and Avira.<\/span><\/p>\n We now have updates from two of the three AV companies:<\/span><\/p>\n Microsoft says that it\u2019s still blocking the six bad actors from installing on computers with Sophos Endpoint installed. There\u2019s no similar advice for Avast.<\/span><\/p>\n Oddly, the <\/span>advisory page for Avira<\/span><\/a> now comes up with a \u201cpage not found.\u201d Yet Microsoft continues to contend, \u201cMicrosoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.\u201d<\/span><\/p>\n You may recall that Avira, alone among the three, also claimed that installing this month\u2019s first cumulative update for Win10 version 1809, KB 4493509, slowed machines down to the point they\u2019re unusable. No official word on that claim at this point.<\/span><\/p>\n Speaking of slowdowns, a small Polish AV company called ArcaBit has seen the error of its ways. Microsoft has modified its KB articles for the Win7 and 8.1 Monthly Rollups, and for the Win10 1809 first April cumulative update to say:<\/span><\/p>\n Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update. ArcaBit has released an update to address this issue.<\/span><\/p>\n Although the<\/span> linked ArcaBit article<\/span><\/a> has been pulled. Oddly (there\u2019s that word again), there\u2019s no analogous warning for the Win7 or 8.1 Security-only patches, or for the Server patches.<\/span><\/p>\n Where does that leave us, a week later? <\/span><\/p>\n I\u2019m still astounded by the indifference. Any way you slice it, whoever made the decision to release this month\u2019s six Win7, 8.1, and Server patches either:<\/span><\/p>\n I have a hard time deciding which is worse.<\/span><\/p>\n I continue to recommend that you <\/span>hold off<\/span><\/a> on the April patches.<\/span><\/p>\n We\u2019re following the situation intently <\/span><\/i>on AskWoody<\/span><\/i><\/a>.<\/span><\/i><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Tue, 16 Apr 2019 08:02:00 -0700<\/strong><\/p>\n A week ago, Microsoft released six patches that brought many machines to their knees. As I <\/span>explained last Friday<\/span><\/a>, when the dust cleared, it was apparent that all six of these April patches:<\/span><\/p>\n<\/p>\n\n