Microsoft .NET Framework update KB4340558 updated

If you need to update an update, especially if you do so multiple times, something went wrong terribly in my opinion. Microsoft released a new version of KB4340558 on July 19 2018 which appears to resolve the 0x80092004 installation error issue that many administrators and users experienced when they tried to install the .NET Framework update on compatible machines.

Microsoft released the update on the July 2018 Patch Day initially as a security and quality rollup update for various versions of the Microsoft .NET Framework for Windows 8.1 and Windows Server 2012 R2.

It resolved several security issues that attackers could exploit to elevate privileges, execute code remotely, or bypass security features.

Users started to report that the update could not be installed on PCs running Windows Server 2012 R2 or Windows 8.1, and Microsoft confirmed the installation issue in the known issues section of the support post.

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.

Microsoft published an article on July 13, 2018 that confirmed the issue with two workarounds to resolve the issue. The company suggested that users would either download two updates manually to install them or run the command Dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup to fix the issue.

Img

Microsoft released updates two days ago to fix issues caused by the July 2018 updates for Windows 7, Windows 8.1, and Server products. The company did update KB4340558's listing on the Microsoft Update Catalog website but it was not clear what changed as Microsoft did not reveal that.

Windows users and admins who check the Microsoft Update Catalog website today will notice that the last update date for the update has changed again. While there is no official confirmation that the update did indeed fix the issue caused by the initial version, firsts reports by users and administrators are positive as the issue appears to have been fixed.

Note that the package includes three files that need to be installed one after the other on compatible systems.

Microsoft did remove the known issue from the update description which is a strong indicator that the company believes that it has fixed the issue for all users. Only time will tell if that is really the case. Let us know in the comment section below whether the new version of the update installed fine on your end or if the update is still causing issues.