New update shipped to Windows 10 version 1809

Jun 27, 2019 06:35 GMT  ·  By

The latest batch of cumulative updates for Windows 10 includes a new release for Windows 10 October 2018 Update, or version 1809, as well.

In fact, the October update is the newest Windows 10 feature update that receives a cumulative update as part of this rollout, as the patch aimed at Windows 10 version 1903 (May 2019 Update) is still being tested in the Release Preview ring.

Windows 10 cumulative update KB4509479 for version 1809 increases the OS build number to 17763.593, so you can determine if the update installed correctly by typing winver in the Start menu and then checking the OS version.

This update comes with a single fix for a bug that broke down some features of the Event Viewer after installing a previous cumulative update. Microsoft explains the following in the release notes:

“Addresses an issue that may prevent devices from connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing KB4497934. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”

KB4497934 is a cumulative update that was published by Microsoft on May 21 and increased the OS build number to 17763.529.

Three known issues in KB4509479

There are three known issues in the update, all of them acknowledged by the software in the previous releases.

First of all, certain operations on files or folders located on a Cluster Shared Volume could fail with error STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). A fix is already in the works, but no ETA is available.

Then, some Asian language packages might no longer work and users could see error 0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND. Again, Microsoft says it’s working on a fix already, and it will be included in an upcoming release.

And last but not least, some devices might end up stuck on a black screen on the first boot after installing the update. The workaround is to initiate a force reboot.