⋮    ⋮  

[Update x2] Last Night’s Mandatory Security Update Is Sending Some Windows 10 PCs into a BSOD Bootloop – How to Fix


[Update, Oct 11]: Microsoft tells Wccftech problem has now been resolved.

[Update, Oct 12]: Official workaround and fixes

How to Fix Windows 10 Stuck on Checking for Updates Issue

In its Patch Tuesday releases yesterday, Microsoft sent fixes to over 62 security vulnerabilities, including several that were rated critical or were zero-days. An extremely important update, we had suggested our readers install the patches right away as some flaws were already spotted in targeted attacks. Turns out the update is creating problems for some machines that are running the latest Windows 10 Creators Update.

Windows 10 users report facing BSOD after installing October Patch KB4041676

After last night's security updates that brought those on the Windows 10 Creators Update up to cumulative build 15063.674, some users woke up to face the infamous Blue Screen of Death (BSOD). After automatic installation of last night's security updates, the security patch, KB4041676, appears to be failing for quite a few people. The affected machines reportedly turn into useless junk temporarily since the update puts them into an endless reboot loop.

A user who reported facing the issue on all their Windows 10 machines, including HP, Dell and Lenovo systems, said (emphasis is ours):

I deploy patches via SCCM on a regular basis to nearly 5500 clients worldwide. My first group of Alpha systems which contains all of my own workstations receive the first round of patches as a test. ALL of the systems running 1703 blue screen upon reboot AFTER applying this patch (KB4041676).

The message that comes up is INACCESSIBLE BOOT DEVICE. After that, it reboots automatically, attempts to boot again, and then displays the "Automatic Repair" screen. None of these systems make it past this message.

My ALPHA test systems range from brand new Lenovo laptops, 2 Lenovo desktops, 1 Dell desktop, 2 custom built desktops, and 10 VMs.

What now Microsoft?

One reason that has come up so far is that the mandatory update often fails on systems with support for USB Type-C Connector System Software Interface (USCI). it is suggested to go into the system BIOS and disable UCSI before to applying the updates. However, some have reported this issue on systems without USB Type-C.

We have reached out to Microsoft for a comment, but until an official explanation and/or a workaround is offered, a user on Reddit has suggested a fix - head over here for complete instructions to fix the Windows 10 BSOD issue.

Microsoft Finally Acknowledges Windows 10 v2004 BSOD Errors on Lenovo ThinkPads

[Update] Fixed now; only affected enterprise users

In an emailed statement to Wccftech, a Microsoft spokesperson said that the issue has now been resolved and never impacted customers who receive updates via Windows Update. The company suggests that it only affected enterprise consumers.

"Some customers may have experienced issues in Windows Server Update Services (WSUS) deployment of KB 4041676and KB 4041691, which has been resolved. Most customers receive updates from Windows and Microsoft Update, and were not affected."

As reported earlier, this is a very critical security update and should be installed on all Windows 10 versions being supported by the company.

[Update]: Here's the official workaround

Despite some reports suggesting that Windows 10 Home users are also impacted, Microsoft continues to say that only enterprise consumers were affected. The company has recommended users to clear the cache on WSUS servers to ensure that latest packages are available.

  1. WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4pm PDT October 10 may still have these KBs cached.
  2. WSUS/SCCM managed devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have devices in a pending reboot state.
  3. 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.

Official workarounds to the above scenarios are shared by the company in this post.