[German]Last night Microsoft released the .NET Framework update KB4340558 for Windows. As it looks, this update is buggy and cannot be installed. The installation ends (on some systems) 0x80092004. Addendum: Microsoft has published workarounds – see addendum below.
.Net Framework update KB4340558
.Net Framework update KB4340558 (Security and Quality Rollup updates for .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 8.1, RT 8.1, and Server 2012 R2) is available for the above framework versions. The security update is intended to fix the following vulnerabilities.
- A “remote code execution” vulnerability exists when .NET Framework does not validate input correctly. An attacker who successfully exploits this vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts that have full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who have administrative user rights. To exploit the vulnerability, an attacker would have to pass specific input to an application through susceptible .NET Framework methods. This security update addresses the vulnerability by correcting how .NET Framework validates input. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8284.
- An “elevation of privilege” vulnerability exists in .NET Framework that could allow an attacker to elevate their user rights level. To exploit the vulnerability, an attacker would first have to access the local computer, and then run a malicious program. This update addresses the vulnerability by correcting how .NET Framework enables COM objects. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8202.
- A “security feature bypass” vulnerability exists when .NET Framework components do not correctly validate certificates. An attacker could present expired certificates when challenged. This security update addresses the vulnerability by making sure that .NET Framework components correctly validate certificates. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8356.
The specified security fixes therefore suggest that you install this security update quickly.
Installation Fails with Error 0x80092004
German blog reader Markus B. contacted me today via e-mail (thanks) and described his observation.
KB4340558 is running on error. 60 PCs cannot install it. Find also already the first forum posts to it. Don’t seem like the only one.
“2018-07 Security and Quality Rollup for.NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 under Windows 8.1 and Server 2012 R2 for x64 (KB4340558)”. It has error code 80092004.”
A 2nd blog reader from Greece reported the same to me via e-mail. Currently ther is only a German forum post, describing the same error. Also downloading the package from Microsoft Update Catalog and install ist manually, ends with the error dialog shown below.
However, Markus B. wrote, that he received an install error code 0x80092004 (not shown above), which should be found in the event logs. Error code 0x80092004 stands for CRYPT_E_NOT_FOUND, ‘The object or property was not found’. This indicates that something was not found within the package. I assume that Microsoft broke something within the package and have to re-release a new version.
Below user Valter left a comment, shedding a bit light into that issue. I mentioned the CRYPT_E_NOT_FOUND meaning for error code 0x80092004. Blog reader Valter found the following entry within his event log:
“Couldn’t find the hash of component: NetFx4-PenIMC”
So it seems that one part of the update is missing a has value, so the update installer refuse the package. PenIMC stands obviously for a pen component (Pen Input Mode Component?).
For curiosity I went to Microsoft Update Catalog and tried to download KB4340558. The goal was to analyze the package.
Microsoft Update Catalog offered me three .msu packes. Blog reader Valter wrote below in a comment, that he wasn’t able to install the .msu files. There is a Russian Technet forum thread, where KB4338424, KB4338415 and KB4338419 are mentioned also. While KB4338424 and KB4338415 installs for this user, KB4338419 creates the install error.
I read also some forum posts (see here at spiceworks), where users are claiming, that the update installs on Windows Server 2012 R2 without a flaw. Due to the fact, that we have a cumulative update, it’s explainable, that not all Windows 8.1 and Windows Server 2012 R2 systems will fail. Some are probably patched, while on others updating NetFx4-PenIMC fails due to the missing hash value.
What helped some users
Addendum: At askwoody.com there is this forum post, where a user wrote, that entering the command below in an administrative command prompt windows helped.
Dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
Just try it and reboot Windows. If it works, it’s fine, but I’m skeptical.
Addendum: At askwoody.com user abbodi86 pointed out: ‘but running DISM is not enough, KB4229727 & KB4096417 must be uninstalled beforehand.
Sum it up and final recommendations
Before I wrote the blog post, I’ve 3 different cases, where this update fails during installation on Windows 8.1 clients or Windows Server 2012 R2. After publishing the German and English article, I received another 8 confirmations of this error so far. There are also posts at Microsoft answers, at askwoody and spicework community.
All approaches as using sfc /scannow and dism, to repair Windows system files and component store, or delete the update store, won’t help. Also an attempt to install the package from a download via the .msu file will fail. Currently my recommendation is to hide the update, and wait until Microsoft releases a revised patch or recommendations to fix the install issue. I’ve escalated the issue within this Microsoft answers forum thread, and I created this Technet forum thread – let’s hope that help. If you are affected, you can leave a comment. If a solution is known, also.
Addendum: Microsoft confirmed the issue
Microsoft has added a ‘known issues’ section to KB4340558 with the following text:
Users receive a “0x80092004” error when they try to install the July 2018 Security and Quality Rollup update KB4340557 or KB4340558 on Windows 8.1, Windows Server 2012 R2, or Windows Server 2012 after they install the June 2018 .NET Framework Preview of Quality Rollup updates KB4291497 or KB4291495 on systems that are running on .NET Framework 4.7.2, 4.7.1, 4.7, 4.62, 4.6.1, or 4.6.
So it may be helpful, to uninstall KB4291497 or KB4291495.
Microsoft published workarounds
On July 13, 2018 Microsoft published the article “0x80092004” error occurs and July 2018 .NET Security and Quality Rollup update KB4340557 or KB4340558 does not install after you apply June update KB4291497 or KB4291495 with workarounds for this issue (thx JR for the comment). But I should note, that I got feedback from some affected users, where Microsoft’s fix doesn’t help.
Microsoft published a revised update
Microsoft released a revised Update on July 19, 2018, see my blog post Revised .NET Framework Update KB4340558 (July 19, 2018). Some users are reporting, that this update will install without error 0x80092004.