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. Symantec has completed its evaluation of the impact of this update and future updates to Windows 7 and Windows 2008 R2.

The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start. Microsoft and Symantec have identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428. Info: Windows cannot verify the digital signature for this file.' IA64 devices (in any configuration) and 圆4 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: Scripts or apps that use Visual Basic Scripting Edition (VBScript).ĭevices 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. Macros that use Visual Basic for Applications (VBA). This non-security update for Windows 7 SP1 and Windows Server 2008 R2 SP1 includes the quality improvements from KB4512486 (released August 16, 2019), in addition to these key changes:Īddresses an issue in which the following may stop responding and you may receive the error, 'Invalid procedure call”:Īpplications that were made using Visual Basic 6 (VB6).

Winload.efi digital signature