If you often experience Windows 10 app crashes, make sure to install the latest updates on your computer. Microsoft recently rolled out Windows 10 Creators Update KB4041676 aimed specifically at fixing app crashes, so now is as good a time as ever.

Unfortunately, many users reported that this update also brings issues of its own. Luckily for you, we’re going to list the most common bugs that Creators Update users reported after installing this update.

KB4041676 reported issues

Install freezes

Many users are still struggling to install KB4041676 on their computers. The download and install process sometimes fails with various error codes, including error 0x800705b4 and 0x80070157, or just simply freezes.

Here’s how one user describes the issue on Microsoft’s forum:

Some users complained that their computers keep restarting because Windows Update can’t successfully install KB4041676.

Windows 10 (KB4041676) – Error 0x80070157 stuck in limbo Installation error, stuck in limbo, only one system is affected. After the 100% hardisk activities, and force reboot , now the patch is stuck in a limbo, cant install , it just keep downloading automatically via wucs but failed to installed. Manual download via catalog doesnt install it either. Error 0x80070157 is reported.

Blue Screen of Death

Other Windows 10 users also reported that the restart problem is often accompanied by various BSoD errors. Judging by user reports, it seems that the INACCESSIBLE BOOT DEVICE message is the most frequently encountered error.

The only solution to fix this issue is to perform a system restore. However, this fix doesn’t work for all users but you’ve got nothing to lose if you try it.

Update KB4041676 is plagued by BSoD loops because Microsoft accidentally rolled out the Delta updates to the WSUS channel. In other words, the fact that two updates got pushed to computers at the same time caused this problem. The good news is that the Delta patch expired and BSoD errors should no longer affect users.

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.

Excel hangs

The update also affects Excel, preventing users from editing their documents. More specifically, KB4041676 causes Excel to freeze, gdiaplyet blank areas on the sheets or even a white screen.

Mail won’t sync

Since installing KB4041676 and restarting PC excel stops updating display when 2 instances of Excel are running. I can save the files and sometimes they will close ok but display doesn’t update and Excel windows eventually gets more and more blank areas.

Creators Update users also report that their inbox stopped syncing after they installed the update.

Print to PDF stopped working

My MS365 email address has stopped receiving new emails since the above updates were applied to my x64 system. The personal Outlook email address also accessed via Windows 10 mail still works fine.

Other users reported that the ‘Print to PDF’ feature has stopped working since installing KB4041676. Word fails to save the files or saves 0 KB files. If you’re among them, do check out our extensive guide on how to fix this issue.

These are the most common issues triggered by KB4041676. As always, if you want to avoid update bugs, the best solution is to wait one week and then download the patches.

Windows 10 update KB4041676 installed today. Print to PDF stopped working. Will not save file.

If you encountered other KB4041676 issues, use the comment section below to tell us more about your experience.

If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

Still having issues? Fix them with this tool:

SPONSORED

  • patch tuesday

Email *

Commenting as . Not you?

Comment