{"id":10749,"date":"2019-08-14T21:19:00","date_gmt":"2019-08-14T19:19:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10749"},"modified":"2022-06-26T12:53:56","modified_gmt":"2022-06-26T10:53:56","slug":"windows-updates-kb4512506-kb4512486-drops-error-0x80092004","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/08\/14\/windows-updates-kb4512506-kb4512486-drops-error-0x80092004\/","title":{"rendered":"Windows Updates KB4512506\/KB4512486 drops error 0x80092004"},"content":{"rendered":"

\"Windows[German<\/a>]A brief information for users who install the August 2019 security updates KB4512506 or KB4512486 for Windows 7 SP1 and Windows Server 2008 R2 in an installation error 0x80092004. It is highly likely that updates to retrofit SHA-2 support will then be missing.<\/p>\n

<\/p>\n

Users report error 0x80092004<\/h2>\n

\"\"It didn't take long after the release of the security updates KB4512506 (Monthly Rollup) or KB4512486 (Security Only) for Windows 7 SP1 and Windows Server 2008 R2 until the first users reported issues within my German blog. German blog reader Heidemann wrote in this comment<\/a>:<\/p>\n

The attempt to install the update to W2K8R2 fails here with Installation Failure: Windows failed to install the following update with error 0x80092004: Security Update for Windows (KB4512486).<\/p>\n

No Symantec or Norton (but McAfee) on the systems.<\/p><\/blockquote>\n

And a short time later M. Gruber posted this comment<\/a> with the same tenor, but to another German blog post.<\/p>\n

I repeatedly fail to install KB4512506 (Monthly Security Quality Rollup) with code 80092004 under a naked Win7 x64 without AV software.
\nAm I the only one or is there a workaround?<\/p><\/blockquote>\n

The user then pointed out similar feedback from users in the English DSL forum<\/a>.<\/p>\n

I can't install KB4512506 on two different Windows 7 64 bit systems. Each one fails with the error code: 80092004. Multiple restarts and retries result in same error. Anyone else seeing this?<\/p><\/blockquote>\n

I found also a japanese post<\/a> mentions this error code without giving further hints.<\/p>\n

The error has already occurred with .NET<\/h2>\n

I mentioned the error code 0x80092004 in some blog posts (see links at the end of the article) and Microsoft also published a KB article<\/a> about the error. However, this KB article refers to a bug in the .NET framework that prevents updates from being installed. However, I don't consider this to be a valid cause, as these are currently Windows updates.<\/p>\n

What does error code 0x80092004 stands for?<\/h2>\n

Before you start any wild experiments, it's good to know what the cause of the error is. The error code 0x80092004 stands for CRYPT_E_NOT_FOUND. Windows Update could not find any cryptographic value and rejects the update.<\/p>\n

There was something SHA-2 signing?<\/h2>\n

I had it mentioned in the blog post Symantec\/Norton blocks Windows Updates (SHA-2)<\/a>. Microsoft changed the signing of update packages for Windows 7 SP1 and Windows Server 2008\/R2 for the first time in August 2019. Instead of signing the packages with both SHA-1 and SHA-2, only a SHA-2 hash value is stored in the package. The above error code indicates that Windows Update is looking for the SHA-1 signature in the package and does not find it.<\/p>\n

What should be checked<\/h2>\n

One possibility is that an external virus scanner recognizes and modifies the update packets incorrectly. The blog post Symantec\/Norton blocks Windows Updates (SHA-2)<\/a> mentions that Symantec and Norton security solutions cause trouble. In this scenario, however, Microsoft blocks the delivery of security updates.<\/p>\n

Weighting the above information, there is a lot of evidence that the support for the new updates and Windows signed exclusively by SHA-2 is simply missing. As of March 12, 2019, Microsoft had extended support article 4472027<\/a> (2019 SHA-2 Code Signing Support requirement for Windows and WSUS) to include the SHA-2 updates required for Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, and Windows Server 2008 Service Pack 2.<\/p>\n