Customers who have applied KB 4489887 or later Monthly Rollup Packages to Microsoft Server 2008 SP2 may notice a change to the operating system version string. The “build number” component of the version string increases by 1, and the revision number decreases by approximately 4000 numbers. To find out more about this change please refer to the following article.
Improvements and fixes
This security update includes improvements and fixes that were a part of update KB4489887 (released March 19, 2019) and addresses the following issues:
- Addresses an issue that causes the error "0x3B_c0000005_win32k!vSetPointer" when the kernel mode driver, win32k.sys, accesses an invalid memory location.
- Addresses an issue in which netdom.exe fails to run, and the error, “The command failed to complete successfully” appears.
Addresses an issue that may cause compound document (OLE) server applications to display embedded objects incorrectly if you use the PatBlt API to place embedded objects into the Windows Metafile (WMF).
- Security updates to Windows Storage and Filesystems, Windows Server, Microsoft Graphics Component, Windows Input and Composition, Windows Datacenter Networking, 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, 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.
|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.|| |
Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.
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.
Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.We are presently investigating this issue with Avira and will provide an update when available.
How to get this update
Before installing this update
Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest Rollup. SSUs improve the reliability of the update process to mitigate potential issues while installing the Rollup and applying Microsoft security fixes.
Install this update
This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.
For a list of the files that are provided in this update, download the file information for update 4493471.