Windows 10 Cumulative Update KB4489894 Can Cause BSODs Due to a Known Bug

[The AchieVer]

Windows 10 Cumulative Update KB4489894 Can Cause BSODs Due to a Known Bug 

 

The most recent cumulative update released by Microsoft for Windows 10 version 1803 (April 2018 Update) can cause a fatal crash due to an issue that has already been acknowledged by the software firm.

 

KB4489894 is a cumulative update published on March 19, and it is specifically aimed at delivering non-security fixes to Windows 10 version 1803 devices.

The update, however, can lead to a Blue Screen of Death due to an issue concerning fonts and end-user-defined characters, or EUDC. Microsoft explains in the official release notes:

“If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen will appear at startup. This is not a common setting in non-Asian regions.”How to avoid a BSODThe workaround, in this case, is as simple as it could be: just don’t enable per font EUDC, Microsoft explains. So basically, if you don’t want this feature to end up causing a BSOD after installing the new cumulative update, you better not using it.

Obviously, this isn’t really the most convenient workaround, but the good news is that Microsoft is already working on a fix. The release, however, is projected to take place in an upcoming patching cycle.

The software giant has confirmed that the same issue exists in the other cumulative updates released on March 19, including in KB4489890 for Windows 10 Fall Creators Update (version 1709).

The next Patch Tuesday will take place on April 9, and it will also include security updates for Windows 10, but at this point, it’s not known if this is the target date for the bugfix.

This cumulative update also comes with a series of other known issues, but most are inherited from the previous updates. The font bug described here, on the other hand, is introduced with KB4489894.

 

 

 

Source

 

[Angelika_3000]

I got the 4489894 update last week and yesterday. At both occasions the blue screen (see above) appeared only after entering username and password and I needed to restore the whole system thereafter. Whatever they have "betterworsed", the second fail and the consecutive restoration crushed my antivirus-software and corrupted another (scan-app).

 

Finally, I decided to skip updates via the delay-option in Windows-Update and hope that a third or forth update will run smoothly. With a net profit of several billion dollars Windows should be able to employ one or two guys who are capable of checking what they're trying to deliver, aren't they? Giving them a clue: This entirely new feature in production lines is called quality management.