April 9, 2019—KB4493472 (Monthly Rollup)
Applies To
Windows 7 Service Pack 1 Windows Server 2008 R2 Service Pack 1Release Date:
09/04/2019
Version:
Monthly Rollup
Starting with KB 4493472 Monthly Rollup updates will no longer include PciClearStaleCache.exe. This installation utility addressees inconsistencies in the internal PCI cache. This can cause the symptoms listed below when installing monthly updates that do NOT include PciClearStaleCache:
These symptoms are especially common on guest virtual machines and on machines which have not been updated since March, 2018.
Administrators should ensure that any one or more of the Monthly rollups released between April 10, 2018 (KB 4093118) and March 12, 2019 (KB 4489878) have been installed prior to installing April 2019 and later updates. Each of these rollup updates includes PciClearStaleCache.exe.
-
Existing NIC definitions in control panel networks may be replaced with a new Ethernet Network Interface Card (NIC) but with default settings. Any custom settings on the previously NIC persist in the registry but were unused.
-
Static IP address settings were lost on network interfaces.
-
Wi-Fi profile settings were not displayed in the network flyout.
-
WIFI network adapters were disabled
Improvements and fixes
This security update includes improvements and fixes that were a part of update KB4489892 (released, March 19, 2019) and addresses the following issues:
-
Provides protections against Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754) for VIA-based computers. These protections are enabled by default for the Windows Client, but disabled by default for Windows Server. For Windows Client (IT Pro) guidance, follow the instructions in KB4073119. For Windows Server guidance, follow the instructions in KB4072698. Use these guidance documents to enable or disable these mitigations for VIA-based computers.
-
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 prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
-
Addresses an issue that may cause authentication issues for Internet Explorer 11 and other applications that use WININET.DLL. 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.
-
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 Kernel, Windows Server, Graphics Component, Windows Input and Composition, Windows Datacenter Networking, 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
Symptom |
Workaround |
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. |
This issue is resolved in KB4499164. |
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. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article. |
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. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
|
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. |
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update. |
This issue has been resolved. McAfee has released an automatic update to address this issue. Guidance for McAfee customers can be found in the following McAfee support articles: |
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.
If you are using Windows Update, the latest SSU (KB4490628) will be offered to you automatically. To get the standalone package for the latest SSU, go to the Microsoft Update Catalog.
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.
File information
For a list of the files that are provided in this update, download the file information for update 4493472.