{"id":8959,"date":"2019-03-19T00:09:00","date_gmt":"2019-03-18T23:09:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8959"},"modified":"2022-03-18T06:02:55","modified_gmt":"2022-03-18T05:02:55","slug":"windows-7-updates-for-sha-2-support","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/03\/19\/windows-7-updates-for-sha-2-support\/","title":{"rendered":"Windows 7: Updates for SHA-2 support"},"content":{"rendered":"

\"win7\"[German<\/a>]On March 12, 2019, Microsoft released updates for SHA-2 support for Windows 7 SP1 and Windows Server 2008\/R2 as well as WSUS 3.0 SP2. Here is some information about this topic and some hints about first issues.<\/p>\n

<\/p>\n

\"\"The blog post is an attempt to pick up some loose ends and bring them together to an article describing the odds and evens. You can add missing information to the comments..<\/p>\n

What is SHA-2 support about?<\/h2>\n

Microsoft had announced in 2018 that it would only add SHA-2 signatures to its Windows updates from mid-2019 onwards – signing with SHA-1 would then no longer be necessary for security reasons. I've had published the article Windows 7: From April 2019 'SHA-2-Support' is <\/a>about that.<\/p>\n

Users of Windows 7 SP1 (as well as its server counterparts) and WSUS will therefore need a special update from April 2019, which will enable the machine for SHA-2 code signatures. Without this update, these machines will not be able to process new updates in the future. In the blog post SHA-2 patch for Windows 7 arrives on March 2019<\/a> I had announced an update for this month, but I had to leave some details to it. As of March 12, 2019, Microsoft has provided the required updates as part of the patchday.<\/p>\n

Updates KB4474419 and KB4490628<\/h2>\n

Effective March 12, 2019, Microsoft has extended the support article 4472027<\/a> titled 2019 SHA-2 Code Signing Support requirement for Windows and WSUS<\/em> with the details and named the required updates.<\/p>\n

Security Update KB4474419<\/h3>\n

Update KB4474419<\/a> (SHA-2 code signing support update for Windows Server 2008 R2 and Windows 7: March 12, 2019) adds support for SHA-2 signature evaluation for Windows 7 SP1 and its server pendants. The update is automatically downloaded and installed via Windows Update. The update is also available via Windows Server Update Services (WSUS) or for manual download via Microsoft Update Catalog<\/a>. The update is also linked to the Microsoft Update Catalog on the ADV90009<\/a> advisory page.<\/p>\n

Servicing Stack Update KB4490628<\/h3>\n

In addition, the Servicing Stack Update (SSUs) KB4490628<\/a> was released for Windows 7 SP1 and Windows Server 2008 R2 SP1. This update fixes a problem with the Servicing Stack when installing updates that were signed using only the SHA-2 hash algorithm. I already pointed this out in the blog post Patchday: Updates for Windows 7\/8.1\/Server (March 12, 2019)<\/a>.<\/p>\n

More issues with these updates<\/h2>\n

When installing the updates mentioned above to support SHA-2 only update packages, various errors and issues may occur. Microsoft states that the SSU need to be installed before installing the March 2019 updates to avoid subsequent errors and installation problems. But that seems not true \u2013 because on my systems this update had been offered only after installing Update KB4474419 first.<\/p>\n

Update KB4490628 hangs on reboot<\/h3>\n

Update KB4490628 comes with a known issue during its installation, which Microsoft lists here<\/a>. After you have installed the SSU together with other updates, a restart may be required to complete the installation.<\/p>\n

(Update hangs, Source: Microsoft)<\/p>\n

During this reboot, the system may hang when the message \"Level 2 of 2\" or \"Level 3 of 3\" appears. If this problem occurs, press Ctrl+Alt+Del to log on to Windows. This problem should occur only once.<\/p>\n

Update KB4490628 is not offered<\/h3>\n

In KB article 4490628<\/a>, Microsoft states that this update is offered automatically by Windows Update. In this comment<\/a> blog reader Joe_Gerhard points out that the update is not offered to him. I checked it on my machine – this update was missing there as well, while update KB4474419 has been offered. Later I learned (see my remark above), that update KB4474419 is required, before update is KB4490628 offered. If required, the Microsoft Update Catalog<\/a> is also available for download.<\/p>\n

German blog reader Markus B. informed me a few days ago via e-mail about an observation:<\/p>\n

I was able to install the Win7 cumulative first via the WSUS. Then I installed the SSU. MS it says in its support article, that there would be some issues, but that seems not be true. Installing SSU after the cumulative update, does not need a restart.<\/p>\n

In an other installation order with SSU first and then the cumulative for SHA-2 support, it would take much longer to distribute the patches. Because I would need to wait, until the maintenance windows has bee shown \u2013 in cause, Windows need some administrator prompts.<\/p><\/blockquote>\n

Thank to Markus for his feedback. There is now a huge discussion thread beneath my German blog post<\/a> about issues.<\/p>\n

Restart loop in 32-bit Windows 7<\/h3>\n

Within this comment<\/a> (German) blog reader Gregor (thanks) writes, that the SHA-2 support update led to a reboot loop on three 32-bit Windows 7 machines. Gregor does not specify which update KB4474419 or KB4490628 is meant. Has anyone ever had similar experiences?<\/p>\n

Update KB4484071 for WSUS 3.0 SP2<\/h2>\n

In addition, Microsoft has provided the standalone update KB4484071<\/a> for WSUS 3.0 SP2 (SHA-2 Support for Windows Server Update Services 3.0 SP2) in this support article<\/a>. This update enabled WSUS 3.0 SP2 for SHA-2 support.<\/p>\n

Administrators using WSUS 3.0 SP2 need to install this update manually until June 18, 2019. This ensures that updates for Windows 7 and Windows Server 2008\/R2 can be redistributed via WSUS 3.0 SP2 from that point. However, the prerequisite for manually installing update KB4484071 is that the following updates:<\/p>\n