Reports are coming in left and proper that the latest safety updates for Windows 7, Windows eight.1, Windows Server 2008 R2 and Windows Server 2012 R2 are causing issues on machines they’re put in on below sure circumstances.
I added a notice to the Tuesday’s Patch Overview for this month’s Windows updates however the situation seems much more widespread than thought initially.
Update: Microsoft added the problem to the recognized issues on help pages that highlights the incompatibility situation with Sophos merchandise. Microsoft blocked units with affected Sophos software program from receiving the replace.
What we all know up to now
The situation impacts pre-Windows 10 working techniques solely, not less than that’s what is been reported on the time. In different phrases: Windows 7, Windows eight.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.
The updates that will trigger issues are:
- KB4493448 Security-only replace for Windows 7 SP1 and Windows Server 2008 R2 SP1
- KB4493472 Monthly rollup replace for Windows 7 SP1 and Windows Server 2008 R2 SP1
- KB4493467 Security-only replace for Windows eight.1 and Windows Server 2012 R2
- KB4493446 Monthly rollup replace for Windows eight.1 and Windows Server 2012 R2
- KB4493450 Security-only replace for Windows Server 2012
- KB4493451 Monthly rollup replace for Windows Server 2012
Sophos stories that machines with the replace might fail as well. The laptop mentions techniques with Sophos Central Endpoint and SEC put in particularly and recommends to not set up the brand new replace at this time limit.
If the replace is put in already, Sophos recommends booting into Safe Mode, disabling Sophos Antivirus, booting into the common system, uninstalling the Windows update there, and enabling the Sophos Anti-Virus service afterward.
Avast published a help article on the corporate’s KB website that describes the same situation. The firm stories that PCs operating Avast for Business and Avast Cloud Care on Windows machines might change into locked or frozen on begin after putting in the brand new Windows updates.
Windows machines (notably these operating Windows 7) have gotten locked or frozen on startup after Microsoft updates KB4493472, KB4493448, and KB4493435.
Some of those machines are utterly unable to log in, and some log in after a really prolonged time period.
Avast means that customers roll again the replace as nicely and has printed directions on how to take action on the linked help web page.
Microsoft has but to acknowledge the problem; no help article lists the issue as a recognized situation but.
It remains to be really useful to create a system backup prior to installing any new replace for Windows in your machines.
Now You: are you influenced by issues after putting in these updates? (by way of Ask Woody)