Windows Server 2008 R2 2019年8月安全更新需要注意的重大BUG问题（红字部分）
August 13, 2019—KB4512486 (Security-only update)
Applies to: Windows 7 Service Pack 1Windows Server 2008 R2 Service Pack 1
Release Date:
August 13, 2019
Version:
Security-only update
IMPORTANT Verify that you have installed the recommended updates listed in the How to get this update section before installing this update. For all updates starting with August 13, 2019, we strongly recommend that you install these updates to prevent any issues.
Improvements and fixes
This security update includes quality improvements. Key changes include:
- Security updates to Windows App Platform and Frameworks, Windows Wireless Networking, Windows Storage and Filesystems, Windows Virtualization, Windows Datacenter Networking, the Microsoft JET Database Engine, Windows Input and Composition, Windows MSXML, and Windows Server.
For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.
Known issues in this update
| Symptom | Workaround |
| Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed" after installing this update on a WDS server. | This issue is resolved in KB4512514. |
| IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error: "File: \Windows\system32\winload.efi Status: 0xc0000428 Info: Windows cannot verify the digital signature for this file." |
To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428. |
| Symantec identified the potential for a negative interaction that may occur after Windows Updates code signed with SHA-2 only certificates are installed on devices with Symantec or Norton antivirus programs installed. The software may not correctly identify files included in the update as code signed by Microsoft, putting the device at risk for a delayed or incomplete update. | The safeguard hold has been removed. Symantec has completed its evaluation of the impact of this update and future updates to Windows 7 and Windows 2008 R2. Symantec has determined that there is no increased risk of a false positive detection for all in-field versions of Symantec Endpoint Protection and Norton antivirus programs. See the Symantec support article for additional details and please reach out to Symantec or Norton support if you encounter any issues. |
| After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an "invalid procedure call error." | This issue is resolved in KB4517297, which is an optional update. It is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS). |
How to get this update
Before installing this update
Microsoft strongly recommends that you install the updates listed below and restart your device before installing the latest Rollup. Installing these updates improves the reliability of the update process and mitigates potential issues while installing the Rollup.
- The latest servicing stack update (SSU) (KB4490628). If you are using Windows Update, the latest SSU will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.
- The latest SHA-2 update (KB4474419) released August 13, 2019. If you are using Windows Update, the latest SHA-2 update will be offered to you automatically. For more information on SHA-2 updates, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
- If you are using EFI Boot on your device or virtual machine (VM), you must also install KB3133977. Currently, KB3133977 is required as a workaround for a known issue when using EFI Boot and should be applied even if you are not using BitLocker. For more information on this update, see the frequently asked questions in 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
Install this update
| Release Channel | Available | Next Step |
| Windows Update and Microsoft Update | No | See the other options below. |
| Microsoft Update Catalog | Yes | To get the standalone package for this update, go to the Microsoft Update Catalog. |
| Windows Server Update Services (WSUS) | Yes | This update will automatically synchronize with WSUS if you configure Products and Classifications as follows: Product: Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1 Classification: Security Updates |
File information
For a list of the files that are provided in this update, download the file information for update 4512486.
Last Updated: Aug 29, 2019