A
ArtSnob
Update KB4340557, "Security and Quality Rollup for .NET Framework 3.5, 4.52, 4.6, 4.6. I, 4.6.2, 4.7, 4.7. I, 4.7.2 " will not install on my Server 2012 machine. It gets part way and then crashes with error code 80092004. The "get help with this error" link is as useless as it's always been. I get a red dot for the machine in my WSUS console.
I decided to try installing it as a standalone package and downloaded "2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, ...6.2, 4.7, 4.7.1, 4.7.2 for Windows Server 2012 for x64 (KB4340557)" from the Microsoft Download Catalogue. It turned out to be a ZIP file with four installation packages in it. However, all of the installation packages were for KB4338418. I installed one that was the same size as the original and it installed properly. However, since it wasn't KB4340557, the red dot in WSUS persisted.
So I investigated further, and followed the instructions for Fix Windows Update errors by using the DISM or System Update Readiness tool. The DISM command ran to completion and reported, "The restore operation completed successfully. The component store corruption was repaired." But the update still fails identically as it did at the start. The red dot persists.
I've exhausted all available unpaid support from Microsoft. Has anyone ever overcome a similar dead end with a similar problem?
Continue reading...
I decided to try installing it as a standalone package and downloaded "2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, ...6.2, 4.7, 4.7.1, 4.7.2 for Windows Server 2012 for x64 (KB4340557)" from the Microsoft Download Catalogue. It turned out to be a ZIP file with four installation packages in it. However, all of the installation packages were for KB4338418. I installed one that was the same size as the original and it installed properly. However, since it wasn't KB4340557, the red dot in WSUS persisted.
So I investigated further, and followed the instructions for Fix Windows Update errors by using the DISM or System Update Readiness tool. The DISM command ran to completion and reported, "The restore operation completed successfully. The component store corruption was repaired." But the update still fails identically as it did at the start. The red dot persists.
I've exhausted all available unpaid support from Microsoft. Has anyone ever overcome a similar dead end with a similar problem?
Continue reading...