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

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

Kb4489894 known issues

1. Applications are not responding

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

When a user tries 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 version.

2. Problem with the application protocol drivers

Users may face initial problems related to the IE Trusted Sites and the corresponding application for the local intranet.

The main factor behind the bug is the custom URI schemes for the application protocol handlers.

Microsoft suggests that users should try the following workaround:

Use the right click to open the URL link in a new tab or window.
on the contrary
, you can also enable the protected mode in IE for local intranet and trusted sites.

  1. Go to Tools > Internet Options > Security .
  2. Within Select a zone to view or change security settings , select Local intranet and then select Enable protected mode.
  3. Please select Trusted sites and then select Enable protected mode .
  4. Choose okay .

The changes will be applied correctly after restarting the browser.

Users will have to wait for the next update to fix the problem.

  • RELATED: What To Do If The Desktop Is Unavailable After Windows 10 Update

3. Secure Shell (SSH) client program startup failed

Users may also experience an error that restricts the launch of the Secure Shell (SSH) client program.

The error is triggered after the update is installed in the following cases:

  1. User has a Windows Subsystem for Linux (WSL)
  2. Agent forwarding has been enabled through a command line switch or configuration (ssh –A)

Microsoft promises to bring a permanent fix to the bug in the next version. At this point you can use a configuration or command line switch (ssh –a) to disable connection forwarding for the authentication agent.

4. Device startup problem

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

As a result, when the user tries to download an image, the WDS server connection may end prematurely. However, devices or clients that do not use the Variable Window Extension do not have to fix the error.

The tech giant is currently working on the bug, and for now, 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 user interface.

Open Windows Deployment Services from Windows Administrative Tools.
Expand Servers and right-click on a WDS server.
Open its properties and uncheck the Enable variable window extension box on the TFTP tab.

Solution 3:
set the following registry value to 0:


Note that the WDSServer service must be restarted after the variable window extension is disabled.

5. Blue screen error

Microsoft is warning users that they will face a system crash and startup blue screen error if they enable end-user-defined characters (EUDC) per font.

Users who currently reside in non-Asian regions should avoid the particular configuration.

The company suggests that users refrain from enabling EUDC by source until a bug fix has been released.

Let us know in the comment section below if you have experienced any issues other than those mentioned in the article.


  • How to restore previous sessions in Microsoft Edge
  • FIX: Microsoft Store stopped working after Windows 10 update
  • windows 10 news
  • windows 10 updates


Leave a Comment

Your email address will not be published. Required fields are marked *

This div height required for enabling the sticky sidebar