There is obviously a fix for the install error 0x80092004 caused from .Net Framework update KB4340558. Here are a few details about the status of that topic.
In July 2018 Microsoft released .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). But this update caused serious install errors on machines with Windows 8.1 and Windows Server 2012 R2. Shortly after the update release, 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.”
I’ve reported this within the blog post .Net Framework: Update KB4340558 drops error 0x80092004? But blog reader Markus B. wasn’t the only one. Worldwide numerous users has been hit by this install error. Microsoft has pulled this update due to the issues and re-released another version (see Revised .NET Framework Update KB4340558 (July 19, 2018)). But this didn’t fix the install issues at all. On July 30, 2018 pushed another .NET Framework with fixes to affected machines (see my blog post NET-Framework Updates July 30, 2018 with Fixes).
Someone found a workaround
Microsoft’s attempts to fix those install issues still leaves some people ‘in the rain’, because they continue to fail during install – especially on Windows Server 2012 R2. Gladly a German blog readers posted a solution for a workaround within this comment.
- Expand the .msu files of the update packages into a local folder of the machine using the DOS expand –f command.
- Uninstall all faulty .NET framework updates using dism /online /remove-package.
- Install the expanded new updates using dism /online /add-package.
The details of this solution may be found on (and the credit goes to) Stephen Wagner’s blog post Windows Server 2012 R2 .NET Windows Updates fail with error 0x80092004, dated on August 21, 2018.