0x80092004 kb4535102 – Here we can see “windows update error code 80092004”
Windows Update error 0x80092004 occurs on Windows 7 and Server 2008, R2.
Microsoft released all the updates for Windows client and server on August 2019, Patch Day. If you haven’t already, we’ll show you our overview of the latest updates.
Reports suggest that some administrators and residential users face issues with the released updates on machines running Windows 7 or Windows Server 2008 R2.
0x80092004 is the error that prevents you from putting in updates KB4512506 (monthly rolling update) and KB4512486 security-only update. The error code CRYPT_E_NOT_FOUND indicates that Windows Update rejected the updates because the package contains cryptographic values.
Also, see Spotify error code 17
Microsoft changed the signing of update packages for Windows 7 and Windows Server 2008 R2 devices on the August 2019 Patch Day for the primary time. The corporate has been signing packages with SHA-2 only since August 2019. It had previously signed them with SHA-1, SHA-2 and then decided to drop SHA-1 because of known weaknesses.
In 2018, we published a piece about the change that stated that Windows 7 (and Server 2008 R2) systems required certain patches to continue receiving updates.
The affected Windows systems may be trying to locate SHA-1 in the update package, and ignore SHA-2. SHA-1 is not included anymore. This is why error 0x80092004 appears.
Microsoft disclosed that Symantec and Norton software on Windows 7 and Windows Server 2008 R2 doesn’t work well with the change. Microsoft decided to suspend Symantec or Norton software updates until the problem is solved. These safety measures may prevent or delete Windows Updates.
It may seem difficult to believe that some antivirus solutions are causing problems with Windows Updates. However, it is more likely that an update is missing.
Windows 7 and Windows Server 2008 R2 needed two updates to ensure that SHA-2-signed updates were correctly installed
- KB4474419Update for SHA-2 code signing support for Windows Server 2008 R2, Windows 7, and Windows Server 2008: August 13, 2019,
- KB4490628 March 12, 2019, Servicing stack upgrade for Windows 7 SP1 or Windows Server 2008 R2 SP1
If any of these aren’t installed, SHA-2-signed updates won’t work and the error will be thrown.
Also, see: How to delete ringtones from iPhone
Microsoft confirms that KB4474419 may be a prerequisite on the support website. The corporate also lists KB4490628 on the page. It strongly recommends that it be updated. SSU updates can be automatically installed if Windows Updates are used, but must be manually installed if updates are manually installed. It’s not clear why Microsoft does not list the SSU as a prerequisite.
These updates can be verified by looking at the “Installed Updations” list in the instrument panel or running third-party software such as Nirsoft’s WinUpdatesList.
Install the minimum one of the updates and do a replacement check to make sure it is installed. The August 2019 update should then install fine.
Questions from the user:
- Windows Update Error code 80092004 for Update KB4340558 (.NET Framework Upgrade)
The Update KB4340558,.NET Framework Update was published July 10, 2018. I am experiencing an 80092004 error for the past two days. What is the cause and how can it be fixed?
- Error code 80092004 while trying to update Windows 7
My friend runs Windows 7 Home on his computer. He gets error 80092004 when he runs the updates. The error 80092004 is caused by KB4519976 (2019-10 Security Monthly Qrollup for Windows 7 x64-based Systems). I tried restarting Windows Update again, but the same problem occurred. The error code 80092004 appears in my search, but it is not specific to Windows 7 or KB4519976. What should I do to make this update work? Thank you.
Also see: Facebook Ends Its Temporary Ban On Political Ads
- Windows Update Error 80092004 Server 2008R2
There are still 5 Windows Server 2008r2 servers (yes, we do want to prevent them). We were seeing the error above after we applied windows security updates. This error was anyone else spotted?