wrote:
This is the details quoted from the failed install:


===========================================
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 for Windows 8.1 and Server 2012
R2 for x64 (KB4340558)

Installation date: ?7/?12/?2018 9:14 AM

Installation status: Failed

Error details: Code 80092004

Update type: Important

A security issue has been identified in a Microsoft software product
that could affect your system. You can help protect your system by
installing this update from Microsoft. For a complete listing of the
issues that are included in this update, see the associated Microsoft
Knowledge Base article. After you install this update, you may have to
restart your system.

More information:
http://support.microsoft.com/kb/4340558

Help and Support:
http://support.microsoft.com

======================================

When I check the 4340558 page, there is a difference in the
descriptions (i.e. when it should be installed).

As can be seen above, it says it is to be installed for 4.7.2. I have
4.7.2 installed and running fine. So, it needs to be intalled.

When one checks the 4340558 page, there is no 4.7.2 in the description
field (i.e. it is NOT for 4.7.2). The initial update did NOT have this
update checked when the system checked for updates.

But when it the description showed it was for 4.7.2 (and other
vulnerabilities), I checked it to install it. Then the failures began.

https://borncity.com/win/2018/07/11/...or-0x80092004/

"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.
"

"Couldn't find the hash of component: NetFx4-PenIMC"

"While KB4338424 and KB4338415 installs for this user,
KB4338419 creates the install error."

"Currently my recommendation is to hide the update, and
wait until Microsoft releases a revised patch or recommendations
to fix the install issue.
"

Similar information here, with users seeing different results
to the suggested "recipes". One suggest is to uninstall two
previous rollups, and then this rollup will work. Seems
like a lot of work.

https://www.computerworld.com/articl...in-flames.html

HTH,
Paul