How To Update Windows 10 That Throws Bsod

Confusion reigns over Windows x update that causes blue screen of death

A freshly introduced update for Windows 10 has apparently been causing havoc with some users' machines, invoking the dreaded blueish screen of decease (BSOD), and in some cases triggering the fifty-fifty-more than-dreaded boot loop (i.e. repeated rebooting).

The trouble lies with update KB4041676 for Windows ten (Creators Update), and is described in this post on Microsoft's 'answers' community bulletin board, where the original affiche says: "My computer keeps restarting because windows update won't install KB4041676."

A further post (from SCCMGuy74) describes the trouble with multiple systems: "ALL of the systems running 1703 blue screen upon reboot AFTER applying this patch (KB4041676). The message that comes up is INACCESSIBLE BOOT DEVICE. Subsequently that, information technology reboots automatically, attempts to boot again, and then displays the 'Automatic Repair' screen. None of these systems make information technology past this message."

Now, this is where it gets thorny, because the Microsoft moderator on the post notes that this is caused by a 'dual patching disaster' in enterprise environments. In other words, it's not the fault of the update itself, but the fact that users have been led to install "both the delta update and the cumulative update which shouldn't accept been pushed to WSUS [Windows Server Update Services] last night".

Black Fri bargains might include cheap deals on Windows 10

Home free?

So, your average home user simply downloading updates from Windows Update shouldn't be afflicted by this issue – and however at that place are reports on that same thread from such users who claim they have been hit by the problem.

NicDG observes: "I had this consequence on my home PC. Afterward Automatic Repair failed, I rebooted and hit F8 to get the boot options carte du jour and booted into prophylactic mode. Windows started to load, then crashed. Rinse and repeat (once, maybe twice). Windows booted properly into condom style, restarted, finished installing updates, restarted at least in one case and loaded Windows normally."

To throw a little more defoliation into the pot, Microsoft has highlighted the following known issue with the KB4041676 update: "Systems with back up enabled for USB Type-C Connector System Software Interface (UCSI) may experience a blueish screen or stop responding with a black screen when a system shutdown is initiated."

Although user NicDG notes that his PC doesn't have USB Blazon-C on board. At any rate, Microsoft has said information technology's working on a ready for the USB-C event, which will exist provided in a futurity update. The workaround for now is to "disable UCSI in the computer system's BIOS", although that will fully disable UCSI features across Windows, of course.

While there may not be much of an issue hither for the majority of home users, if indeed any, the more cautious out there might desire to give this particular update a little breathing room.

These sort of potential problems, of class, are ane reason why updates being piped directly and automatically to a Windows x PC can be a cause of frustration. Certainly, when information technology comes to the major updates, nosotros're never smashing to exist an early adopter, preferring the strategy of waiting to see what issues ingather upwards (if any) before nosotros take the plunge.

Via: PC Gamer

Windows 10 is the Os installed on many of our best laptops

Darren is a freelancer writing news and features for TechRadar (and occasionally T3) across a broad range of computing topics including CPUs, GPUs, various other hardware, VPNs, antivirus and more. He has written about tech for the best part of three decades, and writes books in his spare time (his debut novel - 'I Know What You lot Did Last Supper' - was published by Hachette UK in 2013).