KB4501835
詳細情報
KB番号 | KB4501835 |
---|---|
リリース日 | 2019/05/01 |
Windowsバージョン | Windows 10 1809 |
ビルド番号 | 17763.439 |
URL(英語) | https://support.microsoft.com/en-us/help/4501835 |
URL(日本語) | https://support.microsoft.com/ja-jp/help/4501835 |
ダウンロード | Microsoft Update Catalog |
ハイライト
改良点
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.
既知の不具合
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. | This issue is resolved in KB4503327. |
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 is working on a resolution and will provide an update in an upcoming release. |
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. | This issue has been resolved. Arcabit has confirmed this issue is not applicable to Window 10, version 1809. |
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. | This issue is resolved in KB4495667. |
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e." | This issue is resolved in KB4501371. |
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND." | This issue is addressed by updates released June 11, 2019 and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) before installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows:
Note Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it. Workaround:
Note If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server. |