Improvements and fixes
This security update includes improvements and fixes that were a part of update KB4487022 (released February 19, 2019) and addresses the following issues:
- Addresses an issue in which the abbreviated Japanese Era name did not refer to the typographic ligature.
- Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
- Security updates to Internet Explorer, Windows App Platform and Frameworks, Windows Server, Windows Hyper-V, Windows Storage and Filesystems, Windows Fundamentals, Windows Kernel, Windows MSXML, and the Microsoft JET Database Engine.
For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.
Known issues in this update
|After installing this update, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.|| |
This issue is resolved in KB4493471.
|After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.|| |
To mitigate this issue, use one of the following options:
Option 1: Purge the Kerberos tickets on the application server. After the Kerberos ticket expires, the issue will occur again, and you must purge the tickets again.
Option 2: If purging does not mitigate the issue, restart the application; for example, restart the Internet Information Services (IIS) app pool associated with the SQL server.
Option 3: Use constrained delegation.Microsoft is working on a resolution and will provide an update in an upcoming release.
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.
|This issue is resolved in KB4493471.|