Microsoft Windows 10, Server 2016 patching error borks users' systems
A problem with the way that Microsoft released some of this week’s Patch Tuesday updates caused some users’ PCs and servers to blue screen, hang and/or fail to reboot.
MJ Foley
Updates Microsoft issued for Windows 10 1703 (Windows 10 Creators Update), Windows 10 1607 (Windows 10 Anniversary Update) and Windows Server 2016 caused havoc for a number of business customers who deployed them as part of the October 10 Patch Tuesday release. The updates causing the problems after installation were KB4041676 and KB4041691.
It pparently was not the patches themselves, but the fact Microsoft accidentally published to Windows Server Update Services (WSUS) and System Center Configuration Manager both Cumulative and Delta updates that could be installed on machines together that caused the problems. As Microsoft doesn’t publish Delta updates to Microsoft Update, this problem shouldn’t have affected consumers, as they don’t use WSUS and Configuration Manager.
As Microsoft explained in an article on its docs.com site, “If you approve and deploy the same version of the Delta and Cumulative update, you will not only generate additional network traffic since both will be downloaded to the PC, but you may not be able to reboot your computer to Windows after restart.”
There are steps those affected can take to get their systems working again that are detailed in that same article on the Microsoft docs.com site.
Another site, DeploymentBunny.com, has some additional options for those who can’t reboot after both the Cumulative and Delta updates were applied together. This one, WorkingHardinIT.Work, steps through using DISM (the Deployment Image Servicing and Management command-line tool) to remove the updates.
Users should apply the Cumulative Updates only and not the Delta updates. Customers are being advised to re-synchronise their WSUS/SCCM servers and the Delta Updates Binaries will be expired.
I’ve asked Microsoft for further information as to who was affected and any other additional steps it is advising users to take. No word back so far.