| Windows Server 2008 SP2 May 14, 2019 Stand Alone security update released to introduce SHA-2 code sign support | 0 SP2, must be manually installed by this date to support SHA-2 updates |
|---|---|
| SHA-2 update released September 10, 2019 | Boot into Windows prior to installing any August 13, 2019 or later updates |
1 Windows Server 2012 R2 September 10, 2019 Stand Alone security update was re-released to add missing EFI boot mangers.
19| Any devices without SHA-2 support will not be able to install Windows updates on or after July 2019 | The required updates can be installed in any order and do not need to be reinstalled, unless there is a new version of the required update |
|---|---|
| This copies the boot files from the Windows directory and sets up the boot environment | For more information, see the Windows IT pro blog |
Identify devices and VMs in restart pending state with updates released August 13, 2019 or later and open an elevated command prompt• For those customers using WSUS 3.
| 1 Windows Server 2019, all editions Windows Server Update Services 3 | Unfortunately, the security of the SHA-1 hash algorithm has become less secure over time because of the weaknesses found in the algorithm, increased processor performance, and the advent of cloud computing |
|---|---|
| If you encounter this issue, you can mitigate this issue by opening a command prompt window and run the following command to install the update replace the placeholder with the actual location and file name of the update : wusa | Install the image on the disk and boot into Windows |
You will now need to install the required updates listed in the How to get this update section of the update you are trying to install, or the required updates listed above in the Current status section of this article.
26