Kb4489894 comes with BSOD errors and app launch issues

by Milan Stanojevic
Milan Stanojevic
Milan Stanojevic
Windows & Software Expert
Milan has been enthusiastic about PCs ever since his childhood days, and this led him to take interest in all PC-related technologies. Before joining WindowsReport, he worked as... read more
Affiliate Disclosure
Windows Update bugs

Microsoft releases another batch of cumulative updates for various versions of Windows 10 on the third Tuesday of the month. 

Although the update brings plenty of bug fixes and improvements, still we can’t ignore various bugs it brings along with it. However, users have already reported they encountered some bugs after installing KB4489894.

Kb4489894 known issues

1. Applications not responding

Microsoft acknowledges the fact that the installation of the update triggers a bug in MSXML6. This bug further forces different applications to stop responding in case the node operations insertBefore(), appendChild() and moveNode() throw an exception.

When a user attempts to edit a Group Policy Object (GPO), the Group Policy editor may stop responding. 

Microsoft is currently working to resolve the bug and promises to release a fix in the next release.

2. Application Protocol handlers issue

The users might face starting issues related to IE trusted sites and corresponding application for local intranet.

The main factor behind the bug is Custom URI Schemes for Application Protocol handlers.

Microsoft suggests the users should try the following temporary workaround:

Use the right click to open the URL link in a new tab or window.
You can also Enable Protected Mode in IE for local intranet and trusted sites.

  1. Go toTools>Internet options>Security.
  2. WithinSelect a zone to view or change security settings, selectLocal intranetand then selectEnable Protected Mode.
  3. SelectTrusted sitesand then select Enable Protected Mode.
  4. SelectOK.

The changes will be applied successfully after you restart the browser.

The users will have to wait for the next update to fix the issue.

3. Secure Shell (SSH) client program Start-up failure

The users can also experience a bug that restricts Secure Shell (SSH) client program from starting.

The error is triggered after the installation of the update in the following cases:

  1. The user has a Windows Subsystem for Linux (WSL)  
  2. The agent forwarding has been enabled using a configuration setting or a command line switch (ssh –A)

Microsoft promises to bring a permanent fix to the bug in the upcoming release. Right now you can use a configuration setting or a command line switch (ssh –a) to disable authentication agent connection forwarding.

4. Device start-up issue

The update brings another bug for the users when a Windows Deployment Services (WDS) server’s device that uses Variable Window Extension is started with the Preboot Execution Environment (PXE).

As a result when the user attempts to download an image the WDS server connection might terminate prematurely. However, those devices or clients that are not using Variable Window Extension does not have to tackle the bug.

The tech giant is currently working on the bug and for the time being, it can be resolved by following one of these solutions:

Solution 1
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Solution 2
Use the Windows Deployment Services UI.

Open Windows Deployment Services from Windows Administrative Tools.
Expand Servers and right-click a WDS server.
Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Solution 3:
the following registry value to 0:


Keep in mind that the WDSServer service needs to be restarted following the Variable Window Extension is disabled.

5. Blue screen bug

Microsoft warns the users that they will have to face a system failure and a startup blue screen bug if they enable per font end-user-defined characters (EUDC).

The particular setting needs to be avoided by those users who are currently residing in the non-Asian regions.

The company suggests the users refrain from enabling per font EUDC till a bug fix has been released.

Let us know in the comments section below if you have experienced any issue apart from those mentioned in the article.


This article covers:Topics: