SHA-2 Support for Windows Server Update Services 3.0 SP2

Applies to: Windows Server Update Services 3.0 Service Pack 2


To align with industry standards, Microsoft is moving away from using SHA-1 signatures for future updates and moving to SHA-2 signatures (see KB4472027 for more details). Without applying this SHA-2 update, beginning July 2019, WSUS 3.0 SP2 (also called WSUS 3.2) will not be able to perform the necessary WSUS update tasks. Starting with WSUS 4.0 on Windows Server 2012, WSUS already supports SHA-2-signed updates, and no customer action is needed for these versions. This update is necessary for those customers still using WSUS 3.0 SP2. We recommend upgrading to the latest version of WSUS, version 10.0.



  • Windows Monthly Rollup released March 12, 2019 or later, such as
    • KB4489880 or higher rollup for Windows Server 2008 SP2 installed.

    • KB4489878 or higher rollup for Windows Server 2008 R2 SP1 installed.

  • .Net 3.5


Synchronizing WSUS hierarchy after successful patch installation

We recommend that you synchronize all WSUS servers in your environment after applying this update. If you have a hierarchy of WSUS servers, apply this update and synchronize your servers from the top of the hierarchy.  

To synchronize your servers in this manner, follow the steps below   

  1. Apply update to the WSUS server that synchronizes with Microsoft Update. 

  1. Start the synchronization.

  1. Wait for the synchronization to succeed.

Repeat these steps for each WSUS server that synchronizes to the server that you just updated. 

Known issues

  • If you have not installed the applicable Windows operating system prerequisite (KB4489880 or KB4489878), you may encounter an error message if you test the local publishing feature. In the WSUS log, search and locate the following error message: 

“PublishPackage(): Operation Failed with Error: Failed to sign package; error was: 2147942527”

  • This update does not support uninstallation via MSI. Microsoft recommends that validations be performed in a non-production environment. 
  • Remote Microsoft SQL Server administrators must download and install the update by using an account that has SQL Server Administrator permissions. WSUS3.0 SP2 installations using a remote SQL Server will always require manual installation of this update.

How to obtain the update

Method 1: Windows Update

This update will be downloaded and installed automatically.

Note: This update is also available through Windows Server Update Services (WSUS).

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.


Learn about the terminology that Microsoft uses to describe software updates.