How to fix BSOD problems after installing KB4041676 on Windows 10


Microsoft recently released update KB4041676 for Windows 10 running the Creators Update to address a number of issues. However, hours after the rollout, many users began to make their voice heard as the October 2017 update is causing BSoD (Blue Screen of Death) on a number of computers.

Some users at the Microsoft forums noted a message that read: “INACCESSIBLE BOOT DEVICE,” and after that, the reboots automatically, attempts to boot again, and then it boots into the “Automatic Repair” screen.

There are also complaints from other users in Reddit noting 100 percent of disk usage installing the update, and stuck applying the update.

If the you haven’t install the update yet, you can go to Settings > Internet & Security > Windows Update, and use the Restart options to postpone the installation as long as you can.

According to a report from Neowin, this appear to only affecting users using WSUS.

How to fix problems with update KB4041676

If you need to recover your device, you can use this workaround that appeared in Reddit.

Using the advanced repair options on Windows 10, open Command Prompt and use this commands:

Dism /Image:C:\ /Get-Packages (could be any drive, had it on D, F, and E.)
Dism /Image:C:\ /Remove-Package /PackageName:package_ for_###

Important: do there is no space between package_ and for

How to remove any pending update

There are 3 updates that are causing the issue they are:

Rollupfix~31bf3856ad364e35~amd64~14393.1715. 1.10


Apparently this problem no only happens with update KB4041676, but also with update KB4041691 for version 1607.

Also, according to a new report from ZDNet, it seems that it’s not an issue with the updates themselves, but a mistake that Microsoft made publishing the updates to Windows Server Update Services (WSUS) and System Center Configuration Manager both Cumulative and Delta updates that could be installed on PCs at the same time caused the hiccup.

Microsoft doesn’t make Delta updates to Microsoft Update, as such this issue shouldn’t affect regular users, as they don’t use WSUS and Configuration Manager.


Microsoft has officially responded to this issue and says that problem has been corrected.

For more details, check this Microsoft Support announcement.