This update includes the quality improvements from KB4493467, in addition to new Japanese Era related changes. Key changes include:
- Updates the NLS registry to support the new Japanese Era.
- 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.
- Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format.
- Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character.
- Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras.
- Addresses an issue that causes the abbreviated Japanese Era names to be incorrect.
- Addresses an issue that causes the Clock and Calendar flyout control to ignore user settings for Japanese Era date and time formats.
- Enables the 元年 character for the first year in the Japanese Era.
- Addresses an issue that prevents Microsoft Office Visual Basic for Applications from displaying the correct Japanese Era name.
- Addresses an issue that may overwrite gan-nen support behavior for the Japanese Era after an update.
- Addresses an issue that fails to recognize the first character as the abbreviation for the Japanese Era name.
- Addresses an issue that prevents cross-era navigation in the Japanese Calendar view.
- Addresses an issue related to the date format for the Japanese Era calendar.
- Addresses an issue that causes the GetCalendarInfo function to return a wrong value for the Japanese Era.
- Updates fonts to support the new Japanese Era.
- 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.
- Addresses an issue that prevents date parsers from converting future and past dates (Gregorian and Japanese) in compound documents (formerly OLE) to a relevant Japanese Era date.
For more information on changes for the Japanese Era, see KB4469068.
|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 KB4503276.
|Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.|| |
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.
Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.We are presently investigating this issue with Avira and will provide an update when available.
|Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.||This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.|
|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:
|When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.|| |
This issue is resolved in KB4499151.
How to get this update
There are no prerequisites for installing this update.
Update replacement information
This update does not replace a previously released update.