The problem actually came with “Patch Tuesday” update on October 10. However, after publishing, Microsoft forums started to get many complaints from Windows users on PCs from various manufacturers and even on individually assembled computers. Microsoft assigns the problem to a publishing error, primarily hitting corporate clients. The “blue screen of death” hit computers running Windows 10 version 1703 (KB4041676), Windows 10 version 1607 (KB4041691), and Windows Server 2016 (KB4041691) for WSUS/SCCM managed devices. A company representative on the forums said that Microsoft is aware of it. The problem occurred because of a “publishing issue” at the company’s end and the computers that got them both ran into problems. Well, users who have downloaded the cumulative updates through Windows update and Windows update for Business aren’t affected. The WSUS/SCCM customers having affected devices can consider mitigating plans for the following scenarios:
WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4 pm PDT October 10 may still have these KBs cached. WSUS/SCCM managed devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have devices in a pending reboot state. WSUS/SCCM managed devices that installed the October 10 KB4041676 or KB4041691 update and are unable to boot and/or may land on a recovery screen
If you are among the affected users, then you need to visit Microsoft’s support page for the solutions. So, what do you think about this? Share your views in the comment box below.
