If you need to update an update repeatedly, something is not going well. Microsoft has released a new version of it KB4340558 on July 19 2018 to resolve an installation error that was displayed with 0x80092004.
The phenomenon is already known from previous updates: Windows 7 Critical update that fixes critical updates
However, this specific error (0x80092004) was encountered by too many system administrators and users when they tried to install the .NET Framework update on systems that were supposed to be compatible.
Microsoft originally released the update at 2018 July Patch Day as a security update for various versions of the Microsoft .NET Framework on Windows 8.1 and Windows Server 2012 R2.
The update solved a number of security issues that attackers could exploit to gain increased privileges, run remote code, or bypass various security features.
Initially, there were many users who reported that the update could not be installed on Windows Server 2012 R2 or Windows 8.1 computers, and Microsoft has confirmed the problem in the known issues of the update.
Users may encounter the "0x80092004" error when trying to install KB4340557 or KB4340558 on Windows 8.1, Windows Server 2012 R2, or Windows Server 2012 after installing KB4291497 or KB4291495 on .NET Framework 4.7.2 .4.7.1, 4.7, 4.62, 4.6.1, 4.6 or XNUMX.
Microsoft published an article on July 13 of 2018 which confirmed the problem and gave it two alternative ways of resolving it. The company suggested downloading updates manually or installing them with the Dism / Online / NoRestart / Cleanup-Image / StartComponentCleanup commands.
Two days later, Microsoft released new updates to fix issues that were previously caused by Windows 7, Windows 8.1, and Server. The company updated the listing of the KB4340558 update in the Microsoft Update Catalog but did not report what it was.
Windows users check the Microsoft Update Catalog website today, they will notice that the last date for the update has changed again. We do not know what to do with this update at this time, but the first reports from users and system administrators seem to indicate that the problem has been resolved.
To see, will the same happen tomorrow?