The cumulative update was released for Windows 10 version 1703 (KB4041676), Windows 10 version 1607 (KB4041691), and Windows Server 2016 (KB4041691) for WSUS/SCCM managed devices.
Microsoft has addressed the issue and said they are aware of it. The problem occurred due to a “publishing issue” at the company’s end. Without mentioning further details about why it happened, they have corrected the publishing issue and validated the updates.
Users who had downloaded the cumulative updates through Windows Update and Windows Update for Business weren’t affected.
Microsoft has suggested that the WSUS (Windows Server Update Services) and SCCM (System Center Configuration Manager) customers having affected devices can consider mitigation plans for the following scenarios:
- WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4pm 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.
Solutions for these can be found on Microsoft’s support page describing the issue.
Also Read: Microsoft Wants To Put Fingerprint Sensor In Keyboard Keys, Files Patent