Fix For .Net Framework Update KB4340558 Error 0x80092004

1 view

Skip to first unread message

Message has been deleted

Vida Hubbert

unread,

Jul 10, 2024, 11:06:54 PM7/10/24

to plotdespdismo

Just wondering if this is affecting other users who run the same server OS? I have tried the usual fixes but the update keeps failing, hopeful its a generic issue that will be resolved with a new update being pushed out?

Fix for .Net Framework Update KB4340558 error 0x80092004

Download File ->->->-> https://tlniurl.com/2yKEvU

Hi, it failed on 6 of our test servers, im not going to approve it for the rest, it worked OK on desktops just the servers with an issue, the error seems to indicate an issue with the patch, if you look at the link someone posted above. Im hopping an updated patch will be released within a week or two,

My English version of the blog post is also online. See: .Net Framework: Update KB4340558 drops error 0x80092004? Born's Tech and Windows World .Net Framework: Update KB4340558 drops error 0x80092004?

For the people who are failing, do you approve the Security Only Quality updates or do you approve the Security Monthly Quality updates on a regular monthly basis? And also do you approve the Security Only update for .NET framework or do you approve the Security and Quality Rollup for .NET framework?

[German]A brief information for users who install the August 2019 security updates KB4512506 or KB4512486 for Windows 7 SP1 and Windows Server 2008 R2 in an installation error 0x80092004. It is highly likely that updates to retrofit SHA-2 support will then be missing.

It didn't take long after the release of the security updates KB4512506 (Monthly Rollup) or KB4512486 (Security Only) for Windows 7 SP1 and Windows Server 2008 R2 until the first users reported issues within my German blog. German blog reader Heidemann wrote in this comment:

I mentioned the error code 0x80092004 in some blog posts (see links at the end of the article) and Microsoft also published a KB article about the error. However, this KB article refers to a bug in the .NET framework that prevents updates from being installed. However, I don't consider this to be a valid cause, as these are currently Windows updates.

Before you start any wild experiments, it's good to know what the cause of the error is. The error code 0x80092004 stands for CRYPT_E_NOT_FOUND. Windows Update could not find any cryptographic value and rejects the update.

I had it mentioned in the blog post Symantec/Norton blocks Windows Updates (SHA-2). Microsoft changed the signing of update packages for Windows 7 SP1 and Windows Server 2008/R2 for the first time in August 2019. Instead of signing the packages with both SHA-1 and SHA-2, only a SHA-2 hash value is stored in the package. The above error code indicates that Windows Update is looking for the SHA-1 signature in the package and does not find it.

One possibility is that an external virus scanner recognizes and modifies the update packets incorrectly. The blog post Symantec/Norton blocks Windows Updates (SHA-2) mentions that Symantec and Norton security solutions cause trouble. In this scenario, however, Microsoft blocks the delivery of security updates.

Weighting the above information, there is a lot of evidence that the support for the new updates and Windows signed exclusively by SHA-2 is simply missing. As of March 12, 2019, Microsoft had extended support article 4472027 (2019 SHA-2 Code Signing Support requirement for Windows and WSUS) to include the SHA-2 updates required for Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, and Windows Server 2008 Service Pack 2.

I had mentioned within my blog post Windows 7: Updates for SHA-2 support, that it's required both updates are installed. Within my German comment here I had recommended checking to see if the relevant updates were available. In fact, blog reader M. Gruber reported here that the SSU KB4490628 was missing on his machine. After installing the Servicing Stack Update (SSUs) from March 2019, the August 2019 security update for Windows 7 SP1 and Windows Server 2008 R2 was successfully installed. And I got a 2nd feedback, that this was the root cause for the update install error. Perhaps it will help one or the other affected person.

After reading this information, I did some recon on these workstations. They all have KB4474419, but they were all missing KB4490628. Just now, I manually added KB4490628 to two workstations, then attempted a manual install of KB4516065. Both installed successfully now and are working without issue.

Secondly, I did not have KB4490628 installed, this did the trick.
After a short search WSUS was to blame. This update was reported installed, but really was not. After installation, the rest worked fine again.

I tried these recommendations but I would still get "windows failed to start" after the update, had to boot with win7 cd and then do a restore to get back to point before the update. Finally found the fix, I installed all of the "optional" updates that were marked "recommended", after doing this I was able to install update KB4512506 without issue.

