KB4487044 fails to install for some and disables Windows Defender

Madalina Dinita
by Madalina Dinita
Managing Editor
0 Comments
Download PDF

KB4487044 bugs

The latest Windows 10 v1809 update is KB4487044. The update doesn’t bring any new features to the table, focusing on fixing some of the technical issues triggered by previous patches.

At the same time, KB4487044 also brings some issues of its own. While these problems are not that frequent, they might affect some users. In this quick post, we’re going to list all the bugs reported by users after installing this update.

Ad

KB4487044 issues

1. KB4487044 install fails

Some users reported that their computers failed to install the update with error 0x80070003. Here’s how one user describes this problem:

Updates (KB4487044) downloaded ok to 2 computers, but during installation, they both got an error message: We couldn’t complete the updates. Undoing changes. Don’t turn your computer off…
Looking at the View update history on both computers: 2019-02 Cumulative Update for Windows 10 version 1809 for X64-based Systems (KB4487044) failed to install on 02/12/2019 – 0x80070003
Thought Microsoft fixed the updates problem.

If you’re experiencing the same error, use the troubleshooting guides listed below to fix it:

2. Windows Defender Offline is no longer working

After installing KB4487044, it disabled Windows Defender leaving it with the Red X, and not possible to scan. This was never an issue prior with any CU installed on Retail 17763. Putting it back online, updating and back working.

If you’re experiencing this problem, try restart Windows Defender. If the problem persists, you can either uninstall the update or install a third-party antivirus software.

As you can see, users reported only two bugs after installing KB4487044. There is also a third issue affecting this patch, but Microsoft already added it to the list of known issues.

3. Japanese date and time issues

Microsoft already acknowledged this problem and explained that after installing this update, previously abbreviated Japanese date and time strings no longer parse. As a workaround, you need to tweak your Registry in the following manner:

  1. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Calendars\Japanese\Eras.
  2. Operate the following changes:
    • “1868 01 01″=”明治_明_Meiji_M”
    • “1912 07 30″=”大正_大_Taisho_T”
    • “1926 12 25″=”昭和_昭_Showa_S”
    • “1989 01 08″=”平成_平_Heisei_H”

A permanent fix for this issue will be available next month.

How has your KB4487044 experience been so far? Let us know in the comments below.

RELATED POSTS TO CHECK OUT:

Ad