If you need to update an update repeatedly, something is seriously wrong. Microsoft released a new version of KB4340558 on July 19, 2018 to resolve an installation error that appeared with code 0x80092004.
The phenomenon is already known from older updates: Windows 7 Critical update that fixes a critical update
But this particular error (0x80092004) was encountered by many system administrators and users when they tried to install the .NET Framework update on systems that were supposed to be compatible.
The history
Microsoft originally released the update on Patch Day in July 2018 as a security update for various versions of the Microsoft .NET Framework on Windows 8.1 and Windows Server 2012 R2.
The update resolved several security issues that could be exploited by attackers to gain elevated privileges, execute remote code, or bypass various security features.
Initially, there were many users who reported that the update was unable to install on computers running Windows Server 2012 R2 or Windows 8.1, and Microsoft confirmed the issue in the update's known issues.
Users may encounter the error “0x80092004” when trying to install the updated version KB4340557 or KB4340558 on Windows 8.1, Windows Server 2012 R2 or Windows Server 2012 after installing the updated version KB4291497 or KB4291495 on systems running .NET Framework 4.7.2, 4.7.1, 4.7, 4.62, 4.6.1 or 4.6.
Microsoft published an article on July 13, 2018 that confirmed the issue and provided two workarounds. The company suggested downloading the updates manually, or installing them with the Dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup command.
Then, two days later, Microsoft released new updates to fix issues that the previous ones caused on systems running Windows 7, Windows 8.1, and Server. The company updated the entry for update KB4340558 in the Microsoft Update Catalog but did not mention what exactly changed.
Windows users who check the Microsoft Update Catalog website todaywill notice that the last date for the update has changed again. We don't know what will happen with this update at this time, but early reports from users and system administrators seem to indicate that the issue has been resolved.
Let's see, will the same be true tomorrow?
Microsoft and Windows 10: speed reduces quality?