Windows7 Pro and I was never offered the update 4490628 either. Personal attack by GBorn? I have now wasted hours on MS incompetence. Lets blame the victims? Tired of this typical nonsense with MS. Will now have to disable AVAST modules, clear the cache, and manually download this and pray it works. Thanks Microsoft!

Yes, thank you very much for researching and posting this information with the detailed background and explanation of the root cause, and thanks to the commenters for reporting on their experiences. I found I already had KB4474419 installed and only needed KB4490628. Once I installed KB4490628, I was then able to install KB4512506, the 2019-08 Security Monthly Quality Rollup that had failed to install and that gave the 0x80092004 error.

With 10 years running Win 7 (since the initial release), I can perhaps forgive a few hiccups in the OS. For the most part, Win 7 has aged like fine wine. However, if I were to consider the problems that have taken the most time for me to research and resolve, particularly since 2016, the chief culprit is probably Windows Update.

thanks the solutions posted here about requiring the pre-requisite files kb4490628 and kb4474419 confirmed fixed my problem with error 0x80092004 on trying to install KB4512506. Some organizations choose to only install Critical and Security Update categories using WSUS or SCCM so these updates must be "optional" category even though they should be "critical" to continue getting security updates later. Somebody was really sleeping at Microsoft office.

Many thanks. I got a laptop to repair after someone had spilled milky sweet coffee over the keyboard. (They denied they'd done it, but the evidence was there to see. It might have been vomit though.) Easy fix on a Dell E5500. I love these proper work oriented laptops. No need for pry tools and hot glue. The laptop hadn't been updated for 4 years. Windows 7 32 bit. I ran the Microsoft Fixit tool and got most of the updates, but was blocked at the last hurdle. KB4490628 sorted it. Thanks again.

An example: 64-bits. The only thing it does is steal. In the first place, there are no reasons for a maximum of 4 GB internal memory in 32-bits systems. This is just a short example. (I unlocked this memory lock with a small software*)

When installing KB4490628 (I didn't do a restart), also those stuck updates now did install. Though my system could not boot into Windows. In my boot menu I chose the other option, which is the same OS. That small software that unlocks the memory puts two boot entries in the boot menu. One is, where the lock is still there. I could boot into that. And then probably unlock again to be able to boot into the other option again. (I don't mean this happens all the time. Not to me. Though I am not a "update fetisjist". Pardon my French). I looks like it only updates basically cause problems with this.

Wants to fix windows update error 80092004, yes it might looks like difficult and frustrating, just calm down, you are here because, we have the attached the solution attached in the link, you can go through it, find the easiest solution ever. We have explained it in a way that every body can read, understand and apply to fix the said error.

You may notice on Windows Server 2012 R2, when applying Windows Updates that one or more .NET updates may fail with error code 0x80092004. This issue may affect all, or only some of your Windows Server 2012 R2 servers.

Thank you much for assisting the many IT administrators across the globe in resolving this issue. I performed the steps as listed on my two 2K12 R2 domain controllers and they worked well. I particularly appreciated the in-window command-line scripts. Of note, I waited until the last install of the four re-install scripts before rebooting.

Stephen,
Thank you very much, I have been looking for a solution off and on for a couple months.
If your ever in Minneapolis, and would like a beer, stop by Broken Clock Brewery, and you can have a pint on me! Thank You again. Tom W.

Hi Stephen
We have struggled with this issue for a long time across a number of our servers . .
We are indebted to you for not only figuring this out, but also being generous enough to share.
Thank you

Awesome Stephen! Without your precise and simple instructions I was unable to Update mit Exchange 2013 Server to cu 22 because .net 4.7.1 was a prerequisite. Many thanks from Germany! Have a good one ?

Stephen, after a google search I found your concisely worded solution to this KB install problem and implemented it on 2 of my servers. It fixed the problem flawlessly. Thank you so much for taking the time to write this out so clearly! Best Regards! -Wes

[English]Gestern Nacht hat Microsoft das .Net Framework-Update KB4340558 fr Windows freigegeben. Wie es ausschaut, ist dieses Update aber buggy und lsst sich nicht installieren. Ergnzung: Auch Update KB4054566 lst bei manchen Systemen den gleichen Fehler aus. Ergnzung 2: Microsoft hat den Bug besttigt. Ergnzung 3: Microsoft hat Workaround gepostet.