Improvements and fixes
This security update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
- Addresses an issue that causes the abbreviated Japanese Era names to be incorrect. For more information, see KB4469068.
- Addresses an issue that causes the clock and calendar flyout to ignore user settings for Japanese Era date and time formats. For more information, see KB4469068.
- Enables the 元年 character for the first year in the Japanese Era. For more information, see KB4469068.
- Addresses an issue that prevents Microsoft Office Visual Basic for Applications from displaying the correct Japanese Era name. For more information, see KB4469068.
- Addresses an issue that may overwrite gan-nen support behavior for the Japanese Era after an update. For more information, see KB4469068.
- Addresses an issue that fails to recognize the first character as the abbreviation for the Japanese Era name. For more information, see KB4469068.
- Addresses an issue that may cause users to receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.
- Addresses an issue with a virtual memory leak and the depletion of the paged pool with the CMNB tag that cause the server to become unresponsive.
- Addresses an issue with stop error D1 in TCPIP.SYS.
- Security updates to Windows App Platform and Frameworks, Windows Hyper-V, Windows Storage and Filesystems, Windows Fundamentals, Windows Kernel, Windows Server, 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, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
This issue is resolved in KB4493467.
After installing this update, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
|This issue is resolved in KB4493467.|
|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:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
Restart the WDSServer service after disabling the Variable Window Extension.
Microsoft is working on a resolution and will provide an update in an upcoming release.
|After installing this update, devices with a winsock kernel client may receive D1, FC, and other errors. Additionally, systems that run the Skype for Business or Lync Server Edge Transport role may be affected by this issue.||This issue is resolved in KB4489893.|
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 KB4493467.|
|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: