Microsoft has released a new build of Windows 10 for users on the October 2018 Update, as well for those running Windows Server 2019. While the delivery schedule is a bit off, it is worth noting that the Windows 10 October 2018 Update did not get a cumulative update alongside other versions of Windows for the second half of April. Microsoft typically releases two rounds of cumulative updates per month, but version 1809 was seemingly left out last week.
Nonetheless, it's better to be late than not release an update at all, and users on Windows 10 version 1809, as well as Windows Server 2019, can now get KB4501835, which is build number 17763.439, and includes many of the same fixes as the updates released last week. Some of these revolve around adding support for the new Japanese era. Here's the full list:
- Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
- Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
- Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
- Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
- Updates fonts to support the new Japanese Era. For more information, see KB4469068.
- Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
- Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
- Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
- Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
- Addresses an issue in Unified Write Filter (UWF) that prevents Hibernate Once/Resume Many (HORM) from working as expected on Unified Extensible Firmware Interface (UEFI) systems.
This release still comes with a fairly long list of known issues, though. Here's what you should be aware of before grabbing the update:
|After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.||
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Microsoft is working on a resolution and will provide an update in an upcoming release.
|Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.||
Do one of the following:
|Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.||
Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
|Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update.||Microsoft is working on a resolution and will provide an update in an upcoming release.|
|After installing this update, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.||
Right-click the URL link to open it in a new window or tab.
Enable Protected Mode in Internet Explorer for local intranet and trusted sites.
You must restart the browser after making these changes.Microsoft is working on a resolution and will provide an update in an upcoming release.
This update actually isn't available through Windows Update, for some reason, even if you choose to manually check for updates. It's available through WSUS, and Microsoft says it should be available on the Microsoft Update Catalog for manual download, but it doesn't seem to be listed there just yet. We'll update this post as soon as it becomes available.