KB4523205 updates Windows 10 1809 to Build 17763.864 – 12 Nov 2019

November Patch Tuesday is here and Microsoft unveiled the cumulative update KB4523205 for Windows 10 version 1809. This update will fly the build to 17763.864 and address several issues of the operating system including certain key changes as well. In this patch, the company basically improve the overall functioning and security of the system while using Internet Explorer, Edge, some external and internal devices.

Users are able to download KB4523205 as an MSU file format from the Microsoft update catalog site. To keep receiving the updates, you need to upgrade the latest version by visiting “Settings > Update & Security > Windows Update > Check for updates“. Furthermore, you can also check the Cumulative Update Complete patches on Windows 10 Cumulative Updates List. Read on to know about the further update, known issues and ways to download it.


General Improvements and fixes – Windows 10 1809

This patch having Build 17763.864 is actually a bug-fixing update that carries no new feature to the OS. Here are the key changes –

  • Windows 10 maker works upon an issue that might cause the Microsoft Defender Advanced Threat Protection (ATP) service to prevent running and hinder sending reporting data.
  • The Build 17763.864 carries new attributes that protect your PC against the Intel® Processor Machine Check Error vulnerability (CVE-2018-12207). Apart from this, you may use the registry settings as illustrated in the Guidance KB article.
  • Furthermore, KB4523205 shields your Windows 10 device from the Intel® Transactional Synchronization Extensions (Intel® TSX) Transaction Asynchronous Abort vulnerability (CVE-2019-11135) as well. Accordingly, to get detailed information, you may click on Windows Client or Windows Server posts. 
  • With build 17763.864, the company provides the security updates “Microsoft Scripting Engine, Internet Explorer, Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Microsoft Edge, Windows Fundamentals, Windows Cryptography, Windows Virtualization, Windows Linux, Windows Kernel, Windows Datacenter Networking, Windows Peripherals, and the Microsoft JET Database Engine”.

Known Issues on KB4523205


Symptoms Workaround

With Build 17763.864, you may receive an error when performing certain operations, for example, rename, on files or folders.

This happens periodically while using Cluster Shared Volume (CSV). Thereafter, you will see the error message that prompts while performing is-STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

This issue basically arises because the operation does not have an administrator authorization. Along with this, the operation operates on the CVS owner node.

Follow anyone –

  • Perform the operation using a process that holds admin authorities.
  • Use a node that does not have CSV ownership and then perform the task.

In the upcoming release, the experts promise to release a solution as they are currently working upon this.

Inside patch KB4523205, when you install KB4493509, devices with some Asian language packs installed may experience an error.

Here the error is – “0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND.”

  1. First of all, uninstall and reinstall any newly added language packs.
  2. Therefore, click on Check for Updates and install the April 2019 Cumulative Update.

Important – If the problem doesn’t reduce even on reinstalling the language pack, reset your device as follows –

  1. Go to the Settings (Win+I) app > Recovery.
  2. Choose Get Started option, available under the Reset this PC recovery option.
  3. Select Keep my Files.

In the upcoming release, the experts promise to release a solution as they are currently working upon this.

As per the appeared report in build 17763.864, when setting up a new Windows device during the Out of Box Experience, you might not be able to create a local user. It happens when you use the Input Method Editor (IME). There’s is the high chance to get affected by this issue if you are using the IME for Chinese, Japanese, or Korean languages.

Important Note – During OOBE, you will not experience any issue using a Microsoft Account during OOBE.

As a primary step to rectify this issue, set the keyboard language to English during user creation. Alternatively, you can also use a Microsoft Account to complete OOBE. This will surely mitigate the issue. Furthermore, you can set the keyboard language back to your preferred language after user creation. Once the OOBE is done and you are at the desktop region, you are able to rename the current user using these instructions. Check out KB4026923, If you prefer to create a new local user.

Microsoft experts are currently working on a resolution and will provide an update in a future release.

How to get patch update KB4523205 

Before proceeding to download and apply this cumulative update on to your PC, make sure to run the latest SSU i.e. KB4523204Below, we illustrate three different ways to get KB4523205 for Windows 10 version 1809.

Windows Update and Microsoft Update

This release will get downloaded automatically through the Windows Update section. If not, you may do the same manually visiting the below address –

Open Settings using Win+I > Update & Security > Windows Update > Check for Updates

Microsoft Update Catalog Get the standalone package
Windows Server Update Services (WSUS)

The KB4523205 patch will auto-synchronize using the WSUS if you have already arranged the following-

  • Product: Windows 10
  • Classification: Security Updates

Source File

One comment

  1. I have an Access db that is split into a front end db (with the queries, forms etc) that links to a db with the tables.

    Has worked fine for close to 20 years (was developed in Access 2000).

    The day after this 17763.846 was installed, the update queries in the accesss db ceased to function, returning the message that the query is corrupt. The table data appears to be fine. The queries look ok in design view. Just can’t be run. Tried compact and repair, tried re-linking tables, neither worked.

    Should we just go back to using the previous build or is there a not too complicated work-around?


Comments are closed.